[fpc-devel] Use case ... ( Respect )

Hi all, today was "one of those days" in work. We had some issues with one branche office and we needed to send a team to do a new inventory report. But we used all the available licenses from the warehouse inventory module in our ERP and there wasn't any handheld device with software loa

Re: [fpc-devel] Problems with rapid fpSend calls on x64 Ubuntu 10.10 (updated)

> > (and look on internet for the meaning of the MSG_NOSIGNAL flag :) ) > > Michael. > Thanks Michael. That did the trick. But sooner or later I'm going to need to switch from polling to events... ___ fpc-devel maillist - fpc-devel@lists.freepascal

Re: [fpc-devel] Console IO revisited

Thaddy wrote: On 3-12-2010 13:52, Michael Van Canneyt wrote: As said in my other mail: The behaviour of Input, Output, StdErr is not governed by OS rules, but by the pascal standard. Michael. My understanding has always been that the PASCAL syntax allowed for console IO in a way that enca

Re: [fpc-devel] Console IO revisited

Op Fri, 3 Dec 2010, schreef Thaddy: On 3-12-2010 15:50, Daniël Mantione wrote: Could you maybe specify what you want to achieve and in what way FPC requires you to use workaround hacks? Daniël Yes, In FPC the console IO is *always* redirected, be it through a handle or a named file.

Re: [fpc-devel] Console IO revisited

Am 03.12.2010 16:11, schrieb Thaddy: > On 3-12-2010 15:50, Daniël Mantione wrote: >> >> Could you maybe specify what you want to achieve and in what way FPC >> requires you to use workaround hacks? >> >> Daniël > Yes, > > In FPC the console IO is *always* redirected, be it through a handle or > a

Re: [fpc-devel] Console IO revisited

On 3-12-2010 15:50, Daniël Mantione wrote: Could you maybe specify what you want to achieve and in what way FPC requires you to use workaround hacks? Daniël Yes, In FPC the console IO is *always* redirected, be it through a handle or a named file. The named file is expected to be independe

Re: [fpc-devel] Console IO revisited

Am 03.12.2010 13:22, schrieb Thaddy: Sorry if this is already picked up as it IMHO should have been. I missed some mails due to a server crash. Today I encountered a similar issue with using threadvars for the input, output and err variables in system when trying to use the input as a win32 sync

Re: [fpc-devel] Console IO revisited

Op Fri, 3 Dec 2010, schreef Thaddy: If you all say no, I will live with it. Could you maybe specify what you want to achieve and in what way FPC requires you to use workaround hacks? Daniël___ fpc-devel maillist - fpc-devel@lists.freepascal.or

Re: [fpc-devel] Console IO revisited

On 3-12-2010 13:52, Michael Van Canneyt wrote: As said in my other mail: The behaviour of Input, Output, StdErr is not governed by OS rules, but by the pascal standard. Michael. My understanding has always been that the PASCAL syntax allowed for console IO in a way that encapsulates the co

Re: [fpc-devel] Console IO revisited

Note the console IO functions are *as I read it and can show it* are supposed NOT to share a single handle. Only the use of the std file names should guarantee a common handle and that is where FPC fails my tests. The redirection for other purposes on a OS level call under windows and posix will

Re: [fpc-devel] Console IO revisited

On Fri, 3 Dec 2010, Thaddy wrote: On 3-12-2010 13:38, Michael Van Canneyt wrote: On Fri, 3 Dec 2010, Thaddy wrote: Sorry if this is already picked up as it IMHO should have been. I missed some mails due to a server crash. Today I encountered a similar issue with using threadvars for the

Re: [fpc-devel] Console IO revisited

On Fri, 3 Dec 2010, Thaddy wrote: On 3-12-2010 13:22, Thaddy wrote: --- CreateFile; lpFileName Use the CONIN$ value to specify console input. Use the CONOUT$ value to specify console output. CONIN$ gets a handle to the console input buffer, even if the SetStdHandle function redirects th

Re: [fpc-devel] Console IO revisited

On 3-12-2010 13:38, Michael Van Canneyt wrote: On Fri, 3 Dec 2010, Thaddy wrote: Sorry if this is already picked up as it IMHO should have been. I missed some mails due to a server crash. Today I encountered a similar issue with using threadvars for the input, output and err variables in s

Re: [fpc-devel] Console IO revisited

On Fri, 3 Dec 2010, Thaddy wrote: Sorry if this is already picked up as it IMHO should have been. I missed some mails due to a server crash. Today I encountered a similar issue with using threadvars for the input, output and err variables in system when trying to use the input as a win32 s

Re: [fpc-devel] Console IO revisited

On 3-12-2010 13:22, Thaddy wrote: --- CreateFile; /lpFileName/ Use the CONIN$ value to specify console input. Use the CONOUT$ value to specify console output. CONIN$ gets a handle to the console input buffer, even if the *SetStdHandle*

[fpc-devel] Console IO revisited

Sorry if this is already picked up as it IMHO should have been. I missed some mails due to a server crash. Today I encountered a similar issue with using threadvars for the input, output and err variables in system when trying to use the input as a win32 sync handle with the CreateFile API. Fa

Re: [fpc-devel] 2.5.1 doesn't build

The resourcestrings are in dbconst, and I forgot to commit that. This has been fixed meanwhile. Tnx ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel

Re: [fpc-devel] 2.5.1 doesn't build

On Fri, 3 Dec 2010, Thaddy wrote: There seem to be a couple of stringresources missing in sqldb.pp latest checkout, make clean, make all The resourcestrings are in dbconst, and I forgot to commit that. This has been fixed meanwhile. Michael. ___

Re: [fpc-devel] 2.5.1 doesn't build

2010/12/3 Thaddy : > There seem to be a couple of stringresources missing in sqldb.pp latest > checkout, make clean, make all > > /FPC/2.5.1/packages/fcl-db/units/i386-win32 -di386 -dRELEASE sqldb.pp > sqldb.pp(765,32) Error: Identifier not found "SCommitting" > sqldb.pp(779,37) Error: Identifier n

[fpc-devel] 2.5.1 doesn't build

There seem to be a couple of stringresources missing in sqldb.pp latest checkout, make clean, make all /FPC/2.5.1/packages/fcl-db/units/i386-win32 -di386 -dRELEASE sqldb.pp sqldb.pp(765,32) Error: Identifier not found "SCommitting" sqldb.pp(779,37) Error: Identifier not found "SCommitRetaining"