Hi Guys, > > Got it ? I think this is the general desired behaviour. > > Tell me if you think that would break something. > > Yup, I understand, but I can't for the life of me decide > what's a reasonable behaviour :-)
The parseArgsEx fix I made - oh - quite a while back, provides a fix for this. Basically it splits on "\s/" instead of "/" so the parameters following switches are included in the preceding switch as its value until the next value switch, which *must* include a space before it. This also fixes the problem with passing dates as parameters in the format nnnn/nn/nn or nn/nn/nnnn. I can't recall at this point if I actually committed the changes or just pointed out here how to correct the issue. Tom? Was this ever committed? Regards, Shawn K. Hall http://12PointDesign.com/ ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Archive: https://lists.sourceforge.net/lists/listinfo/dqsd-devel
