hi John, after giving it some thought, I realized why I the parser currently allows for multiword context names -- although context actions only accept a single word name (largely for parsing purposes), the name could become a multiword name after variable substitution (as you have mentioned). In order to allow for matching multiword names with context expressions, the parser currently supports them (for example, someone might want to create a constant for matching a particular multiword name). In order to recall that, I had to look at the code for some time :) I have to admit, though, that I have never used multiword names myself. BR, risto
--- On Tue, 8/11/09, John P. Rouillard <rou...@cs.umb.edu> wrote: > From: John P. Rouillard <rou...@cs.umb.edu> > Subject: Re: [Simple-evcorr-users] Invalid SEC context doesn't raise an error > To: simple-evcorr-users@lists.sourceforge.net > Date: Tuesday, August 11, 2009, 11:39 PM > > In message <36498.2499...@web33003.mail.mud.yahoo.com>, > Risto Vaarandi writes: > >hi John, > > Hi Risto: > > >you are seeing this behavior, because context > expression parser > >doesn't require the context name operand to contain no > spaces. I seem > >to remember that in past version of SEC, it was > possible to use > >multiword context names in expressions. > > Seriously? I never though that was the case in the context > specification. After substitution with $1, %1, %S > whatever the > context could have spaces, but not in the specifcation. > Then again I > may be thinking of context actions where AFAIK context > specifications > have always been a single white space delimited word, and I > just > assumed the same definitions for their use in the > expressions. > > >However, after having briefly > >checked the code and man page, it seems that with later > versions every > >context related action has a check that forces a > single-word > >operand. I will verify this issue and implement a > relevant check in > >the context name parser, if needed. > > Thanks. It would have saved me a lot of time tracking this > down. > > Also if context specifications are always single words, it > means I > won't have to update my class notes 8-). > > -- > > -- rouilj > John Rouillard > =========================================================================== > My employers don't acknowledge my existence much less my > opinions. > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal > Reports 2008 30-Day > trial. Simplify your report design, integration and > deployment - and focus on > what you do best, core application coding. Discover what's > new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Simple-evcorr-users mailing list > Simple-evcorr-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/simple-evcorr-users > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Simple-evcorr-users mailing list Simple-evcorr-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/simple-evcorr-users
