Re: [fpc-pascal] FPC 2.6.4 for GO32

A new fpgdb.zip is available in dist/2.6.4/i386-go32v2/separate/ directory. I added a readme.dos containing the changes made to 2.6.4 sources in order to get a “hopefully” fully functional IDE with debugger included. Please test and report, Pierre Muller De : fpc-pascal-boun...

Re: [fpc-pascal] fpc in symlinked directory

On Tue, 25 Mar 2014 21:07:45 +0100 (CET) Michael Van Canneyt wrote: >[...] > > For example a way to tell fpc to use the PWD environment > > variable? > > No. > > Because if you do a Chdir('ABC') inside a FPC program, 'a FPC program' sounds as if you are talking about console programs in genera

Re: [fpc-pascal] fpc in symlinked directory

On Tue, 25 Mar 2014, Mattias Gaertner wrote: Hi, When I start fpc in a directory containing symlinks the compiler uses the resolved directory, leading to wrong source file names. For example: /tmp/orig/project1.pas /tmp/link -> /tmp/orig cd /tmp/link fpc -vb project1.pas /tmp/orig/project1.

[fpc-pascal] fpc in symlinked directory

Hi, When I start fpc in a directory containing symlinks the compiler uses the resolved directory, leading to wrong source file names. For example: /tmp/orig/project1.pas /tmp/link -> /tmp/orig cd /tmp/link fpc -vb project1.pas /tmp/orig/project1.pas(6,5) Error: Identifier not found "w" Is there

Re: [fpc-pascal] FPC 2.6.4 for GO32

I found the cause of the ugly behavior… See http://svn.freepascal.org/cgi-bin/viewvc.cgi?view=revision &revision=27281 It’s astonishing this was not found before… I suspect this is mainly due to the fact that most

Re: [fpc-pascal] TSQLQuery.ApplyUpdates problem with UTF-8

On Tue, 25 Mar 2014, Dennis Poon wrote: By the way, why isn't a semicolon required at the end of SET NAMES 'utf8' command? I tried both with and without semicolon and neither raise an error. Seems, that MySQL is tolerant to this. MySQL supports MULTI_STATEMENTS, which enables client to p

Re: [fpc-pascal] TSQLQuery.ApplyUpdates problem with UTF-8

On Tue, March 25, 2014 09:56, Dennis Poon wrote: > >>> >>> By the way, why isn't a semicolon required at the end of SET NAMES >>> 'utf8' command? I tried both with and without semicolon and neither >>> raise an error. >> Seems, that MySQL is tolerant to this. >> MySQL supports MULTI_STATEMENTS, whi

Re: [fpc-pascal] TSQLQuery.ApplyUpdates problem with UTF-8

By the way, why isn't a semicolon required at the end of SET NAMES 'utf8' command? I tried both with and without semicolon and neither raise an error. Seems, that MySQL is tolerant to this. MySQL supports MULTI_STATEMENTS, which enables client to pass multiple statements separated by ";" in