Re: [fpc-pascal] Bug or feature ?

Am 27.07.2022 um 15:14 schrieb Ched via fpc-pascal: Hello All, I have a long code which include lines for writing stuffs into an assigned writable text-file F.    WRITELN(F: 'Hello');    WRITELN(F, 'Hello'); The code can be compiled with 3.2.2 in i386/windows and i386/linux and runs both

Re: [fpc-pascal] Bug or feature ?

Le 27.07.2022 à 17:41, DougC via fpc-pascal a écrit : WRITELN(F: 'Hello'); is not proper Pascal. Yes, Doug, I agree ; but it is compiled with no warning and runs perfectly. Now, why the compiler do not complain... ? Cheers, Ched' ___ fpc-pascal

Re: [fpc-pascal] Bug or feature ?

WRITELN(F: 'Hello'); is not proper Pascal.___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

[fpc-pascal] Bug or feature ?

Hello All, I have a long code which include lines for writing stuffs into an assigned writable text-file F. WRITELN(F: 'Hello'); WRITELN(F, 'Hello'); The code can be compiled with 3.2.2 in i386/windows and i386/linux and runs both times at perfection. But... i'm wondering if the first

Re: [fpc-pascal] bug or feature?

This can't be right, can it? type TBird = class procedure Fly; end; TEagle = TBird; // alias procedure TEagle.Fly; begin end; It does depend on what you expect an Type-Alias to be. If you expect the compiler to generate an compatible class then your example must not be

Re: [fpc-pascal] bug or feature?

On Sun, 13 Feb 2022, Sven Barth via fpc-pascal wrote: Personally, I would not allow this. But Delphi compiles and runs it... ... and Delphi's class completion no longer works in the unit giving a useless error "expected ';' but '.' found". So it is one of those Delphi "features" compiling

Re: [fpc-pascal] bug or feature?

Am 13.02.2022 um 10:25 schrieb Sven Barth via fpc-pascal: Michael Van Canneyt via fpc-pascal mailto:fpc-pascal@lists.freepascal.org>> schrieb am So., 13. Feb. 2022, 09:47: On Sun, 13 Feb 2022, Mattias Gaertner via fpc-pascal wrote: > On Sat, 12 Feb 2022 12:14:14 +0100 (CET) >

Re: [fpc-pascal] bug or feature?

Michael Van Canneyt via fpc-pascal schrieb am So., 13. Feb. 2022, 09:47: > > > On Sun, 13 Feb 2022, Mattias Gaertner via fpc-pascal wrote: > > > On Sat, 12 Feb 2022 12:14:14 +0100 (CET) > > Michael Van Canneyt via fpc-pascal > > wrote: > > > >> On Sat, 12 Feb 2022, Mattias Gaertner via

Re: [fpc-pascal] bug or feature?

On Sun, 13 Feb 2022, Mattias Gaertner via fpc-pascal wrote: On Sat, 12 Feb 2022 12:14:14 +0100 (CET) Michael Van Canneyt via fpc-pascal wrote: On Sat, 12 Feb 2022, Mattias Gaertner via fpc-pascal wrote: > Hi, > > This can't be right, can it? > > type > TBird = class >procedure Fly; >

Re: [fpc-pascal] bug or feature?

On Sat, 12 Feb 2022 12:14:14 +0100 (CET) Michael Van Canneyt via fpc-pascal wrote: > On Sat, 12 Feb 2022, Mattias Gaertner via fpc-pascal wrote: > > > Hi, > > > > This can't be right, can it? > > > > type > > TBird = class > >procedure Fly; > > end; > > TEagle = TBird; // alias > > > >

Re: [fpc-pascal] bug or feature?

On Sun, 13 Feb 2022, Ryan Joseph via fpc-pascal wrote: On Feb 12, 2022, at 11:40 PM, Jonas Maebe via fpc-pascal wrote: I wouldn't consider this to be working by design, but rather because of implementation limitations. I agree and it should be fixed probably. As I wrote in my

Re: [fpc-pascal] bug or feature?

> On Feb 12, 2022, at 11:40 PM, Jonas Maebe via fpc-pascal > wrote: > > I wouldn't consider this to be working by design, but rather because of > implementation limitations. I agree and it should be fixed probably. Regards, Ryan Joseph

Re: [fpc-pascal] bug or feature?

