>I havent tracked this discussion, but its just possible that you may
>have missed the significance of H+ (if using D3+). If the compiler
>option is H-, then string == shortstring. If it is H+ then
>string==ansistring. If using D3+, you should never use string as the
>type, always qualify it as shortstring or ansistring. Note that
>string[8] is automatically shortstring.
Unfortunately the original query incvolved long strings of variable length
therefore unable to use fixed length string allocation.
>The compiler has a serious bug, which will kick in if you are using
>string for type definition. Theoretically the compiler does auto
>conversions etc between the two string types. It fails however when
>the declaration is in another unit.
Ouch... I haven't encountered an example of it but then I always am using
long strings and declare shortstrings explicitly - but if someone else has
declared 'string' to mean shortstring then that could be serious... Hmm...
--
Aaron Scott-Boddendijk
Jump Productions
(07) 838-3371 Voice
(07) 838-3372 Fax
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
