From: "Jeroen Frijters" <jeroen@sumatra.nl>
To: <mauve-discuss@sources.redhat.com>
Subject: Patch: BufferedWriter.Test
Date: Fri, 23 Jul 2004 09:29:00 -0000 [thread overview]
Message-ID: <788B535AB1F9CB49BB9C229372B50ACC10CE73@LEMBU.sumatrasoftware.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 195 bytes --]
Hi,
The attached patch fixes the BufferedWriter test on platforms that don't
use \n as the line.separator.
I would appreciate it if someone would apply it.
Thanks.
Regards,
Jeroen
[-- Attachment #2: BufferedWriter.Test.patch --]
[-- Type: application/octet-stream, Size: 1471 bytes --]
Index: gnu/testlet/java/io/BufferedWriter/Test.java
===================================================================
RCS file: /cvs/mauve/mauve/gnu/testlet/java/io/BufferedWriter/Test.java,v
retrieving revision 1.1
diff -u -r1.1 Test.java
--- gnu/testlet/java/io/BufferedWriter/Test.java 21 Nov 2002 20:48:21 -0000 1.1
+++ gnu/testlet/java/io/BufferedWriter/Test.java 23 Jul 2004 09:27:36 -0000
@@ -41,7 +41,7 @@
String str = "I used to live right behind this super-cool bar in\n" +
"Chicago called Lounge Ax. They have the best music of pretty\n" +
"much anyplace in town with a great atmosphere and $1 Huber\n" +
- "on tap. I go to tons of shows there, even though I moved.\n";
+ "on tap. I go to tons of shows there, even though I moved.";
char[] buf = new char[str.length()];
str.getChars(0, str.length(), buf, 0);
@@ -51,13 +51,14 @@
bw.write(buf, 5, 8);
bw.write(buf, 13, 12);
bw.write(buf[25]);
- bw.write(buf, 26, buf.length - 27);
+ bw.write(buf, 26, buf.length - 26);
bw.newLine(); // newLine()
bw.flush();
bw.close();
String str2 = new String(caw.toCharArray());
- harness.check(str, str2, "Did all chars make it through?");
+ harness.check(str + System.getProperty("line.separator"), str2,
+ "Did all chars make it through?");
harness.debug(str2, false);
}
catch(IOException e)
next reply other threads:[~2004-07-23 9:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 9:29 Jeroen Frijters [this message]
2004-07-23 17:54 ` Thomas Zander
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=788B535AB1F9CB49BB9C229372B50ACC10CE73@LEMBU.sumatrasoftware.com \
--to=jeroen@sumatra.nl \
--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).