XML for module descriptor

[Rémi Forax]

On 04/14/2012 01:30 AM, Jeff MAURY wrote:
> Why don't you force a specific encoding for this file (UTF-8?) ?
> This should be the responsability of the compiler to generate the 
> expected encoding
>
> Jeff

because UTF-8 is not the default encoding on some platforms.
I think people still want to use their Mac, by example, to code in Java.

Rémi

>
> On Sat, Apr 14, 2012 at 12:39 AM, Rémi Forax <forax at univ-mlv.fr 
> <mailto:forax at univ-mlv.fr>> wrote:
>
>     On 04/13/2012 01:10 PM, Neil Bartlett wrote:
>
>         +1 for JSON as a first choice, XML as a second if a small
>         enough parser can be found/written to fit into the core.
>
>         -1 for YAML and other significant-whitespace formats; I agree
>         with the comments about fragility.
>
>         -1000 for module-info.class and other binary formats. The
>         seems like a no-brainer to me. The only reason to use it
>         appears to be that the parser is already present in the core,
>         though as David points out that parser is ordinarily not
>         accessible to applications.
>
>
>     Please re-read the mail of Alan.
>     and we can't use JSON because there is no way to specify the
>     character encoding.
>
>     Rémi
>
>
>
>
> -- 
> Jeff MAURY
>
>
> "Legacy code" often differs from its suggested alternative by actually 
> working and scaling.
>  - Bjarne Stroustrup
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.com
> http://www.twitter.com/jeffmaury