At 12:36 AM 6/3/98 +1000, Craig Sanders wrote:
>On Tue, 2 Jun 1998, Jules Bean wrote:
>> Of course it's viable. It just becomes a package maintainer
>> responsibility. In the vast majority of cases, the package maintainer
>> ought to be able to use the *same code* as the package itself for
>> parsing config files.
>> In many well factored cases, this will be as simple as extracting
>> config.c or some similarly named file from the distribution and making
>> a few changes to it.
>no, it's not that simple.
>it needs to read and parse the config file, allow the user to manipulate
>it, and then write it back out again (if the user chooses to save any
>changes) WITHOUT losing any information, including comments and the
>order of the comments.
I believe linuxconf will error out if it can't parse the config file.
Craig, would you be happy if there was a built in exception handeling
mechanism into linuxconf that would give a nice error when linuxconf
couldn't parse a file.
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com