1. Conflicts in include files
I am working on winmng.ew which employs windows support functions. I
wanted to test it on an application and used win32lib.ew also. When I
include them both in an .exw file, the obvious happens. The constant
definitions for various windows functions collide.
Have I missed something obvious? Is there a way to have the same
constant definitions in different .ew files and to avoid collisions?
If not. I have read some of the comments about preprocessing and so
forth. One simple thing that would help would be to have something like
a defined() function.
As it is, we can:
if atom(???) ...
if sequence(???) ...
Could we have:
if defined(variable or constant or function or routine) ...
This possibility would allow much more flexibility than we presently
have and would be simpler than the more complex solutions of
preprocessor statements. Such a function should be fairly simple, I
think.
--
Terry Constant
constant at flash.net
2. Re: Conflicts in include files
On Sun, 14 Jun 1998, Terry Constant wrote:
> If not. I have read some of the comments about preprocessing and so
> forth. One simple thing that would help would be to have something like
> a defined() function.
>
> As it is, we can:
>
> if atom(???) ...
> if sequence(???) ...
>
> Could we have:
>
> if defined(variable or constant or function or routine) ...
This should work for one half...
if routine_id("your function or procedure name here") != -1 ...
Detecting variables isn't possible and is probably messy to implement,
although EX.EXE's trace can tell you if a variable exists without
crashing, so it might not be that hard...
--
Carl R White
E-mail...: cyrek- at -bigfoot.com / Remove the hyphens before
Finger...: crwhite- at -dcsun1.comp.brad.ac.uk \ mailing or fingering...
Url......: http://www.bigfoot.com/~cyrek/
