public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Raif S. Naffah" <raif@fl.net.au>
To: Brian Jones <cbj@gnu.org>
Cc: Mauve <mauve-discuss@sources.redhat.com>
Subject: Re: "a string".getBytes("ASCII")
Date: Tue, 04 Feb 2003 19:36:00 -0000	[thread overview]
Message-ID: <200302050639.27426.raif@fl.net.au> (raw)
In-Reply-To: <m37kcgdwkl.fsf@lyta.haphazard.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

On Wednesday 05 February 2003 00:06, Brian Jones wrote:
> "Raif S. Naffah" <raif@fl.net.au> writes:
> > hello there,
> >
> > the encoding page in the JDK1.4.1 documentation states that "ASCII"
> > is a supported encoding (see
> > <.../docs/guide/intl/encoding.doc.html>).
> >
> > i dont see in the Mauve String test classes any test for things
> > like "a string".getBytes("ASCII") --and more generally getBytes()
> > for supported encodings.
> >
> > is it ok to add some methods to the
> > gnu/testlet/java/lang/String/getBytes.java class to test ASCII and
> > other encodings?  or may be create a new class 'encoding14.java' to
> > test all 1.4 supported encodings?
>
> Probably add to getBytes.java if the TAGS java version is okay in the
> TAGS line, otherwise create a new file with the appropriate TAGS line
> and probably called getBytes<version>.java, such as getBytes14.java.

ok.  i'll submit some code later today or tomorrow for review.


cheers;
rsn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Que du magnifique

iD8DBQE+QBbt+e1AKnsTRiERAxy/AJ9j60YssDWE/8WhjGOm0eMMtmAylACg7S3Y
IEj8+xKEUw8qOYBHfs3yeRc=
=RuWp
-----END PGP SIGNATURE-----

      reply	other threads:[~2003-02-04 19:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-04  8:29 Raif S. Naffah
2003-02-04 19:33 ` Brian Jones
2003-02-04 19:36   ` Raif S. Naffah [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=200302050639.27426.raif@fl.net.au \
    --to=raif@fl.net.au \
    --cc=cbj@gnu.org \
    --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).