winbin

[Ludis Langens]

Eric Aos wrote:
> 
> I have no problem with adding the functionality... it would be nice to keep
> a standard though.
> 
> Have we learned enough that it's time for a newer standard ???
> 
> My vote is to go to a windows INI format, that would allow for adding new
> fields in the future, without breaking previous versions.

A while ago, I thought about a way to do something similar to .ecu
files.  What I came up with is for the files to actually be a piece of
executable software in a language like Java.  (The idea was an editor
itself written in Java.  For that case, there is no sense in spending
effort to "interpret" a data file when the system already has a built in
interpreter.)  The "calling program" can provide standard functions for
all the normal data field types.  If something nonstandard needs to be
done, the definition file can simply provide the code fragment needed to
handle that case.

A downside is that and .ecu file could contain a virus.  ;-)

-- 
Ludis Langens                               ludis (at) cruzers (dot) com
Mac, Fiero, & engine controller goodies:  http://www.cruzers.com/~ludis/


----------------------------------------------------------------------------
To unsubscribe from gmecm, send "unsubscribe gmecm" (without the quotes)
in the body of a message (not the subject) to majordomo at lists.diy-efi.org