Re: [fpc-pascal] FPC 3.0.4 released!

On 03/12/17 17:36, Florian Klämpfl wrote: Am 03.12.2017 um 18:20 schrieb kardan: On Fri, 1 Dec 2017 21:02:30 +0100 Florian Klämpfl wrote: And? FPC is not debian/linux only. If you are using windows I recommend to use a one of the many checksum tools to verify

Re: [fpc-pascal] Seek to EOF of file of byte

On 18/11/17 20:27, Mark Morgan Lloyd wrote: because the program is being viewed critically by the ALGOL programmer whose code Algol, one my all time favourite languages. while wend if fi why is this not universally adopted? I still comment my C code with fi's and wend's to keep

Re: [fpc-pascal] FORTRAN from FreePascal

On 18/11/17 20:14, Mark Morgan Lloyd wrote: I think that conventional wisdom is that if somebody's written numerical analysis code you don't change it gratuitously, since any alterations will change rounding errors etc. For some reason, that seems to apply particularly to FORTRAN programs :-)

Re: [fpc-pascal] Problem with array of const

On 29/10/17 00:31, Vojtěch Čihák wrote: Looking to docs: https://www.freepascal.org/docs-html/ref/refsu69.html I tried writeln(AnsiString(args[0].VAnsiString)); or just writeln(String(args[0].VAnsiString)); which works. V. __ >

Re: [fpc-pascal] Problem with array of const

On 29/10/17 00:31, Vojtěch Čihák wrote: Looking to docs: https://www.freepascal.org/docs-html/ref/refsu69.html I tried writeln(AnsiString(args[0].VAnsiString)); or just writeln(String(args[0].VAnsiString)); which works. V. __ >

Re: [fpc-pascal] Overloaded functions

On 28/10/17 23:54, Darius Blaszyk wrote: Thanks! This is in line with what I was suspecting. However, why in the world does the compiler not warn in this case. This should be at least happening I would suppose? Darius Vojtěch Čihák schreef op 28 okt '17: Overloading means that you have

Re: [fpc-pascal] CRT unit and Windows' terminal

On 16/10/17 13:03, James Richters wrote: >Long story short: CRT unit doesn't work at all on Windows, but it works with unicode on Mac/Linux. I’m curious how the CRT unit handles the Extended ASCII codes on Mac and Linux…  All versions should be the same for cross platform compatibility. I

Re: [fpc-pascal] CRT unit and Windows' terminal

On 13/10/17 14:39, James Richters wrote: I‘ve tried Writeln(Chr(9556)) but chr() has a limit of 255, and I’ve tried just Writeln(#9556) and while that compiles and runs, it doesn’t produce the correct character.. I have a feeling (but have not tested it) that it keeps cycling around the first

Re: [fpc-pascal] where's the glyph?

On 11/10/17 13:28, Sven Barth via fpc-pascal wrote: Am 11.10.2017 13:13 schrieb >: > > Hi, > > LCL provides the usual Delphi equivalent components like TBitBtn and TSpeedButton  but there do not seem to be any glyphs to go with them. > >

Re: [fpc-pascal] Const params question

On 11/10/17 13:11, Michael Van Canneyt wrote: Delphi has recently Huh? I thought Delphi got shut down years ago. :? ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] where's the glyph?

On 11/10/17 12:23, Vojtěch Čihák wrote: Hi, TBitBtn has property Kind, setting it to anything else than bkCustom will show the glyph (native, from widgetset). With TSpeedButton, you are always on your own. V. Hi, LCL provides the usual Delphi equivalent components like TBitBtn and

Re: [fpc-pascal] {$DEFINE DEVEL}

On 11/10/17 12:00, Mattias Gaertner wrote: On Wed, 11 Oct 2017 11:45:33 +0100 pasc...@piments.com wrote: [...] It wasn't a reply because they was no Re and it had a new title. I should have deleted the [fpc-pascal] as well . Sorry. A reply is not defined by the title. It is marked by the

[fpc-pascal] where's the glyph?

Hi, LCL provides the usual Delphi equivalent components like TBitBtn and TSpeedButton but there do not seem to be any glyphs to go with them. Do I really have to make my own or are there some resources I have not found ? Thanks. ___ fpc-pascal

[fpc-pascal] {$DEFINE DEVEL}

