[fpc-devel] Major problem with Move and Array of Int64

Hans-Peter Diettrich DrDiettrich1 at aol.com
Fri Sep 23 16:32:21 CEST 2011


Andrew Brunner schrieb:
> On Fri, Sep 23, 2011 at 7:28 AM, Martin Schreiber <mse00000 at gmail.com> wrote:
>> On Friday 23 September 2011 14.00:07 Sergei Gorelkin wrote:
>>> Recently strings behavior was changed, they are now codepage-aware. The
>>> compiler can now implicitly convert strings from one encoding to another.
>>> To handle non-string data, you should use RawByteString type, or better
>>> yet non-string types like (dynamic) array of byte.
>>>
>> So TBlobField.Value probably should be changed to array of byte and there
>> should be a TField.AsByteArray property?
>>
> 
> Yes, Certainly.  Or better even Stream objects.

Why not use (or introduce) an TBlob type, matching the need of DB users 
and other users, which currently use strings for storing raw bytes. It 
must not be a really new type, just an alias for the suggested type for 
such content.

DoDi




More information about the fpc-devel mailing list