Re: [fpc-pascal] how to make a type private to the unit but not defining it in the implementation section?

2019-03-07 Thread Dennis Poon
Anthony Walter wrote: type   _PrivateData = class     private type THidden = record Name: string; end;   end; ... and later in the implementation section of the same unit ... var H: _PrivateData.THidden; begin H.Name := 'Hello'; end; But that will have the same problem of extra long method

[fpc-pascal] Error: Local variables size exceeds supported limit

2019-03-07 Thread Fabio Luis Girardi
Hi All! I'm trying to use the FPC 3.2.0 beta + Lazarus 2.0.1 with fpCEF3. But when I try compile this package with FPC 3.2.0 I got this error: Error: Local variables size exceeds supported limit But the same package compiles fine with FPC 3.0.4 and 3.0.5. Should I fill a bug report? Ahh, in ti

Re: [fpc-pascal] how to make a type private to the unit but not defining it in the implementation section?

2019-03-07 Thread Anthony Walter
type _PrivateData = class private type THidden = record Name: string; end; end; ... and later in the implementation section of the same unit ... var H: _PrivateData.THidden; begin H.Name := 'Hello'; end; ___ fpc-pascal maillist - fpc-pascal@li

Re: [fpc-pascal] *.rst vs *.rsj

2019-03-07 Thread Victor Campillo
On 7/3/19 18:33, Luca Olivetti wrote: Guess whay I'm using them for? ;-) https://bugs.freepascal.org/view.php?id=30208 Good to know that I am not alone using Freepascal in industrial environments :-) The most of my projects are still with FPC 2.6.4 but next week I will start a new one, as F

Re: [fpc-pascal] *.rst vs *.rsj

2019-03-07 Thread Luca Olivetti
El 7/3/19 a les 17:44, Victor Campillo ha escrit: On 7/3/19 9:02, Luca Olivetti wrote: Beware, if you use bitpacked records or threading there are bugs in 3.0.4. I have to keep using 2.6.4 due to that. Apparently the 3.2 branch works fine in my case, but it's still unreleased. Also the transiti

Re: [fpc-pascal] *.rst vs *.rsj

2019-03-07 Thread Victor Campillo
On 7/3/19 9:02, Luca Olivetti wrote: Beware, if you use bitpacked records or threading there are bugs in 3.0.4. I have to keep using 2.6.4 due to that. Apparently the 3.2 branch works fine in my case, but it's still unreleased. Also the transition to codepage aware ansistrings, though not as te

Re: [fpc-pascal] *.rst vs *.rsj

2019-03-07 Thread Luca Olivetti
El 6/3/19 a les 23:40, Graeme Geldenhuys ha escrit: On 06/03/2019 22:30, Florian Klämpfl wrote: You had the same discussion years ago with Jonas, conclusion: http://lists.freepascal.org/pipermail/fpc-pascal/2016-July/048264.html Awesome! Glad my point of view hasn't changed over time. ;-) Man

Re: [fpc-pascal] how to make a type private to the unit but not defining it in the implementation section?

2019-03-07 Thread Michael Van Canneyt
On Thu, 7 Mar 2019, Dennis wrote: unit frproxyserver; {$mode objfpc}{$H+} interface uses   Classes, SysUtils, Forms, Controls, Graphics, Dialogs, ExtCtrls, Grids,   frBase; type   TMyStringGrid=class(TStringGrid) //how to I make this class visible only to this unit?   public   end;   {

Re: [fpc-pascal] how to make a type private to the unit but not defining it in the implementation section?

2019-03-07 Thread Darius Blaszyk
Make stringgrid1 a pointer and put TMyStringGrid in the implementation section? Op do 7 mrt. 2019 om 09:11 schreef Dennis > unit frproxyserver; > > {$mode objfpc}{$H+} > > interface > > uses >Classes, SysUtils, Forms, Controls, Graphics, Dialogs, ExtCtrls, Grids, >frBase; > > type > >

[fpc-pascal] how to make a type private to the unit but not defining it in the implementation section?

2019-03-07 Thread Dennis
unit frproxyserver; {$mode objfpc}{$H+} interface uses   Classes, SysUtils, Forms, Controls, Graphics, Dialogs, ExtCtrls, Grids,   frBase; type   TMyStringGrid=class(TStringGrid) //how to I make this class visible only to this unit?   public   end;   { TProxyServerFrame }   TProxyServerFr