Re: [fpc-pascal] WinCE multithreading
Patch for FPC-RTL: http://bugs.freepascal.org/view.php?id=20280 The best regards, Fabio Luis Girardi PascalSCADA Project http://sourceforge.net/projects/pascalscada http://www.pascalscada.com ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] WinCE multithreading
Hi! I submitted two patches that solves multi threading issues on WinCE (one on Lazarus LCL, other on FPC RTL) http://bugs.freepascal.org/view.php?id=18756 After the patches, all examples works as expected. The best regards, Fabio Luis Girardi PascalSCADA Project http://sourceforge.net/projects/pascalscada http://www.pascalscada.com ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Linux - ExecuteProcess versus fpSystem
Marco van de Voort: > So basically this bugreport is about adding *nix > shell quoting to a routine that was meant to mimic > WINDOWS API (iow not even Windows shell) be- > haviour. I only wanted to fix the parsing of partially quoted parameters. Of course, it is best to deprecate this function and avoid all confusion. Anton ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Linux - ExecuteProcess versus fpSystem
In our previous episode, cobines said: > > I have created issue # 0020279. > > If this must be like shell quoting These routines were never meant to be shell quoting (which is silly since it is a Runtime lib call, not a shell). I also don't see the point why it should be expanded to do shell quoting. The original executeprocess was made as replacement for dos.exec, which was before 1.9.2 the only portable way to call a function, but had a 255 char limit. The original string,string version of executeprocess solved that, and to better suit Unix, a version with an open array was made because it suits Unix api conventions (execve) more, and because since the Unix restructure that option was open. So basically this bugreport is about adding *nix shell quoting to a routine that was meant to mimic WINDOWS API (iow not even Windows shell) behaviour. Some minor quoting support that was already there was added for easy conversion, but I'm very reluctant to expand that and get even more corner cases. I added comments to that end to above bugreport. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Linux - ExecuteProcess versus fpSystem
2011/9/17 Anton Shepelev : > Felipe Monteiro de Carvalho: > >> If FPC Trunk also does not support this, then I'm >> sure a patch to improve StringToPPChar would be >> welcome. > > I have created issue # 0020279. If this must be like shell quoting then you also need to allow quoting with backslash, inside single quotes escaping is not allowed and not mix single and double quotes. For example: param\ eter1 'param\"'eter2' param"eter3' "parameter'4" should do: 1: param eter1 2: param\"eter2 param"eter3 3: parameter'4 There is a good guide here which I used for similar purpose: http://www.grymoire.com/Unix/Quote.html -- cobines ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Linux - ExecuteProcess versus fpSystem
Felipe Monteiro de Carvalho: > If FPC Trunk also does not support this, then I'm > sure a patch to improve StringToPPChar would be > welcome. I have created issue # 0020279. Anton ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
