Re: Windows stuff...
Tommy Carlier wrote:
>
> If such a standard API-library would be made, the constants should have a
> prefix, to
> reduce the chance of possible naming conflicts.
This is really a precedence issue. Maybe such commonly used names should
be regarded as if they were reserved words and thus no-one can use
them for other things. Its a pity that Microsoft chose commonly
used words, such as "Normal", "Bold",...
> Win32Lib uses x as a prefix (xSetVisible, ...) for functions, but no prefix
> for constants
> and structures. Perhaps it would be good to prefix all definitions.
The 'x' prefix is a mistake. There should not have been any prefix. But hey,
its a "standard"!
Some constants have prefixes, some don't. Another mistake. The API ones
don't (and that's a good thing), and the ones created by the library do.
> I suggest 'api' as prefix, unless someone can find a better prefix (or
> multiple prefixes).
> Examples: apiSetVisible, apiWM_PAINT, ...
Don't make that mistake again. The prefixes are not needed if we regard
the Microsoft names as reserved words.
However, if you are writing a platform independant library, then you are
free to invent new names 
--
Derek Parnell
Melbourne, Australia
|
Not Categorized, Please Help
|
|
