Re: [fpc-pascal] Re: fcl-passrc package question about source file and line number info

2012-07-18 Thread Michael Van Canneyt
On Wed, 18 Jul 2012, Seth Grover wrote: Hm, it's still failing for me. Here's what I get with test_parser from examples given this input: [] I'm doing it in Linux compiling for x86_64. There wouldn't be any problem with me using this package source (pastree, paswrite, pparser, pscanner) w

Re: [fpc-pascal] Inter-process communication, a cautionary tale

2012-07-18 Thread Mark Morgan Lloyd
Michael Van Canneyt wrote: I meant the SimpleIPC unit from the FCL: http://lazarus-ccr.sourceforge.net/docs/fcl/simpleipc/index.html Because I was exploring various unix-domain socket aspects including mtu, where they're put, how to recover if an inactive one's already there (e.g. gdb failur

[fpc-pascal] Re: fcl-passrc package question about source file and line number info

2012-07-18 Thread Seth Grover
Hm, it's still failing for me. Here's what I get with test_parser from examples given this input: === unit timelib; {$mode objfpc}{$H+} interface implementation procedure SmonthToCmonth (const sMonth : array of char; c

[fpc-pascal] Re: fcl-passrc package question about source file and line number info

2012-07-18 Thread Seth Grover
> Works fine here. > Michael. Hm, that's odd. I'll do a clean pull and clean build and let you know. Thanks. -SG -- This email is fiction. Any resemblance to actual events or persons living or dead is purely coincidental. Seth Grover ___ fpc-pascal ma

Re: [fpc-pascal] Inter-process communication, a cautionary tale

2012-07-18 Thread Michael Van Canneyt
On Wed, 18 Jul 2012, Mark Morgan Lloyd wrote: michael.vancann...@wisa.be wrote: On Wed, 18 Jul 2012, Mark Morgan Lloyd wrote: michael.vancann...@wisa.be wrote: No need to apologize, I'm just curious where you got your info from. The implementation has been the same since day 1, which mean

Re: [fpc-pascal] Re: fcl-passrc package question about source file and line number info

2012-07-18 Thread Michael Van Canneyt
On Wed, 18 Jul 2012, Seth Grover wrote: Michael, I pulled down your latest revision (21934) which did fix the problems I had reported. Thanks! I did find another one for you: unit timelib; {$mode objfpc}{$H+} interface implementation procedure Smo

Re: [fpc-pascal] Inter-process communication, a cautionary tale

2012-07-18 Thread Mark Morgan Lloyd
michael.vancann...@wisa.be wrote: On Wed, 18 Jul 2012, Mark Morgan Lloyd wrote: michael.vancann...@wisa.be wrote: No need to apologize, I'm just curious where you got your info from. The implementation has been the same since day 1, which means your statement puzzles me. So instead of re-i

Re: [fpc-pascal] Inter-process communication, a cautionary tale

2012-07-18 Thread Mark Morgan Lloyd
OBones wrote: Mark Morgan Lloyd wrote: Basically, what I was trying to do was this. In the main thread: fIpcPipe:= CreateNamedPipe(PChar(fIpcName), PIPE_ACCESS_INBOUND, PIPE_TYPE_MESSAGE + PIPE_READMODE_MESSAGE, 1, 0, 0, 1000, NIL (* @

[fpc-pascal] Re: fcl-passrc package question about source file and line number info

2012-07-18 Thread Seth Grover
Michael, I pulled down your latest revision (21934) which did fix the problems I had reported. Thanks! I did find another one for you: unit timelib; {$mode objfpc}{$H+} interface implementation procedure SmonthToCmonth (const sMonth : array of char;

Re: [fpc-pascal] Inter-process communication, a cautionary tale

2012-07-18 Thread michael . vancanneyt
On Wed, 18 Jul 2012, Mark Morgan Lloyd wrote: michael.vancann...@wisa.be wrote: No need to apologize, I'm just curious where you got your info from. The implementation has been the same since day 1, which means your statement puzzles me. So instead of re-inventing the wheel, maybe have a

Re: [fpc-pascal] Inter-process communication, a cautionary tale

2012-07-18 Thread OBones
Mark Morgan Lloyd wrote: Basically, what I was trying to do was this. In the main thread: fIpcPipe:= CreateNamedPipe(PChar(fIpcName), PIPE_ACCESS_INBOUND, PIPE_TYPE_MESSAGE + PIPE_READMODE_MESSAGE, 1, 0, 0, 1000, NIL (* @sa *) ); That

Re: [fpc-pascal] Inter-process communication, a cautionary tale

2012-07-18 Thread Mark Morgan Lloyd
michael.vancann...@wisa.be wrote: No need to apologize, I'm just curious where you got your info from. The implementation has been the same since day 1, which means your statement puzzles me. So instead of re-inventing the wheel, maybe have a closer look again at the standard IPC mechanisms.

Re: [fpc-pascal] Inter-process communication, a cautionary tale

2012-07-18 Thread Mark Morgan Lloyd
OBones wrote: Mark Morgan Lloyd wrote: A couple of weeks ago, out of curiosity rather than necessity, I started looking at whether the library could be ported to Windows using MS-style named pipes. However I seem to have hit a snag since it appears that Windows can't both create a named pipe (

Re: [fpc-pascal] Inter-process communication, a cautionary tale

2012-07-18 Thread michael . vancanneyt
On Wed, 18 Jul 2012, Mark Morgan Lloyd wrote: michael.vancann...@wisa.be wrote: On Wed, 18 Jul 2012, Mark Morgan Lloyd wrote: I was reminded of this when somebody was asking about portable signalling APIs the other day, but I think it's also relevant to discussion of e.g. how to pass a key

Re: [fpc-pascal] Inter-process communication, a cautionary tale

2012-07-18 Thread Mark Morgan Lloyd
michael.vancann...@wisa.be wrote: On Wed, 18 Jul 2012, Mark Morgan Lloyd wrote: I was reminded of this when somebody was asking about portable signalling APIs the other day, but I think it's also relevant to discussion of e.g. how to pass a keyword to a help viewer. I am obviously aware of t

Re: [fpc-pascal] Inter-process communication, a cautionary tale

2012-07-18 Thread michael . vancanneyt
On Wed, 18 Jul 2012, Mark Morgan Lloyd wrote: I was reminded of this when somebody was asking about portable signalling APIs the other day, but I think it's also relevant to discussion of e.g. how to pass a keyword to a help viewer. I am obviously aware of the fact that FPC has an IPC unit

Re: [fpc-pascal] Inter-process communication, a cautionary tale

2012-07-18 Thread OBones
Mark Morgan Lloyd wrote: A couple of weeks ago, out of curiosity rather than necessity, I started looking at whether the library could be ported to Windows using MS-style named pipes. However I seem to have hit a snag since it appears that Windows can't both create a named pipe (for reading) an

[fpc-pascal] Inter-process communication, a cautionary tale

2012-07-18 Thread Mark Morgan Lloyd
I was reminded of this when somebody was asking about portable signalling APIs the other day, but I think it's also relevant to discussion of e.g. how to pass a keyword to a help viewer. I am obviously aware of the fact that FPC has an IPC unit which uses a temporary file, although I have alwa