RE: [avrdude-dev] configuration file generation

[Weddington, Eric]

> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden On
> Behalf Of Joerg Wunsch
> Sent: Wednesday, March 23, 2011 4:04 PM
> To: address@hidden
> Subject: Re: [avrdude-dev] configuration file generation
> 
> Ideally, when someone really wants to touch this, the current way of
> how avrdude.conf works should be questioned.  The current avrdude.conf
> is about half a megabyte, which is fairly hard to handle.  At least
> for the source itself (i.e. the files that live in the avrdude source
> tree), it would be nice to have one file (snippet) per device, and
> another one per programmer.  I don't want to claim XML were the
> all-singing all-dancing solution for everything, but the current "flat
> file" solution has shown its deficiencies during the past decade, with
> all its "stabdelay", "hventerstabdelay", "hvleavestabdelay" etc.
> parameters, so I wouldn't mind converting it into some kind of
> hierachical structure if it's about to be touched anyway.

At the risk of rehashing this subject yet again ;-), I would prefer that a new 
file format be in some standard format, even if it is XML. Disk space is cheap.

If it were in XML, we could drop the yacc code, use standard xml libraries, 
plus it would be easier to use xmlstar (open source command-line xml processing 
tool) to convert the info from AVR Studio XML files to avrdude XML files.

Just my 2 cents.