From: Mark Wielaard <mark@klomp.org>
To: Patrick Ellis <Patrick.Ellis@sas.com>
Cc: mauve-discuss@sources.redhat.com
Subject: Re: Is InputStreamReader.ready method deprecated ?
Date: Tue, 04 Mar 2003 22:22:00 -0000 [thread overview]
Message-ID: <1046816565.14252.62.camel@elsschot> (raw)
In-Reply-To: <F2E670D5036BE14E89473A3FAEDE6ACE428F9A@merc18.na.sas.com>
Hi,
On Tue, 2003-03-04 at 20:49, Patrick Ellis wrote:
> Question: I have a testcase that is failing across several platforms (UNIX, LINUX, WINDOWS, etc) that according to the comment in the code was deprecated after 1.1 but I can NOT find any documentation or statement from the SUN JavaTM 2 Platform, Standard Edition, v 1.4.1 website or any books that say the code should be deprecated for the
> InputStreamReader.ready method . Has the function been deprecated ?
Not to my knowledge.
The test looks strange I would expect the first test to always fail.
But with gcj it actaully doesn't/ Haven't figured out why yet.
Cheers,
Mark
prev parent reply other threads:[~2003-03-04 22:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 19:49 Patrick Ellis
2003-03-04 22:22 ` Mark Wielaard [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=1046816565.14252.62.camel@elsschot \
--to=mark@klomp.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).