Peter Memishian wrote:
> > Architectural "bigger than nit":
> >
> > The question of having a common "parsable format" across
> As for the generation code: in my experience, this is harder
My frustration is that we don't have a "grammer" for this
parsable format that can be used as a design pattern for ALL
of our utilities. This leads to statements like Seb's (from
his original proposal):
We propose that parseable output ... similar to ...
I don't want dozens of OpenSolaris utilities that all support
some form of "-o" and "-p" CLI arguments to all generate output
grammars that are similar to (but not quite exactly the same as)
all the others.
Hmm, this is dladm, so my parser needs to have IFS='|', while
later in my script the one that uses zoneadm needs IFS=: and
this other place needs eval (but has namespace issues) - except
on Fridays when the user has a locale != "C" ...
You are right - expecting a common set of code is probably not
worthwhile, but having a common grammar/format (IMO) still is.
I think we have enuf stuff in the system already that uses ":"
delimited lists, one line per item, with ":", "\" and "\n"
escaped by "\" characters that we need to stick with it as a
standard - but someone needs to do the survey and make a case
to make it so.
Maybe not this case, but there is a TC* lurking here to be
exactly the same as whatever that standard turns out to be.
As well as a set of new projects to retrofit all the others
to comply as well.
-John