Hi , I had a little trick that I used on BP and Delphi code that does not work on Lazarus. I define compiler variable which I could toggle on and off by adding a second opening curly bracket, since the define only works if the line starts {$ {$DEFINE DEVEL} If I start the line {{$

Re: [fpc-pascal] alternative name fpc cross

On 10/10/17 13:29, Karoly Balogh (Charlie/SGR) wrote: Linux Subsystem for Windows. While I know what you mean ... I used to be maintainer on Wine AppDB for several years. Nothing ever worked from one release to the next. WINE spent 10y as an alpha release and it started to get

Re: [fpc-pascal] getting cross with the cross compiler

On 10/10/17 10:08, Tony Whyman wrote: On 10/10/17 05:51, pasc...@piments.com wrote: Were it not for the version restrictions in building fpc one could arguably say this was a reasonable assumption.  As it is, it leads to a very confused and confusing state which has taken several days to

Re: [fpc-pascal] alternative name fpc cross

On 10/10/17 11:16, Karoly Balogh (Charlie/SGR) wrote: Hi, On Tue, 10 Oct 2017, turro75 wrote: when I create the cross compiler to arm-android and arm-embedded I get the same compiler name so unable to have both running in the same system. any workaround? The compiler is *NOT* OS/platform

Re: [fpc-pascal] getting cross with the cross compiler

On 10/10/17 10:35, Tony Whyman wrote: On 10/10/17 05:51, pasc...@piments.com wrote: $make all NOGDB=1 OS_TARGET=linux CPU_TARGET=x86_64 INSTALL_PREFIX=/usr Makefile:2914: *** The only supported starting compiler version is 3.0.0. You are trying to build with 3.1.1..  Stop. BTW is 

Re: [fpc-pascal] getting cross with the cross compiler

On 10/10/17 10:08, Tony Whyman wrote: Within the Lazarus parts of the libraries, the Linux libs have the gtk2 interface libraries, while the Windows ones have the win32 interfaces libraries (both win32 and win64). Thanks, that was the missing element. I dropped using gtk2 and it works

Re: [fpc-pascal] getting cross with the cross compiler

On 10/10/17 10:25, Sven Barth via fpc-pascal wrote: Am 10.10.2017 08:08 schrieb >: > $make all         NOGDB=1 OS_TARGET=linux CPU_TARGET=x86_64 INSTALL_PREFIX=/usr > Makefile:2914: *** The only supported starting compiler version is 3.0.0.

Re: [fpc-pascal] compiler option for $J directive

On 08/10/17 21:24, leledumbo via fpc-pascal wrote: There is my old feature request about it https://bugs.freepascal.org/view.php?id=30344 :) You can monitor it. No one seems to care to implement it, so if you badly need it: sj.patch

Re: [fpc-pascal] getting cross with the cross compiler

On 08/10/17 10:12, Tomas Hajny wrote: On Sat, October 7, 2017 22:13, pasc...@piments.com wrote: Hi, . . Can you offer any insights into what is going on with Lazarus not locating the system unit and friends. As you acknowledge they are treated somewhat differently due to problems with

Re: [fpc-pascal] getting cross with the cross compiler

On 07/10/17 19:55, Florian Klämpfl wrote: Am 07.10.2017 um 12:14 schrieb Sven Barth via fpc-pascal: Am 07.10.2017 11:11 schrieb "Karoly Balogh (Charlie/SGR)" >: Hi, On Sat, 7 Oct 2017, Sven Barth via fpc-pascal wrote: So where is

Re: [fpc-pascal] getting cross with the cross compiler

On 07/10/17 11:14, Sven Barth via fpc-pascal wrote: Am 07.10.2017 11:11 schrieb "Karoly Balogh (Charlie/SGR)" >: > > Hi, > > On Sat, 7 Oct 2017, Sven Barth via fpc-pascal wrote: > > > > So where is my cross compiler ?? > > > > >

Re: [fpc-pascal] getting cross with the cross compiler

On 07/10/17 10:01, Sven Barth via fpc-pascal wrote: Am 07.10.2017 10:57 schrieb >: > > Hi, > > I am having trouble getting fpc to cross-compiler for win64 target. > > I'm using fedora 26 which supplies 3.0.2 > > I used instructions here

Re: [fpc-pascal] getting cross with the cross compiler

On 07/10/17 10:01, Sven Barth via fpc-pascal wrote: Am 07.10.2017 10:57 schrieb >: > > Hi, > > I am having trouble getting fpc to cross-compiler for win64 target. > > I'm using fedora 26 which supplies 3.0.2 > > I used instructions here