On Sat, 12 Feb 2022 17:58:27 +0100 Jonas Maebe via fpc-pascal wrote: >[...] > >> I wouldn't consider this to be working by design, but rather > >> because of implementation limitations. +1 pas2js complained. That's how I found out. Someone renamed a class, added an alias for compatibility,

Re: [fpc-pascal] bug or feature?

On 12/02/2022 17:47, Michael Van Canneyt via fpc-pascal wrote: On Sat, 12 Feb 2022, Jonas Maebe via fpc-pascal wrote: On 12/02/2022 17:36, Michael Van Canneyt via fpc-pascal wrote: PS. Just tested, the compiler accepts both... Amazing, I never thought this would be possible. I'd better

Re: [fpc-pascal] bug or feature?

On Sat, 12 Feb 2022, Jonas Maebe via fpc-pascal wrote: On 12/02/2022 17:36, Michael Van Canneyt via fpc-pascal wrote: PS. Just tested, the compiler accepts both... Amazing, I never thought this would be possible. I'd better update the docs :-) I wouldn't consider this to be working by

Re: [fpc-pascal] bug or feature?

On 12/02/2022 17:36, Michael Van Canneyt via fpc-pascal wrote: PS. Just tested, the compiler accepts both... Amazing, I never thought this would be possible. I'd better update the docs :-) I wouldn't consider this to be working by design, but rather because of implementation limitations.

Re: [fpc-pascal] bug or feature?

On Sat, 12 Feb 2022, Sven Barth via fpc-pascal wrote: Michael Van Canneyt via fpc-pascal schrieb am Sa., 12. Feb. 2022, 12:14: On Sat, 12 Feb 2022, Mattias Gaertner via fpc-pascal wrote: Hi, This can't be right, can it? type TBird = class procedure Fly; end; TEagle = TBird; //

Re: [fpc-pascal] bug or feature?

Michael Van Canneyt via fpc-pascal schrieb am Sa., 12. Feb. 2022, 12:14: > > > On Sat, 12 Feb 2022, Mattias Gaertner via fpc-pascal wrote: > > > Hi, > > > > This can't be right, can it? > > > > type > > TBird = class > >procedure Fly; > > end; > > TEagle = TBird; // alias > > > >

Re: [fpc-pascal] bug or feature?

On Sat, 12 Feb 2022, Mattias Gaertner via fpc-pascal wrote: Hi, This can't be right, can it? type TBird = class procedure Fly; end; TEagle = TBird; // alias procedure TEagle.Fly; begin end; Personally, I would not allow this. But Delphi compiles and runs it... Maybe something to

[fpc-pascal] bug or feature?

Hi, This can't be right, can it? type TBird = class procedure Fly; end; TEagle = TBird; // alias procedure TEagle.Fly; begin end; Mattias ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org

Re: [fpc-pascal] bug or feature

Am 01.01.2021 um 19:21 schrieb Mattias Gaertner via fpc-pascal: Hi, library test; procedure Test; begin end; exports Test name 3 'abc'; //^^^ end. It's a bug. Please report. Regards, Sven ___ fpc-pascal maillist -

Re: [fpc-pascal] bug or feature

On Fri, 1 Jan 2021, Mattias Gaertner via fpc-pascal wrote: Hi, library test; procedure Test; begin end; exports Test name 3 'abc'; //^^^ end. I think this is a bug. Delphi also barfs on it. However the following does work: exports Test index 1 name 'abc'; Although

[fpc-pascal] bug or feature

Hi, library test; procedure Test; begin end; exports Test name 3 'abc'; //^^^ end. Mattias ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] bug tracker (bugs.freepascal.org) APPLICATION ERROR #400 (db connection failed)

On Sun, Aug 30, 2020 at 11:26 AM Michael Van Canneyt via fpc-pascal < fpc-pascal@lists.freepascal.org> wrote: > > > On Sun, 30 Aug 2020, Christo Crause via fpc-pascal wrote: > > > On Sun, Aug 30, 2020 at 9:45 AM Dmitry Boyarintsev via fpc-pascal < > > fpc-pascal@lists.freepascal.org> wrote: > > >

Re: [fpc-pascal] bug tracker (bugs.freepascal.org) APPLICATION ERROR #400 (db connection failed)

On Sun, 30 Aug 2020, Christo Crause via fpc-pascal wrote: On Sun, Aug 30, 2020 at 9:45 AM Dmitry Boyarintsev via fpc-pascal < fpc-pascal@lists.freepascal.org> wrote: The site opens up with: APPLICATION ERROR #400 I also get the above mentioned error when trying to open the website.

