On 19/04/2021 07:59, Michael Van Canneyt via fpc-pascal wrote:
>
> But MacOS is a problem.
macOS is also perfectly scriptable, I just have to finish automating it.
The main remaining problem is our hard-wrapped readme and whatsnew files
that look terrible in its installer (because it also perform
On Mon, 19 Apr 2021, Karoly Balogh via fpc-pascal wrote:
Hi,
On Mon, 19 Apr 2021, Sven Barth via fpc-pascal wrote:
Am 18.04.2021 um 23:29 schrieb Zamrony P. Juhara via fpc-pascal:
I would like to propose to separate RTL release from compiler release
so that RTL bug fixes and features can
Hi,
On Mon, 19 Apr 2021, Sven Barth via fpc-pascal wrote:
>> Am 18.04.2021 um 23:29 schrieb Zamrony P. Juhara via fpc-pascal:
>>
>> I would like to propose to separate RTL release from compiler release
>> so that RTL bug fixes and features can be released with shorter release
>> cycle. Is that p
Am 18.04.2021 um 19:58 schrieb Ryan Joseph via fpc-pascal:
On Apr 18, 2021, at 5:00 AM, Sven Barth wrote:
As I have said: Delphi compatibility.
This would have been a good candidate to put behind the delphi mode switch but
I'm sure there is a reason for this also.
Nowadays: backwards compa
Am 18.04.2021 um 23:29 schrieb Zamrony P. Juhara via fpc-pascal:
I would like to propose to separate RTL release from compiler
release so that RTL bug fixes and features can be released with
shorter release cycle.
Is that possible?
No, the RTL and the compiler are tightly coupled.
What mi
I would like to propose to separate RTL release from compiler release so that
RTL bug fixes and features can be released with shorter release cycle.
Is that possible?
Zamrony P. Juharahttps://github.com/zamronypj___
fpc-pascal maillist - fpc-pascal@
Graeme Geldenhuys via fpc-pascal schrieb
am So., 18. Apr. 2021, 17:54:
>
> On 18/04/2021 11:31 am, C Western via fpc-pascal wrote:
> > but there are also case where it never makes sense to
> > implement them and calling them indicates a logical error elsewhere in
> > the code.
>
> So do the logi
Jonas Maebe via fpc-pascal schrieb am
So., 18. Apr. 2021, 21:19:
> On 18/04/2021 18:08, Jonas Maebe via fpc-pascal wrote:
> > In this case, you
> > can easily make it an error yourself with {$warn 4046 error}.
>
> Correction: that's make it an error to construct a classes that contain
> abstract
On 18/04/2021 18:08, Jonas Maebe via fpc-pascal wrote:
> In this case, you
> can easily make it an error yourself with {$warn 4046 error}.
Correction: that's make it an error to construct a classes that contain
abstract methods. For abstract classes, it's {$warn 4122 error}
Jonas
___
On Sun, Apr 18, 2021 at 7:56 PM Travis Siegel via fpc-pascal
wrote:
>... but the last time I asked them
> about pricing, they told me it'd cost $1000 for just delphi 7, and that
> only costed $995 when it first came out, nearly 20 years ago.
Wow!
Long time ago, I bought Delphi2 (it was bundled w
> On Apr 18, 2021, at 5:00 AM, Sven Barth wrote:
>
> As I have said: Delphi compatibility.
This would have been a good candidate to put behind the delphi mode switch but
I'm sure there is a reason for this also.
Regards,
Ryan Joseph
___
fp
On 4/18/2021 11:55 AM, Graeme Geldenhuys via fpc-pascal wrote:
On 17/04/2021 10:09 pm, Sven Barth via fpc-pascal wrote:
but Delphi compatbility is more
important here, thus the default is a warning and not an error.
How is this beneficial? The compiler should help the developer, but here
it wa
On 18/04/2021 17:55, Graeme Geldenhuys via fpc-pascal wrote:
> On 17/04/2021 10:09 pm, Sven Barth via fpc-pascal wrote:
>> but Delphi compatbility is more
>> important here, thus the default is a warning and not an error.
>
> How is this beneficial? The compiler should help the developer,
People
On 17/04/2021 10:19 pm, Sven Barth via fpc-pascal wrote:
> The compiler's parser has a very limited look ahead and thus especially
> with more complex specializations (especially nested ones) and type
> overloads in scope the compiler might not come to the right decision
OK, that and the "it's m
On 17/04/2021 10:09 pm, Sven Barth via fpc-pascal wrote:
> but Delphi compatbility is more
> important here, thus the default is a warning and not an error.
How is this beneficial? The compiler should help the developer, but here
it was decided that it's beneficial for the program to crash at run
On 18/04/2021 11:31 am, C Western via fpc-pascal wrote:
> but there are also case where it never makes sense to
> implement them and calling them indicates a logical error elsewhere in
> the code.
So do the logical thing... Throw an exception! Don't promote a faulty
compiler. Fix your code ins
>I use currently Lazarus 2.0.12 / fpc 3.2.0.
I have Lazarus 2.04 / fpc 3.04 I have fpc 3.2.0 in another directory. It
should be easy enough for me to re-install Lazarus. Thanks for figuring that
out!
>I have corrected this point, it should work now.
Yes it looks fixed even in my large data fil
Le 18/04/2021 à 16:10, James Richters via fpc-pascal a écrit :
RE: [fpc-pascal] Directory Tree I getuFileVirtualTree.pas(533,9)
Error: identifier idents no member "DefaultEncoding"
It seems, using svn blame, that DefaultEncoding has been added in
FreePascal source trunk on the svn server on June
Thanks for figuring that out.
I get uFileVirtualTree.pas(533,9) Error: identifier idents no member
"DefaultEncoding"
For line:sl.DefaultEncoding:= TEncoding.GetEncoding(850);
If I just comment out that line, it works fine for me, because I'm codepage 850
anyway, but that doesn't help an
Am 18.04.2021 um 04:34 schrieb Ryan Joseph via fpc-pascal:
On Apr 17, 2021, at 3:09 PM, Sven Barth wrote:
The compiler will generate a warning in case you instantiate a class that is
abstract or has abstract methods. You can escalate these warnings to errors if
you need:
It's probably not
On 18/04/2021 03:34, Ryan Joseph via fpc-pascal wrote:
On Apr 17, 2021, at 3:09 PM, Sven Barth wrote:
The compiler will generate a warning in case you instantiate a class that is
abstract or has abstract methods. You can escalate these warnings to errors if
you need:
It's probably not prac
21 matches
Mail list logo
