Re: [fpc-pascal] TCustomStream still using LongInt and not Int64

2020-12-27 Thread Graeme Geldenhuys via fpc-pascal
On 27/12/2020 5:02 pm, Michael Van Canneyt via fpc-pascal wrote: > Because on 32 bit platforms, this is the maximum size of available memory for > a program, and we like things maximally portable. You can't read more than > 2gb in memory on a 32-bit platform. Ha yes, it's been so long since I ran

Re: [fpc-pascal] TCustomStream still using LongInt and not Int64

2020-12-27 Thread Michael Van Canneyt via fpc-pascal
On Sun, 27 Dec 2020, Graeme Geldenhuys via fpc-pascal wrote: Hi, Is this a bug in FPC 3.2.0 where TCustomStream still uses LongInt in the Read() method, where all other methods in in the class uses Int64 type? Here is the FPC code: TCustomMemoryStream = class(TStream) private FMemory:

[fpc-pascal] TCustomStream still using LongInt and not Int64

2020-12-27 Thread Graeme Geldenhuys via fpc-pascal
Hi, Is this a bug in FPC 3.2.0 where TCustomStream still uses LongInt in the Read() method, where all other methods in in the class uses Int64 type? Here is the FPC code: TCustomMemoryStream = class(TStream) private FMemory: Pointer; FSize, FPosition: PtrInt; protected Function