XML Bug Triage, #181818: sequence magic does not work in xml attributes

Alex Cruise wrote:
> For some reason List(Atom1,Atom2,Atom3) is pretty-printed as
> Atom1 Atom2 Atom3, i.e. with whitespace between the atoms.
>
> Burak's complaint is that attributes *are not* pretty-printed that way
> and *should be*. I haven't spent enough time to get a clear picture of
> his intent here, but my expectation would be that any whitespace that
> does not appear in the DOM should not be emitted by the pretty-printer.
>
> Thoughts?

Clearly, { List("Atom1", "Atom2", "Atom3") }.toString should
be "Atom1Atom2Atom3".

Jon

Jon Pretty wrote:
> Alex Cruise wrote:
>
>> For some reason List(Atom1,Atom2,Atom3) is pretty-printed as
>> Atom1 Atom2 Atom3, i.e. with whitespace between the atoms.
>>
> Clearly, { List("Atom1", "Atom2", "Atom3") }.toString should
> be "Atom1Atom2Atom3".
>
Note that I meant three Atoms, not plain Strings... The same principle
holds though; I don't think the whitespace belongs. In fact, if the
intent was to ensure that the same-shaped (although typeless) parse tree
can be reverse-engineered from the text, it probably makes sense to
forbid consecutive Atoms without Text in between them:

{List(Atom(123), Atom(-456.1f), Atom("hi"))} =>
"123-456.1hi" or error?

-0xe1a

On Feb 6, 2009, at 3:49 AM, Alex Cruise wrote:
> {List(Atom(123), Atom(-456.1f), Atom("hi"))} =>
> "123-456.1hi" or error?

I wouldn't be too strict on this and don't throw an error. Or is your
suggestion to put all in one (composed) atom at least?

Cheers,
--
Normen Müller