Re: ccscript3: how to use # within quotes ?
David Sugar <[email protected]> Mon, 09 Oct 2006 15:26:25 -0400
| Newsgroups | gmane.comp.gnu.bayonne.devel |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --------------030900090607070808070308 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit If you want to suggest/do a patch for compiler.cpp/getToken I would be happy to add it in a new point release. I haven't had a chance to look at this behavior as yet. There is a lower level assumption that "#" is followed by a space or newline as well then it is considered a comment, where #x.. is assumed to be "valid". This was because at one time I was looking to have special # operations in script name parsing, and in fact there is special meaning for using #xxx in place of %xxx for a symbol name where the "value" will be used instead of the "string". This is also why using "xxx#123" produces invalid symbol, just like using "xxx%yyy" would substitute %yyy with it's value in a string. Test Account wrote: > but it doesn't work when we add a parameter to a command > ex > mycommand myparam="#1" > > should we modify compiler.cpp ScriptCompiler::getToken ? > any solution ? > Thanks > > >> From: "Test Account" <[email protected]> >> To: [email protected] >> Subject: RE: [Bayonne-devel] ccscript3: how to use # within quotes ? >> Date: Mon, 09 Oct 2006 15:10:00 +0000 >> >> putting \ infront of # within the quotes seems to do the trick >> >> >> >>> From: "Test Account" <[email protected]> >>> To: [email protected] >>> Subject: [Bayonne-devel] ccscript3: how to use # within quotes ? >>> Date: Mon, 09 Oct 2006 15:01:16 +0000 >>> >>> Hello, >>> >>> With ccscript3 (1.0.9), it seems that is not possible anymore to use >>> # within quotes >>> for instance >>> set %var "12#3" >>> with the builtin testscript, we get the error symbol 3 invalid >>> In the code, scrSet, getValue, getContent, it looks like it assumes >>> that if there is a #, it must be a symbol, without taking the quotes >>> into consideration. >>> How can we solve/bypass this problem ? >>> Thanks >>> >>> >>> >>> >>> _______________________________________________ >>> Bayonne-devel mailing list >>> [email protected] >>> http://lists.gnu.org/mailman/listinfo/bayonne-devel >> >> >> >> >> _______________________________________________ >> Bayonne-devel mailing list >> [email protected] >> http://lists.gnu.org/mailman/listinfo/bayonne-devel > > > > > _______________________________________________ > Bayonne-devel mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/bayonne-devel --------------030900090607070808070308 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Bayonne-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bayonne-devel --------------030900090607070808070308--