In our previous episode, leledumbo said:
So I ask: what's the correct code to inform as argument a TProcess and
a instruction string and as a return, to get the output string?
If very up to date FPC 2.7.1:
var s : ansistring;
if RunCommand(binaryname,['arg1','arg2'],s) then
begin
//
WUAOOOW!!! Where are those functions, Marco? Which revision implements them?
And last but not least, do those functions consider BIG output?
--
View this message in context:
http://free-pascal-general.1045716.n5.nabble.com/Getting-an-output-string-from-a-TProcess-tp5709934p5709940.html
Sent from
I saw a big commit merging jvmbackend branch into the main branch. Is it
stable already? I currently have both from svn, if it's already stable I'm
planning on deleting the jvmbackend only.
--
View this message in context:
In our previous episode, leledumbo said:
WUAOOOW!!! Where are those functions, Marco?
In 2.7.1 (trunk)
Which revision implements them?
r21437
And last but not least, do those functions consider BIG output?
Yes. As said in the original message, the base is the large output wiki
source.
In 2.7.1 (trunk)
I mean... which unit?
--
View this message in context:
http://free-pascal-general.1045716.n5.nabble.com/Getting-an-output-string-from-a-TProcess-tp5709934p5709943.html
Sent from the Free Pascal - General mailing list archive at Nabble.com.
On Sat, 2 Jun 2012, leledumbo wrote:
In 2.7.1 (trunk)
I mean... which unit?
process.
Michael.
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
On 02 Jun 2012, at 16:26, leledumbo wrote:
I saw a big commit merging jvmbackend branch into the main branch. Is it
stable already?
It's as stable as the jvmbackend branch was (with even already some extra fixes
in the mean time), so there's no problem with deleting your checkout of the
2012/5/31 Bernd prof7...@googlemail.com:
I would like to propose something like this as a patch against
[...]
lNet to make the TLSelectEventer work the same way on all
supported platforms
Almindor committed it to trunk :-)
Now we can have non-LCL TCP servers with up to 1023 concurrent