Re: String from char[] with null termination.
- From: Chris Smith <cdsmith@xxxxxxx>
- Date: Thu, 12 Jan 2006 13:08:47 -0700
Kevin Podsiadlik <kjp@xxxxxxxxx> wrote:
> I'm relatively new to Java programming, and stumbled across this by
> accident. Consider this code fragment:
>
> char[] ch = { 'A', 'B', 'C', '\0' };
> String s = new String(ch);
> System.out.println(s + "DEF");
>
> Should this print out "ABC" or "ABCDEF"?
>
> When I run it from the command line, the output is "ABCDEF". When I
> run it via the Eclipse 3.1.0 SDK, however, the output is "ABC". The
> java compiler is the same both times, version j2sdk1.4.2_10 on a Red
> Hat Linux system. I can understand how either output might logically
> result, but not how different results can come from the same compiler.
> How might that be happening?
It's not. The two compilers are outputting the same or equivalent code.
What you're seeing is different consoles. The actual result is
"ABC\0DEF". When you test the code from the command line, the console
handles the unprintable character by simply omitting it. Eclipse's
console view handles it by considering it the end of the string and not
printing any more.
There exists no Java specification that defines how the console should
behave in response to bytes sent to stdout. Therefore, either is
equally correct.
--
www.designacourse.com
The Easiest Way To Train Anyone... Anywhere.
Chris Smith - Lead Software Developer/Technical Trainer
MindIQ Corporation
.
- References:
- String from char[] with null termination.
- From: Kevin Podsiadlik
- String from char[] with null termination.
- Prev by Date: Re: Overloading abstract methods
- Next by Date: Re: Automating testing of JApplets
- Previous by thread: String from char[] with null termination.
- Next by thread: Re: String from char[] with null termination.
- Index(es):
Relevant Pages
|