Re: New keywords: ifdef, elsifdef, end ifdef
Jeremy Cowgar wrote:
>
> Shawn Pringle wrote:
> >
> > That sounds like optimization:
> >
>
> It's much more than that. It's the ability for conditional includes. It's the
> ability to remove code from bound or executable code you may not want in there
> (such as shareware/full), It gives you the function of even being able to
> maintain
> backwards compatability! Say for instance 4.1 comes out and 4.1 defines a new
> function called fast_find or who knows what. You can now:
>
> }}}
<eucode>
> ifdef EU400 then
> global function fast_find(...)
> end function
> end ifdef
> </eucode>
{{{
>
That would have been useful when win32lib.ew put a string type in their library.
What I meant by my previous post was you could blend the if and ifdef by
having the truth value evaluated when you the program gets bound. Then you
don't need ifdef. You could have a version() builtin to get a version number
|
Not Categorized, Please Help
|
|