From: Brian Jones <cbj@gnu.org>
To: "Patrick Ellis" <Patrick.Ellis@sas.com>
Cc: <mauve-discuss@sources.redhat.com>
Subject: Re: Question about PipedInputStream available method
Date: Thu, 06 Mar 2003 04:33:00 -0000 [thread overview]
Message-ID: <m3zno9azd5.fsf@lyta.haphazard.org> (raw)
In-Reply-To: <F2E670D5036BE14E89473A3FAEDE6ACE428FA0@merc18.na.sas.com>
"Patrick Ellis" <Patrick.Ellis@sas.com> writes:
>
> In the gnu/testlet/java/io/PipedStream/Test.java code, there is a
> call to method available() which Returns the number of bytes that
> can be read from this input stream without blocking. The first call
> to the method returns zero which causes the test to fail. Should the
> code be change to harness.check(pis.available() >= 0,
> "available()");
>
>
>
> // Now set up our reader
> PipedInputStream pis = new PipedInputStream();
> pis.connect(pos);
> new Thread(pstw).start();
> harness.check(pis.available() > 0, "available()");
>
> Pat Ellis
> SDE Build and Test Team
> Phone: (919) 531-0355
> R2263 Patrick.Ellis@sas.com
> SAS... The Power to Know
>
>
Check to see if you have updated Mauve since Mark committed this
fix...
2003-02-14 Mark Wielaard <mark@klomp.org>
* gnu/testlet/java/io/PipedStream/PipedStreamTestWriter.java
(ready): New field.
(waitTillReady): New method.
(run): Set ready field.
* gnu/testlet/java/io/PipedStream/Test.java (test): Call waitTillReady
before testing available().
Brian
--
Brian Jones <cbj@gnu.org>
prev parent reply other threads:[~2003-03-06 4:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 22:47 Patrick Ellis
2003-03-06 4:33 ` Brian Jones [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3zno9azd5.fsf@lyta.haphazard.org \
--to=cbj@gnu.org \
--cc=Patrick.Ellis@sas.com \
--cc=mauve-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).