Jeremy:
The FAR printf is probably good for 16-bit builds with DEBUG defined.
However, there are at least two potential issues (NOT YET VERIFIED).
1. 386 (or higher) builds might fail on a FAR value, as a 32-bit FAR is past
4GB.  I don't know how the compilers treat FAR in these builds.
2.Low memory systems?
It might be good (though perhaps difficult) to
1 Check for 16-bit
2 Check for DEBUG
If both are true,
3 Use FAR printf
Thank you,
Ibidem



------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Freedos-kernel mailing list
Freedos-kernel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

Reply via email to