Hi MLL,
> mysearch argA /param1:argB1 argB2
>
> DQSD will consider argB2 is the second part of argA. So, how
> should I have DQSD understand that argB is actually *two*
> words separated by space ?
I think a two-word argument should be enclosed in quotes;
mysearch argA /param1:"argB1 argB2"
otherwise it gets somewhat ambiguous. For me, I think the current
behavior is more expected, and I think it echoes the command-line
conventions (though I'm not sure, for named args).
I believe I built some code for this for one of my Swedish searches, but
I'm not sure.
Could be that parseArgsEx handles it, as suggested by Shawn.
I'm currently at my last day in front of a screen, so I'm going to build
beta-2 right now, before I forget.
The other day, when I tried, Sourceforge decided to go out of service in
between two of my HTTP requests :(
Cheers,
Kim
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
DQSD-Devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dqsd-devel
