#10 closed defect (fixed)Comments in cfg files cannot be properly handled for string parameters
Description
The comments in cfg files cannot be removed from the value strings. Normally, it doesn't matter. But for string parameters like "InputFile", the comment after the parameter will be treated as a part of the parameter. A possible solution may be the following revision in bool TAppOption::setValue( const char *option , char *value )
Change History (5)comment:1 Changed 14 years ago by ksuehring
comment:2 Changed 14 years ago by davidf
comment:3 Changed 13 years ago by davidf
Updating component after adding WD (Text) tickets comment:4 Changed 13 years ago by davidf
comment:5 Changed 13 years ago by davidf
Note: See
TracTickets for help on using
tickets. | This list contains all users that will be notified about changes made to this ticket. These roles will be notified: Reporter, Owner, Subscriber, Participant
|
This has been resolved in r61, with unified config and command line handling.
The following examples will all give the same result ("some string"):
Hash (#) characters must appear after whitespace for them to be treated as marking the start of a comment.
Eg, "Foo: some string#comment" evaluates to "some string#comment".