Basically, the OW is ok with the functions,as long as they are prepended with an underscore or something to prevent pollution of the namespace, so #defining __TURBOC_FUNCS__ would then be necessary to use them.
On 6/13/06, Arkady V.Belousov <[EMAIL PROTECTED]> wrote: > Hi! > > 13-Июн-2006 14:26 [EMAIL PROTECTED] (Alain M.) wrote to > freedos-devel@lists.sourceforge.net: > > >> >> BC> Turbo C is an old compiler. In many instances, it conflicts with > the > >> >> BC> C standard. > >> >> No, it not confilicts with C standard, And especially not in > question > >> >> of initialization of uninitialized static variables. > AM> I believe that the standard changed since Borland's DOS compilers. And > > Yes, there was added many features since Turbo C times. But > initialization of uninitialized static variables rule wasn't changed. > > AM> OW is upgrading to the standard > > Yes, OW is more compliant to newer standards. > > AM> OTOH, OW does not have all the Borland functions, > > It have _no one_ Borland' function. "Borland" name for OW team has bad > reputation and there was/is no plans to support any compatibility level with > Borland's compilers. Only MS compilers compatibility somewhat supported. > > AM> but it many people have written those. (inclusing some myself) > > AFAIR, Blair offers to OW team some library functions, to increase > Borland compatibility. Don't know their current state. > > > _______________________________________________ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel > -- Fall is my favorite season in Los Angeles, watching the birds change color and fall from the trees. David Letterman (1947 - ) See ya _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
