Re: [fpc-pascal] MS DOS 8086 compiler?

2013-04-28 Thread Mark Morgan Lloyd
Bart wrote: On 4/27/13, Reinier Olislagers reinierolislag...@gmail.com wrote: Noticed that an 8086 branch was merged to fpc trunk. Is it time to get out some 5.25 diskettes[1]? [1] Shame I dumped all the accompanying hardware long ago ;) Perhaps break out DOSBOX ;) I still have a portable

Re: [fpc-pascal] Windows backslash

2013-04-28 Thread Bart
On 4/22/13, Mattias Gaertner nc-gaert...@netcologne.de wrote: 'make' writes the right file name. Next thing is FPC and that uses the wrong path. So either 'make' is lying or FPC alters the path. In either case it is more a FPC issue than a Lazarus issue. The bug report should be moved to

Re: [fpc-pascal] MS DOS 8086 compiler?

2013-04-28 Thread Nikolay Nikolov
On 04/28/2013 12:00 PM, Mark Morgan Lloyd wrote: Bart wrote: On 4/27/13, Reinier Olislagers reinierolislag...@gmail.com wrote: Noticed that an 8086 branch was merged to fpc trunk. Is it time to get out some 5.25 diskettes[1]? [1] Shame I dumped all the accompanying hardware long ago ;)

Re: [fpc-pascal] Windows backslash

2013-04-28 Thread Marco van de Voort
In our previous episode, Bart said: the wrong path. So either 'make' is lying or FPC alters the path. In either case it is more a FPC issue than a Lazarus issue. The bug report should be moved to FPC. The compiler does not seem to have problems with constructs like: fpc

Re: [fpc-pascal] Windows backslash

2013-04-28 Thread Bart
On 4/28/13, Marco van de Voort mar...@stack.nl wrote: Maybe the ^-as-an-escape is a shell-only convention. The compiler doesn't work through the shell. Make probably does. But then the shell would make it \-\. Converting SomePath\^-^\SomePath into SomePath^-^\SomePath looks more like C...

Re: [fpc-pascal] Windows backslasht

2013-04-28 Thread Marco van de Voort
In our previous episode, Bart said: But then the shell would make it \-\. Converting SomePath\^-^\SomePath into SomePath^-^\SomePath looks more like C... Make could also be doing own substitutions, so is not a good testing platform to draw conclusions off. Note that I haven't tested that

Re: [fpc-pascal] Windows backslash

2013-04-28 Thread Bart
On 4/28/13, Bart bartjun...@gmail.com wrote: Someone should be brave enought to try and replicate/confirm the described problem. Just did that, and indeed the error occurred. So, confirmed. Bart ___ fpc-pascal maillist -

Re: [fpc-pascal] MS DOS 8086 compiler?

2013-04-28 Thread Mark Morgan Lloyd
Nikolay Nikolov wrote: So in practical terms, a strict 8086 port is probably untestable. But why would anybody want to when even embedded processors are based on a newer architecture? Actually, I have a vintage IBM PC 5150, with a 4.77 MHz 8088 processor, so this isn't true, it's very

Re: [fpc-pascal] [OT] Pascal compiler for embedded platforms

2013-04-28 Thread greim
Hi, http://www.astrobe.com/default.htm Oberon on ARM. I think its worth to try it! Markus Greim Am 19.03.2013 08:46, schrieb Martin Schreiber: On Tuesday 19 March 2013 08:11:49 Justin Smyth wrote: Thanks, i am waiting to hear back regarding some suggest changes that were suggest in the

Re: [fpc-pascal] [OT] Pascal compiler for embedded platforms

2013-04-28 Thread Michael Ring
Hmmm I read through the web-page, one thing I could not find is support for real debugging (singlestepping, show registers) in ide, they only seem to provide log message capture. Without a real debugger it is for me not worth the download. I might of course be wrong, did you already test

Re: [fpc-pascal] MS DOS 8086 compiler?

2013-04-28 Thread Marco van de Voort
In our previous episode, Mark Morgan Lloyd said: Actually, I have a vintage IBM PC 5150, with a 4.77 MHz 8088 processor, so this isn't true, it's very testable actually :) However, the i8086 code generator still generates some 186/286+ instructions, so it doesn't work there yet, but I'm

Re: [fpc-pascal] MS DOS 8086 compiler?

2013-04-28 Thread Mark Morgan Lloyd
Marco van de Voort wrote: In our previous episode, Mark Morgan Lloyd said: Actually, I have a vintage IBM PC 5150, with a 4.77 MHz 8088 processor, so this isn't true, it's very testable actually :) However, the i8086 code generator still generates some 186/286+ instructions, so it doesn't

Re: [fpc-pascal] Windows backslash

2013-04-28 Thread Sven Barth
On 28.04.2013 13:31, Marco van de Voort wrote: In our previous episode, Bart said: the wrong path. So either 'make' is lying or FPC alters the path. In either case it is more a FPC issue than a Lazarus issue. The bug report should be moved to FPC. The compiler does not seem to have problems

Re: [fpc-pascal] Windows backslash

2013-04-28 Thread Sven Barth
On 28.04.2013 21:03, Sven Barth wrote: Note 2: Maybe the PowerShell will have a bit different rules, I don't know... The PowerShell uses ` (back quote) as escape character... Regards, Sven ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org

Re: [fpc-pascal] Windows backslash

2013-04-28 Thread Tomas Hajny
On 28 Apr 13, at 21:03, Sven Barth wrote: . . As a sidenote: I didn't know up to now that the prompt in the NT shell can also be modified O.o . . Setting the PROMPT variable works for all DOS-like platforms (MS-DOS and compatibles, OS/2 and MS Windows NT+ and also replacement shells like

[fpc-pascal] Problems with ImageMagick Win64

2013-04-28 Thread Andrew Brunner
Current FPC/Trunk running on Win64 XP I can't get ImageMagick unit to work under Windows XP 64. I changed Win32 to Windows {$ifdef Windows} MagickExport = 'CORE_RL_magick_.dll'; WandExport = 'CORE_RL_wand_.dll'; {$else} MagickExport = 'libMagickCore'; WandExport = 'libMagickWand'; //

Re: [fpc-pascal] How to detect connection status of a socket

2013-04-28 Thread Ewald
On 22 Apr 2013, at 15:10, Xiangrong Fang wrote: 1) fpsend() just pass data to the OS's socket layer without try to determine if the connection is still alive, right? I suppose, but there exists an error code that might come in handy: ENotConn (see http://linux.die.net/man/2/send), which is

Re: [fpc-pascal] Problems with ImageMagick Win64

2013-04-28 Thread Andrew Brunner
On 04/28/2013 02:49 PM, Andrew Brunner wrote: I can't get ImageMagick unit to work under Windows XP 64. Also, I have confirmed that ImageMagick installed and the application does work. Can someone please edit change the unit code for Windows instead of Win32? The libraries are identical for