Viktor Szakáts wrote:
>
>> BTW we can also introduce #pragma push/pop which can be used
>> by user to resolve the problem of interaction between compiler
>> switches in much more flexible way.
>
> It's very good idea. Maybe it even makes the per file
> issue easier to fix, since it's possible to internally
> issue a push/pop at the beginning/end of each separate
> source.
>
xHarbour already has push/pop and our code contains
some such occurrances. However, I had to guard them under
#ifdef __XHARBOUR__ while compiling with Harbour.
-----
enjoy hbIDEing...
Pritpal Bedi
http://hbide.vouch.info/
--
View this message in context:
http://harbour-devel.1590103.n2.nabble.com/hbMK2-xHarbour-Oct-2007-Unresolved-External-tp5033192p5042377.html
Sent from the harbour-devel mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
