Re: [GD-General] Feedback wanted on POSH

[Brian H. <ho...@py...>]

> After looking at your var definitions, I'm surprised to see a
> courageous developper who can spend time to write long variable
> type name for basic types ;p

The purpose there is to avoid potential name clashes with pre-existing 
libraries.

It's highly unlikely that someone else has posh_u16_t defined, but 
reasonably likely that someone out there has u16 or unsigned16 or 
u16_t defined.  The intent is that developers will alias their own 
types to the posh ones instead of actually using the posh ones 
everywhere.

I've updated the documentation to reflect this.

> which can make a prototype simple to read like :
> void MyFunction (IN const s32 _s32Int, IN const f32 *_pf32Array, IN
> OUT f32 *_pf32OutArray, OPTIONAL bool _bWrite);

I agree (I really wish that ANSI C had a "writeonly" keyword...), 
however I'm trying to make POSH more about utility and less about 
enforcing style.

Brian