Hi Phil,
Of course I can do it and will do it when I have time, I only would
like to see that it has established in Harbour. Basically, I don't
like the syntax, why was .ARCH. chosen, what do these dots mean, are
they somehow related to xBase syntax for logical values and operators?
;) Are there any other samples of usage of such syntax? Does someone
else feel it like me?
I think was chosen because such macro name would be invalid
but at least quite unlikely in normal usage. (I use such names
as special filenames in my code by coincidence)
Since this is basically an internal switch used in a few
obscure places, this is IMO fine.
Let's hope so. The other annoying bit is __PLATFORM__Windows
and __PLATFORM__Linux. Hopefully someone will fix them there.
I think we ([x]Harbour) should define both versions in the current
situation. It was of course a bad choice to make them mixed-case
initially, but I think that it should be kept for compatibility.
For full and seamless compatibility xhb compiler should always
define the mixed-case versions whenever the uppercased version
gets defined either by default or explicitly by user.
This way externally xhb could fully switch to uppercase,
while it would still handle mixed cased ones as an internal
matter for compatibility with xhb-specific sources relying
on them.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
