OK, I'm stuck. I've read through IPC::Open3 and friends, I've looked through
CPANPLUS, I've tried to solve this problem but no matter how hard I try, while
I can fetch both STDOUT and STDERR, I cannot guarantee that they're in synch.
That's my big problem and
So I'm going to head over to Per
On 9/21/06, Ovid <[EMAIL PROTECTED]> wrote:
OK, I'm stuck. I've read through IPC::Open3 and friends, I've looked through
CPANPLUS, I've tried to solve this problem but no matter how hard I try, while
I can fetch both STDOUT and STDERR, I cannot guarantee that they're in synch.
That's my big
- Original Message
From: demerphq <[EMAIL PROTECTED]>
> There is no problem if you do the backtick method I mentioned.
>
> my $in_sync=`someprocess 2>&1`;
>
> and it should be in sync. I seem to recall it has to be, but i cant
> find the source of that claim. But i know that ive never see
On 9/21/06, Ovid <[EMAIL PROTECTED]> wrote:
- Original Message
From: demerphq <[EMAIL PROTECTED]>
> There is no problem if you do the backtick method I mentioned.
>
> my $in_sync=`someprocess 2>&1`;
>
> and it should be in sync. I seem to recall it has to be, but i cant
> find the sourc
- Original Message
From: demerphq <[EMAIL PROTECTED]>
> Well then forget about synchronized two-channel communications. You
> can't have everything in this world. :-)
Which is why ultimately this needs to be one-channel communication :)
Cheers,
Ovid
--
Buy the book -- http://www.oreil
On 9/21/06, Ovid <[EMAIL PROTECTED]> wrote:
OK, I'm stuck. I've read through IPC::Open3 and friends, I've looked through
CPANPLUS, I've tried to solve this problem but no matter how hard I try, while
I can fetch both STDOUT and STDERR, I cannot guarantee that they're in synch.
That's my big
From: jerry gay <[EMAIL PROTECTED]>
> do you have a test that clearly shows the failure? if so, i can try to
> code up an IPC::Run solution. it shouldn't take me very long to
> determine if it's feasible.
I do have one at home. I'm at work right now, but I'll send it along when I
can.
The majo
(I should have put "Solved" in quotes)
There appears to be a huge amount of disagreement at
http://perlmonks.org/?node_id=574085 regarding how to approach synchronizing
STDERR and STDOUT. While many offer useful suggestions, the suggestions tend
to be rather complicated, might require non-core
From: Ovid <[EMAIL PROTECTED]>
> Unfortunately, I'll have to alter the above to handle versions of
> Test-Simple prior to 0.60 and that sucks, but it also *seems*
> to work flawlessly.
I lied. I examined the code and again and my version appears to work for all
versions of Test::Builder since i
Ovid wrote:
> - Original Message
> From: Michael G Schwern <[EMAIL PROTECTED]>
>
>> Something to consider in all this is that TAPx::Parser
>> needs to know to display what goes to STDERR
>> and suppress what goes to STDOUT. This means
>> you simply can't mash the two streams together,
>>
Ovid wrote:
> You've studiously avoided answering whether or not you would accept a patch
> for Test::Builder
> which would allow STDERR to be sent to STDOUT. I realize Test::Harness can't
> use it, but others
> can. Unless I'm missing something very fundamental, it makes most of my
> problems
Ovid wrote:
> Now I have guaranteed cross-platform behavior, STDERR and STDOUT are
> guaranteed to be in
> synch, this doesn't cause any problems for Test::Harness, I don't need to
> fork Test::Builder
> and I override one method which has not changed since May 2005.
> Unfortunately, I'll have
From: Michael G Schwern <[EMAIL PROTECTED]>
> I will now break your solution.
>
>use Test;
>plan tests => 1;
>ok 23, 42;
>
> PHEAR MY MAD HAX0R SKILLZ!
>
> :P
Hmm, interesting. My parser handled that just fine.
:P
The point isn't that the output comes before or after the test resul
Ovid wrote:
> From: Michael G Schwern <[EMAIL PROTECTED]>
>
>> I will now break your solution.
>>
>>use Test;
>>plan tests => 1;
>>ok 23, 42;
>>
>> PHEAR MY MAD HAX0R SKILLZ!
>>
>> :P
>
> Hmm, interesting. My parser handled that just fine.
Yes, that is interesting. How did it captu
14 matches
Mail list logo
