Seemingly simple ... but when this is split up into the many types of expansion, wild card expansion actually occurs last, AFTER removing backslashes and then doing variable substitution.
So this can work
variable substitution has to occur first ... which means backslash recognition has to occur before that ... so THIS can work
It gets a lot harder then that. the difference between "foo\bar" "foo\\bar" "foo\\\bar" is strange enough ... but add in '' and $ and then xml expressions and wildcards and it really gets strange.
I think I'm going to have to shift over to a "color" model ... that is, during the expansion keep track on a char by char basis the quote "color" for each and every charactor individually. By color I mean \ vs " vs ' ... any given charactor could be colored by one or more of these attributes simultaneously and it effects further processing ... even when the offending quote chars are removed.
These last 3 weeks I've tried several attempts at rewriting the quoting logic and failed miserably. In the end I settled for incremental improvements and added additional tests along the way. So far all the tests pass (dont they always!) but I'm still not happy. I will probably rewrite this module sometime. But for now ... ce' la ve'.ReplyDelete
So what are your test cases?ReplyDelete
It seems fairly simple, and I can't imagine the 'coloring' needs to go too deeply. To borrow from, let's say, Perl:
'"' -> "
"'" -> '
"\"" -> "
\' -> '
\" -> "
'\"' -> \" [single quoted strings do not have escape sequences expanded]
To get more complex:
'"\n"' -> "\n"
'"\\"' -> "\\"
"\\'" -> \'
''''' -> unterminated literal. probably ends up looking like "
Are you excited about ridding your environment of escape sequences and relying solely on XML entities?
Test cases for shells (xmlsh/sh/bsh/ksh) are a lot more complex then most languges.ReplyDelete
Your above examples are prety easy.
The difficulty comes in mainly with variable expansion and wildcard "globbing". Those really screw things up.
Especialy wildcard globbing. This one is really tricky because quotes to be removed AFTER variable expansion but before globbing, and globbing only occurs on unquoted values. I have to preseve where the quotes came from somehow in order to know when to expand "*"
echo $a # expands *
echo "$a" # does NOT expand *
echo *$a # expands like *'*'
echo *'*' # matches foo* but not foo
The quotes have to be removed BEFORE globbing but the globbing has to know what was quoted and what was not.
Perl doesnt have this problem. Shells do ... its ugly.
Its hard to explain well until you really dig through the variations.
You can see the test cases that work in the tests/core/core_quotes.xsh script
If your REALLY interested, take a look at Expander.java and let me know what you think.ReplyDelete
If you can improve or simplify it and it still passes all the test cases, please do send it and I'll check it out !
If you just have horrible things to say about how ugly the code is, post that as well.
I haven't forgotten about this, but I've got quite a bit to install on this new machine it seems... but it is open in Eclipse now. I forgot how fun parsing stuff like this is!ReplyDelete
I'll install a build of it on my work laptop tomorrow and get to playing with it throughout the week as I have time. Looking at it, I might have a couple ideas, but they are certainly about 1/16th baked at this point.
Found and fixed yet another quoting bug.ReplyDelete
"$*" was expanding as "$@" should and adding an extra empty argument.
set a b c
"a" "b" "c" ""
"a b c"