Re: [fpc-pascal] When is AnsiString not a good substitute for string?

2010-03-21 Thread Jürgen Hestermann
Jorge Aldo G. de F. Junior schrieb: actually, for most porpuses, ansistring is a lot faster than normal strings with size 255... you pass around 4 bytes instead of 256... That would be only true if you have multiple variables pointing to the same string without changing each instance. I don't b

Re: [fpc-pascal] When is AnsiString not a good substitute for string?

2010-03-21 Thread Jonas Maebe
On 21 Mar 2010, at 21:07, Jorge Aldo G. de F. Junior wrote: > actually, for most porpuses, ansistring is a lot faster than normal > strings with size 255... > > you pass around 4 bytes instead of 256... And on the downside the compiler inserts a lot of initialisation/finalisation and reference

Re: [fpc-pascal] When is AnsiString not a good substitute for string?

2010-03-21 Thread Jorge Aldo G. de F. Junior
actually, for most porpuses, ansistring is a lot faster than normal strings with size 255... you pass around 4 bytes instead of 256... ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] When is AnsiString not a good substitute for string?

2010-03-21 Thread Jürgen Hestermann
Frank Church schrieb: I recently posted a question about problems involving the use of string and AnsiString when converting a Delphi program. Are the some situations where substituting AnsiString for string will result in errors? The string type is a generic type and can be ShortString or AnsiS

[fpc-pascal] When is AnsiString not a good substitute for string?

2010-03-21 Thread Frank Church
I recently posted a question about problems involving the use of string and AnsiString when converting a Delphi program. Are the some situations where substituting AnsiString for string will result in errors? Does using {$mode delphi}, {H+} involve cases which might introduce hard to track errors?