From: Fintan F. <fi...@gm...> - 2009-08-11 20:21:46
|
Yes, this is it exactly. By having a boolean property to control this, we allow the option to match regardless of whether the argument is blank (empty string) in the option's regexp. Then, when we process we can give a useful error message if we do not allow blank arguments. If we do allow blank arguments, we just proceed. This raises an issue though. In the infinite lookahead parser we don't use process, so this case (and the interaction with using the newly introduced "defaultVal") must be handled separately. On Tue, Aug 11, 2009 at 4:09 PM, Radu Grigore <rad...@gm...> wrote: > On Sun, Aug 9, 2009 at 12:20 AM, Mikoláš Janota<mik...@gm...> > wrote: > > I still don't understand what blankParamAllowed is good for. > > The error message "option X needs an argument" is better than "i don't > know what this option is". > > > ------------------------------------------------------------------------------ > 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 > _______________________________________________ > Clops-users mailing list > Clo...@li... > https://lists.sourceforge.net/lists/listinfo/clops-users > |