XML for module descriptor

[Jeff MAURY]

+1 for JSON

Jeff


On Fri, Apr 13, 2012 at 1:10 PM, Neil Bartlett <njbartlett at gmail.com> 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.
>
>
> On Friday, 13 April 2012 at 11:33, Debasish Ray Chawdhuri wrote:
>
> > I agree with Glyn. Indentation based hierarchy will be error prone when
> > hand written.
> >
> > --
> > Debasish Ray Chawdhuri
> > <http://www.geekyarticles.com/>
> >
> >
>
>
>


-- 
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