OpenEuphoria

Re: WIN32 API Constant Declarations

• Posted by Gary Dumer <dumer9354 at WHITE-MARSH.AIM-SMART.COM> Jun 25, 1999
• 470 views

I think you should continue with multiple definitions (duplicates) and let
the user determine the proper ones. However, It would be desirable if you
would highlight the dups with an obvious comment at the proper place.

Gary.

-----Original Message-----
From: JJProg at CYBERBURY.NET <JJProg at CYBERBURY.NET>
To: EUPHORIA at LISTSERV.MUOHIO.EDU <EUPHORIA at LISTSERV.MUOHIO.EDU>
Date: Friday, June 25, 1999 2:32 PM
Subject: Re: WIN32 API Constant Declarations


>EU>To Jeffrey Fielding... It would be great to have a Euphoria version.
>
>
>EU>>They're in Visual Basic format, but it's pretty simple to convert -
I'll
>EU>>write an Euphoria version when I have a chance.
>
>After writing a program to convert the constants and comments to
>Euphoria (I was going to do the types and functions after I got this
>working), I noticed that Microsoft was very sloppy with their constant
>declarations - many constants depend on other constants that they define
>later, and I fixed these. The main problem is that they give constants
>with the same name different values. KEY_EXECUTE is defined as 0 first,
>then defined as 1.
> I was hoping to write an include file so one could just include the file
>and not search for constants and copy them etc., but the file doesn't
>work at the moment because of the multiple declartions. Shall I continue
this
>by renaming the constants, or continue with the multiple definitions and
>figure the user will figure out which constant they should use.
>
>Jeffrey Fielding
>JJProg at cyberbury.net
>http://members.tripod.com/~JJProg/