Re: [fpc-pascal] bug tracker (bugs.freepascal.org) APPLICATION ERROR #400 (db connection failed)

On Sun, Aug 30, 2020 at 9:45 AM Dmitry Boyarintsev via fpc-pascal < fpc-pascal@lists.freepascal.org> wrote: > The site opens up with: > > APPLICATION ERROR #400 > I also get the above mentioned error when trying to open the website. ___ fpc-pascal

[fpc-pascal] bug tracker (bugs.freepascal.org) APPLICATION ERROR #400 (db connection failed)

The site opens up with: APPLICATION ERROR #400 Database connection failed. Error received from database was #-1: Database connection failed. Please use the "Back" button in your web browser to return to the previous page. There you can correct whatever problems were identified in this error or

Re: [fpc-pascal] Bug 37080 -- StrToHostAddr accepts all Pascal number notations

Op 15-05-2020 om 12:48 schreef Michael Van Canneyt: On Fri, 15 May 2020, Noel Duffy via fpc-pascal wrote: As a consequence, StrToHostAddr will happily parse addresses like these: 0xa.3.4.5 9.$c.4.5 %.%11001110.30.4 &7.&5.30.4 12.+4.1.1 Fixed. Ahh.. why..  An ip-address of

Re: [fpc-pascal] Bug 37080 -- StrToHostAddr accepts all Pascal number notations

On Sun, 17 May 2020, Noel Duffy via fpc-pascal wrote: On 17/05/20 3:00 am, Michael Van Canneyt wrote: On Sat, 16 May 2020, Michael Van Canneyt wrote: On Sat, 16 May 2020, Jonas Maebe wrote: On 15/05/2020 12:39, Noel Duffy via fpc-pascal wrote: While doing some work on bug 37060, the

Re: [fpc-pascal] Bug 37080 -- StrToHostAddr accepts all Pascal number notations

On 17/05/20 3:00 am, Michael Van Canneyt wrote: On Sat, 16 May 2020, Michael Van Canneyt wrote: On Sat, 16 May 2020, Jonas Maebe wrote: On 15/05/2020 12:39, Noel Duffy via fpc-pascal wrote: While doing some work on bug 37060, the refactoring of StrToHostAddr and StrToHostAddr6 in the

Re: [fpc-pascal] Bug 37080 -- StrToHostAddr accepts all Pascal number notations

