Generally speaking .prg should never depend on the C compiler used to build the software, it's a low-level implementation detail. For this reason we don't have such macro and I don't think we should have one.
If you need to create different code for different compilers (f.e. because some external components are or aren't available based on that), you can solve it on the build level, and/or you can introduce some local macros which control inclusion of these components. (hbmk2 helps you to do that) Brgds, Viktor On 2009 Nov 16, at 14:44, Ciro Vargas C wrote: > Very thanks Chen and Massimo, another similar way in a #ifdef ? > > > regards > Ciro > > 2009/11/16 Chen Kedem <n...@synel.co.il>: >> Ciro, >> >>> any way to know what compiler has been used at compile time in PRG level ? >> >> HB_Compiler() >> >> Chen. >> _______________________________________________ >> Harbour mailing list (attachment size limit: 40KB) >> Harbour@harbour-project.org >> http://lists.harbour-project.org/mailman/listinfo/harbour >> > > > > -- > http://www.oohg.prg > http://sistemascvc.tripod.com > > donaciones para CVC de ooHG > > https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=5369884 > _______________________________________________ > Harbour mailing list (attachment size limit: 40KB) > Harbour@harbour-project.org > http://lists.harbour-project.org/mailman/listinfo/harbour _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
