I think that dropping D3 at this time would be very reasonable. I know of
only a few very rare instances of people or companies still using D3 or D4;
a lot using D5; some D6; and many on D7.
Of course, if you want int64s in your TStreams ;-) , I think you have to
move up to D6 or D7... ?
- - - - - - - -
On the other hand, if you want to maintain support for D3, you might be able
to avoid most of those IFDEFs by defining your own types and referring to
those everywhere else. Something roughly like:
type
{$IFDEF VER140andUp...} // Using one of those include files that defines
things like "D4andUp"...
TSynaLargeInteger = int64;
{$ELSE}
TSynaLargeInteger = integer;
{$ENDIF}
In that case only "bit-twiddling" code would normally care how large the
integer is, and that can be compensated for too...
???
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
synalist-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/synalist-public