On 17/05/20 1:21 am, Jonas Maebe wrote: On 15/05/2020 12:39, Noel Duffy via fpc-pascal wrote: While doing some work on bug 37060, the refactoring of StrToHostAddr and StrToHostAddr6 in the sockets unit,(https://bugs.freepascal.org/view.php?id=37060), I found that StrToHostAddr is doing no

Re: [fpc-pascal] Bug 37080 -- StrToHostAddr accepts all Pascal number notations

On Sat, 16 May 2020, Michael Van Canneyt wrote: On Sat, 16 May 2020, Jonas Maebe wrote: On 15/05/2020 12:39, Noel Duffy via fpc-pascal wrote: While doing some work on bug 37060, the refactoring of StrToHostAddr and StrToHostAddr6 in the sockets

Re: [fpc-pascal] Bug 37080 -- StrToHostAddr accepts all Pascal number notations

On Sat, 16 May 2020, Jonas Maebe wrote: On 15/05/2020 12:39, Noel Duffy via fpc-pascal wrote: While doing some work on bug 37060, the refactoring of StrToHostAddr and StrToHostAddr6 in the sockets unit,(https://bugs.freepascal.org/view.php?id=37060), I found that StrToHostAddr is doing no

Re: [fpc-pascal] Bug 37080 -- StrToHostAddr accepts all Pascal number notations

On 15/05/2020 12:39, Noel Duffy via fpc-pascal wrote: > While doing some work on bug 37060, the refactoring of StrToHostAddr and > StrToHostAddr6 in the sockets > unit,(https://bugs.freepascal.org/view.php?id=37060), I found that > StrToHostAddr is doing no validation at all on input address

Re: [fpc-pascal] Bug 37080 -- StrToHostAddr accepts all Pascal number notations

On 15/05/20 11:25 pm, Michael Van Canneyt wrote: On Fri, 15 May 2020, Noel Duffy via fpc-pascal wrote: That must be a new record in bug fix speed. You fixed that within ten minutes of my message to the list! I forgot to mention in my message, but did mention in the bug report, that

Re: [fpc-pascal] Bug 37080 -- StrToHostAddr accepts all Pascal number notations

On Fri, 15 May 2020, Noel Duffy via fpc-pascal wrote: That must be a new record in bug fix speed. You fixed that within ten minutes of my message to the list! I forgot to mention in my message, but did mention in the bug report, that leading zeroes are also allowed, so you can parse:

Re: [fpc-pascal] Bug 37080 -- StrToHostAddr accepts all Pascal number notations

On 15/05/20 10:48 pm, Michael Van Canneyt wrote: On Fri, 15 May 2020, Noel Duffy via fpc-pascal wrote: While doing some work on bug 37060, the refactoring of StrToHostAddr and StrToHostAddr6 in the sockets unit,(https://bugs.freepascal.org/view.php?id=37060), I found that StrToHostAddr is

Re: [fpc-pascal] Bug 37080 -- StrToHostAddr accepts all Pascal number notations

On Fri, 15 May 2020, Noel Duffy via fpc-pascal wrote: While doing some work on bug 37060, the refactoring of StrToHostAddr and StrToHostAddr6 in the sockets unit,(https://bugs.freepascal.org/view.php?id=37060), I found that StrToHostAddr is doing no validation at all on input address

[fpc-pascal] Bug 37080 -- StrToHostAddr accepts all Pascal number notations

While doing some work on bug 37060, the refactoring of StrToHostAddr and StrToHostAddr6 in the sockets unit,(https://bugs.freepascal.org/view.php?id=37060), I found that StrToHostAddr is doing no validation at all on input address characters before calling the function Val, so any Pascal

[fpc-pascal] bug while generating androidR25.pas and Androidr25.inc

I know, that this task is heavy and should be only performed by The elites among Pascal programmers not by users of this programming language. But I Am sure, that if somebody experienced will answer. on my question, it would increase The number of volunteers, who would be ready to generate

Re: [fpc-pascal] bug in make install ?

On Tue, Mar 26, 2019 at 11:18 AM Cyrax wrote: > > I added poNoConsole to the 2 occasions of TProcessUtf8 I could fine in > > InitialSetupDlg, but I still see 2 console windows flashing by. > Does adding clauses for TProcess.StartupOptions := [suoUseShowWindow] > and TProcess.ShowWindow :=

Re: [fpc-pascal] bug in make install ?

On 24.3.2019 19.36, Bart wrote: On Sun, Mar 24, 2019 at 6:10 PM Joost van der Sluis wrote: Note: I see several times a window (console?) flash when starting up Lazarus now. Maybe add poNoConsole to ProcessOptions ? It's a bit annoying now. Can you test if this actually works on Windows (on

Re: [fpc-pascal] bug in make install ?

On Sun, Mar 24, 2019 at 11:41 PM Bart wrote: > > Sorry, I just never use that stuff in my programs. In a simple test program I can make this work withou a console wndow popping up: procedure TForm1.Button1Click(Sender: TObject); var S: String; begin Proc.Executable :=

Re: [fpc-pascal] bug in make install ?

On Sun, Mar 24, 2019 at 6:36 PM Bart wrote: > Sorry, I just never use that stuff in my programs. It seems that when you try to execute a program that writes to console and you specify [poNoconsole] then the program will exit with: Proc.ExitCode=C005, Proc.ExitStatus=C005 -- Bart

Re: [fpc-pascal] bug in make install ?

On Sun, Mar 24, 2019 at 6:10 PM Joost van der Sluis wrote: > > Note: I see several times a window (console?) flash when starting up > > Lazarus now. > > Maybe add poNoConsole to ProcessOptions ? > > It's a bit annoying now. > > Can you test if this actually works on Windows (on Linux this is not

Re: [fpc-pascal] bug in make install ?

Op 24-03-19 om 11:48 schreef Bart: On Sun, Mar 24, 2019 at 1:30 AM Bart wrote: Now I get the rather ludicrous error message: "Warning: The fpcmkcfg configuration tool it too old [3.3.1]." In function TInitialSetupDialog.CheckFpcmkcfgQuality(out Note: string): TSDFilenameQuality; else if not

Re: [fpc-pascal] bug in make install ?

On Sun, Mar 24, 2019 at 1:30 AM Bart wrote: > fpcmkcfg.exe does not support -V parameter Never mind that: it helps if you actually rebuild fpc, not just update the sources ;-) fpcmkcfg -h however does not list the "-V" option. Now I get the rather ludicrous error message: "Warning: The

Re: [fpc-pascal] bug in make install ?

Op 24-03-19 om 01:33 schreef Bart: Notice also that when you cancel the InitialSetupDialog, the IDE raises an exception when closing down: LAZARUS END - cleaning up ... [FORMS.PP] ExceptionOccurred Sender=EAccessViolation Exception=Access violation Stack trace: $0056EB8A

Re: [fpc-pascal] bug in make install ?

Op 24-03-19 om 01:30 schreef Bart: On Sat, Mar 23, 2019 at 7:56 PM Bart wrote: "Warning: Failed to retrieve the version of the fpcmkcfg configuration tool. It is probably too old to create the configuration files. Make sure a recent version is installed and available in the path or alongside

Re: [fpc-pascal] bug in make install ?

Notice also that when you cancel the InitialSetupDialog, the IDE raises an exception when closing down: LAZARUS END - cleaning up ... [FORMS.PP] ExceptionOccurred Sender=EAccessViolation Exception=Access violation Stack trace: $0056EB8A TWINCONTROL__HANDLEALLOCATED, line 7442 of

Re: [fpc-pascal] bug in make install ?

On Sat, Mar 23, 2019 at 7:56 PM Bart wrote: > "Warning: Failed to retrieve the version of the fpcmkcfg configuration > tool. It is probably too old to create the configuration files. Make > sure a recent version is installed and available in the path or > alongside the compiler-executable." in

Re: [fpc-pascal] bug in make install ?

I installed fpctrunk from sources r41749 (make clean; make install). It resides in C:\PP I think it is not an unusual setup. I built lazarus trunk r60747 with it. Lazarus tells me: "Warning: Failed to retrieve the version of the fpcmkcfg configuration tool. It is probably too old to create the

Re: [fpc-pascal] bug in make install ?

On 3/19/19 2:06 PM, Joost van der Sluis wrote: On 3/19/19 11:35 AM, Mattias Gaertner via fpc-pascal wrote: On Tue, 19 Mar 2019 11:17:42 +0100 Joost van der Sluis wrote: [...] Probably it fails because I have old 2.6.4 fppkg configs. I ran the samplecfg, which said it would create

Re: [fpc-pascal] bug in make install ?

On 3/19/19 11:35 AM, Mattias Gaertner via fpc-pascal wrote: On Tue, 19 Mar 2019 11:17:42 +0100 Joost van der Sluis wrote: [...] Probably it fails because I have old 2.6.4 fppkg configs. I ran the samplecfg, which said it would create ~/.fpc.cfg, ~/.fp, ... Then the error was gone. I

Re: [fpc-pascal] bug in make install ?

On Tue, 19 Mar 2019 11:17:42 +0100 Joost van der Sluis wrote: >[...] > > Probably it fails because I have old 2.6.4 fppkg configs. I ran the samplecfg, which said it would create ~/.fpc.cfg, ~/.fp, ... Then the error was gone. I restored the files from backup. Initial dialog pops up with

Re: [fpc-pascal] bug in make install ?

On 3/18/19 11:21 PM, Mattias Gaertner via fpc-pascal wrote: On Mon, 18 Mar 2019 22:04:17 +0100 Joost van der Sluis wrote: Definitely. It would be even better to tell the full file name. e.g. /etc/fpcpkg.cfg. Problem is that it could also be in the fppkg-compiler configuration file (by

Re: [fpc-pascal] bug in make install ?

On Mon, 18 Mar 2019 22:04:17 +0100 Joost van der Sluis wrote: >[...] > > If fppkg.cfg is the cause, why does the Lazarus initial setup not > > tell this? > > I found it difficult to come up with a descriptive message. > > Do you think that "fppkg.cfg" is better then "fppkg configuration"?

Re: [fpc-pascal] bug in make install ?

Op 18-03-19 om 18:20 schreef Mattias Gaertner via fpc-pascal: On Mon, 18 Mar 2019 17:02:35 +0100 Joost van der Sluis wrote: Op 15-03-19 om 22:48 schreef Mattias Gaertner via fpc-pascal: How to install fpc 3.3.1? When I use make install under Linux, Lazarus complains: Error: the Fppkg

Re: [fpc-pascal] bug in make install ?

On Mon, 18 Mar 2019 17:02:35 +0100 Joost van der Sluis wrote: > Op 15-03-19 om 22:48 schreef Mattias Gaertner via fpc-pascal: > > How to install fpc 3.3.1? > > > > When I use make install under Linux, Lazarus complains: > > Error: the Fppkg configuration is corrupt. > > > > I can compile

Re: [fpc-pascal] bug in make install ?

Op 15-03-19 om 22:48 schreef Mattias Gaertner via fpc-pascal: How to install fpc 3.3.1? When I use make install under Linux, Lazarus complains: Error: the Fppkg configuration is corrupt. I can compile everything without errors. "Make install" does not create any configuration-files (like

[fpc-pascal] bug in make install ?

Hi, How to install fpc 3.3.1? When I use make install under Linux, Lazarus complains: Error: the Fppkg configuration is corrupt. I can compile everything without errors. Mattias ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org

Re: [fpc-pascal] Bug in documentation for Random?

On 05/04/17 17:55, Bart wrote: > http://docwiki.embarcadero.com/RADStudio/Tokyo/en/Random > > "random returns a random number between 0 and abs(num-1)" > > IIUC, then Random() shoud always return a positive number. > Mmm, I don't think so: For y := Random(num); the unsigned value of 'y' will

Re: [fpc-pascal] Bug in documentation for Random?

Usualy "non-negative", not positive ! Cheers, Ched' Le 05.04.2017 à 16:55, Bart a écrit : http://docwiki.embarcadero.com/RADStudio/Tokyo/en/Random "random returns a random number between 0 and abs(num-1)" IIUC, then Random() shoud always return a positive number. Bart

Re: [fpc-pascal] Bug in documentation for Random?

http://docwiki.embarcadero.com/RADStudio/Tokyo/en/Random "random returns a random number between 0 and abs(num-1)" IIUC, then Random() shoud always return a positive number. Bart ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org

Re: [fpc-pascal] Bug in documentation for Random?

Fun fact: TP's random used an unsigned parameter (word), so no ambiguity there. Random (function) -- Returns a random number. Declaration: function Random [ ( Range: Word) ]: < Same type as parameter >; Bart ___ fpc-pascal maillist

Re: [fpc-pascal] Bug in documentation for Random?

On 4/5/17, Santiago A. wrote: > random(-10) > will output numbres -9..0 That was not realy the question. The question is wether the documentation is wrong, or the implementation or neither. B.t.w. Delphi7 gives me: Random(-10) = -776108169 Random(-10) = 244426112

Re: [fpc-pascal] Bug in documentation for Random?

Il 05/04/2017 18:09, Bart ha scritto: http://www.freepascal.org/docs-html/current/rtl/system/random.html "Random returns a random number larger or equal to 0 and strictly less than L" However random(a negative number) returns a number <= 0 and > L program r; begin randomize;

Re: [fpc-pascal] Bug in documentation for Random?

El 05/04/2017 a las 18:09, Bart escribió: > http://www.freepascal.org/docs-html/current/rtl/system/random.html > > "Random returns a random number larger or equal to 0 and strictly less than L" > > However random(a negative number) returns a number <= 0 and > L > > > program r; > begin >

[fpc-pascal] Bug in documentation for Random?

http://www.freepascal.org/docs-html/current/rtl/system/random.html "Random returns a random number larger or equal to 0 and strictly less than L" However random(a negative number) returns a number <= 0 and > L program r; begin randomize; writeln('Random(-10) = ',Random(-10)); end.

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

Am 24.02.2016 16:44 schrieb "Mark Morgan Lloyd" < markmll.fpc-pas...@telemetry.co.uk>: > > Bo Berglund wrote: >> >> On Tue, 23 Feb 2016 23:58:37 +0100, Sven Barth >> wrote: >>> >>> What would really help here would be the warning that Jonas mentioned... >>> For the

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

Am 24.02.2016 12:30 schrieb "Bo Berglund" : > > On Tue, 23 Feb 2016 23:58:37 +0100, Sven Barth > wrote: > > > >What would really help here would be the warning that Jonas mentioned... > >For the above you could just use a local variable and be

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

Bo Berglund wrote: On Tue, 23 Feb 2016 23:58:37 +0100, Sven Barth wrote: What would really help here would be the warning that Jonas mentioned... For the above you could just use a local variable and be done with it. No need to try to "fix" the with-statement. I

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

etrusco wrote > I loved 'with' while I was learning Delphi/Pascal and hated after the > first few months since using it professionaly. I truly believe it > warrants/deserves some advice in the documentation, for the beginners. > With the code completion in Lazarus there's even less reason to use

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

On Wed, Feb 24, 2016 at 9:00 AM, Michael Van Canneyt wrote: > > > On Wed, 24 Feb 2016, Flávio Etrusco wrote: > >> On Wed, Feb 24, 2016 at 8:39 AM, Marco van de Voort >> wrote: >>> >>> In our previous episode, Mark Morgan Lloyd said: > (remember

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

Good, I see yours points. Not so impressed, don't really share. The community spirit does not inspire confidence. I stay with FPC/Lazarus for some fun projects like FBProfiler (https://sourceforge.net/projects/fbprofiler/) but for "real world programs" the migration is canceled until better

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

On Wed, 24 Feb 2016, Flávio Etrusco wrote: On Wed, Feb 24, 2016 at 8:39 AM, Marco van de Voort wrote: In our previous episode, Mark Morgan Lloyd said: > (remember recent discussion about IfThen pseudo-function). More relevant to your situation, I remember discussion about

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

On Wed, Feb 24, 2016 at 8:39 AM, Marco van de Voort wrote: > In our previous episode, Mark Morgan Lloyd said: >> > (remember recent discussion about IfThen pseudo-function). >> >> More relevant to your situation, I remember discussion about adding an >> identifier to WITH to use

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

In our previous episode, Mark Morgan Lloyd said: > > (remember recent discussion about IfThen pseudo-function). > > More relevant to your situation, I remember discussion about adding an > identifier to WITH to use as an explicit shortcut, i.e. something like > > with foo= bar do >

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

On Tue, 23 Feb 2016 23:58:37 +0100, Sven Barth wrote: > >What would really help here would be the warning that Jonas mentioned... >For the above you could just use a local variable and be done with it. No >need to try to "fix" the with-statement. I really fully

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

Am 23.02.2016 23:28 schrieb "Mark Morgan Lloyd" < markmll.fpc-pas...@telemetry.co.uk>: > > Serguei TARASSOV wrote: > >> There is no perfect way so why the language extension is the safest >> (remember recent discussion about IfThen pseudo-function). > > > More relevant to your situation, I

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

Serguei TARASSOV wrote: There is no perfect way so why the language extension is the safest (remember recent discussion about IfThen pseudo-function). More relevant to your situation, I remember discussion about adding an identifier to WITH to use as an explicit shortcut, i.e. something like

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

On 23.02.2016 17:21, Serguei TARASSOV wrote: > Michael Van Canneyt wrote >> I hope you will send the same mail to embarcadero/Idera. >> When they added methods to TPoint, they broke have the VCL code ? >> >> To avoid this, we would need to freeze the code as soon as it is released. > > Compared

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

Michael Van Canneyt wrote > I hope you will send the same mail to embarcadero/Idera. > When they added methods to TPoint, they broke have the VCL code ? > > To avoid this, we would need to freeze the code as soon as it is released. Compared with Unicode migration, introducing the methods into

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

On 2016-02-23 14:13, Mark Morgan Lloyd wrote: > And the extra typechecks etc. mean that FPC is a bit better than most > language implementations at catching things like that. Exactly. I prefer getting an error so I can fix my code and know it will work as intended - instead of the compiler

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

Graeme Geldenhuys wrote: On 2016-02-23 10:54, Serguei TARASSOV wrote: I see, but *it's not my code*, its a code of the big third-party framework that is working well with all version of Delphi/C++ builder and Lazarus 1.x with FPC 2.6.4. Well, now it doesn't work with FPC 3.0. ;-) You

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

I have the latest version of Devart pgdac and virtualtable.pas compiles fine. On Feb 23, 2016 3:33 AM, "Serguei TARASSOV" wrote: > Hello, > > Sorry, my previous example was not complete. > Here is a problem detected when compiling UniDAC 6.2.8. > Taken from real code in

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

Henry Vermaak wrote on Tue, 23 Feb 2016: On Tue, Feb 23, 2016 at 02:13:52PM +0100, Jonas Maebe wrote: It would probably be useful if we added support to the compiler to generate a warning (or even error) in case a with statement hides an existing symbol in scope though. Yes, please.

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

On Tue, Feb 23, 2016 at 02:13:52PM +0100, Jonas Maebe wrote: > It would probably be useful if we added support to the compiler to > generate a warning (or even error) in case a with statement hides an > existing symbol in scope though. Yes, please. Something like -Wshadow would be very useful.

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

On Tue, 23 Feb 2016, Serguei TARASSOV wrote: Okay, okay, I see. For info, the indicated error is not critical because of its visibility at compile-time. All other codes inside "with" statement like x := FieldDef; will be compiled without errors and should be checked. Thank you, guys, for a

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

Serguei TARASSOV wrote on Tue, 23 Feb 2016: Thank you, guys, for a good compatibility support Come on. The only way this kind of problems can be avoided is by us never adding any new field or property to any class, ever. It would probably be useful if we added support to the compiler to

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

Okay, okay, I see. For info, the indicated error is not critical because of its visibility at compile-time. All other codes inside "with" statement like x := FieldDef; will be compiled without errors and should be checked. Thank you, guys, for a good compatibility support and adding the

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

On Tue, 23 Feb 2016, Graeme Geldenhuys wrote: On 2016-02-23 10:54, Serguei TARASSOV wrote: I see, but *it's not my code*, its a code of the big third-party framework that is working well with all version of Delphi/C++ builder and Lazarus 1.x with FPC 2.6.4. Well, now it doesn't work with

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

On 2016-02-23 10:54, Serguei TARASSOV wrote: > I see, but *it's not my code*, its a code of the big third-party framework > that is working well with all version of Delphi/C++ builder and Lazarus 1.x > with FPC 2.6.4. Well, now it doesn't work with FPC 3.0. ;-) > You cannot recommend them to

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

On Tue, 23 Feb 2016, Serguei TARASSOV wrote: Michael Van Canneyt wrote The problem is in your code and the use of WITH, as I surmised in my previous mail. In 2.6.4, FieldDef is resolved to the LOCAL VARIABLE FieldDef. The code compiles ok. In 3.0.0, FieldDef is a NEW READ-ONLY property in

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

Michael Van Canneyt wrote > The problem is in your code and the use of WITH, as I surmised in my > previous mail. > > In 2.6.4, FieldDef is resolved to the LOCAL VARIABLE FieldDef. > The code compiles ok. > > In 3.0.0, FieldDef is a NEW READ-ONLY property in TField. > Because of the WITH, the

Re: [fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

On Tue, 23 Feb 2016, Serguei TARASSOV wrote: Hello, Sorry, my previous example was not complete. Here is a problem detected when compiling UniDAC 6.2.8. Taken from real code in VirtualTable.pas program Project1; {$MODE DELPHI} uses SysUtils, Classes, DB; procedure

[fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

Hello, Sorry, my previous example was not complete. Here is a problem detected when compiling UniDAC 6.2.8. Taken from real code in VirtualTable.pas program Project1; {$MODE DELPHI} uses SysUtils, Classes, DB; procedure InternalCreateFieldDefs(Fields: TFields; FieldDefs: TFieldDefs); var

Re: [fpc-pascal] Bug in FPC 3.0?

Error: (3059) No member is provided to access property is because TField.FieldDef is defined like: Property FieldDef : TFieldDef Read FFieldDef; so there is no write method from begining (2 years ago rev. 26776). Error: (5000) Identifier not found "FieldDefs" FieldDefs is property of

Re: [fpc-pascal] Bug in FPC 3.0?

On Mon, 22 Feb 2016, Serguei TARASSOV wrote: Michael Van Canneyt wrote On Mon, 22 Feb 2016, Serguei TARASSOV wrote: Hello, UniDAC doesn't compile with Lazarus 1.6/FPC 3.0. The case may be reproduced on following example. To my knowledge, this has never worked. Michael. History log is

Re: [fpc-pascal] Bug in FPC 3.0?

Michael Van Canneyt wrote > On Mon, 22 Feb 2016, Serguei TARASSOV wrote: > >> Hello, >> >> UniDAC doesn't compile with Lazarus 1.6/FPC 3.0. >> The case may be reproduced on following example. > > To my knowledge, this has never worked. > > Michael. History log is below :) UniDAC 6.1 compiles

  1   2   >