Hi all! As you maybe know, tg and me are working at a major buildroot improvement. One of these improvements is the minimization of redundand information, while in this email I will only address redundand information regarding packages. The general idea was to have a single file for each package containing all information, which will be (together with all others) parsed by a single entity to generate the necessary information at the certain places where it's needed.
Currently I'm writing the specification for the file's format, which is
quite complete besides some things that I want to discuss here.
So before reading the points of interest I wrote down below, read the
attached specification in it's first form.
Here my questions:
* Should variable names be case sensitive?
If they are not, we must allow everything like "hAxOrVaRIAblE". Our
idea was to leave them case sensitive and defining a regexp each has
to match against. E.g. "[A-Z][A-Z0-9_]*". So this allows only
characters in uppercase, digits and the underscore. Should more signs
be allowed (e.g. dashes)?
* The backslash discussion.
As backslashes are used internally (though only if occuring at the
end of line), it's not clear what to do with them if used in the
values themselfs. My idea was to force escaping them, but tg
mentioned then we had to allow stuff like \b, \n, \033 and so on,
too. The other choice would be not to force escaping, but then the
file's syntax would get more complicated, as it would make a
difference whether lines are broken right after the (contained)
backslash (which didn't work), or somewhere else (which would work,
giving a result containing the backslash).
Also one had to make a difference whether there is a value with a
trailing backslash, a value that continues in the next line or simply
a syntax error (which in my eyes are two possibilities over limit).
I'm looking forward to reading your opinions.
Greetings, Phil
pgpNZSSoDYJ7E.pgp
Description: PGP signature
_______________________________________________ freewrt-developers mailing list [email protected] https://www.freewrt.org/lists/listinfo/freewrt-developers
