Feature: Embedded strings

[Cobo]

actually... yes that's true, but in that case you would not use \" around name Cobo.
there are 3 other characters you could use:
'
\'
or even \\" - double escaped

and technically, you could nest quotes to limitless depth by using increasing numbers of backslashes for each depth of nesting.

and that, my friend, is how escaped quotes work.

That kind of defeats the purpose of the neatness of escape characters.
In such case, I believe adding "s is better than adding backslashes.

[webhead]

just multiple quote marks in a row?? now THAT's what would confuse the parser.

[sk89q]

Escaping multiple levels can never be neat if you're working with more than one level. Adding ' instead of \ would completely prevent you from being able to use multiple levels of quotes.

[Cobo]

just multiple quote marks in a row?? now THAT's what would confuse the parser.

Hm, I guess you're right there.
But thats what jitspoe said he was going to do, so idk.

[Zorchenhimer]

computers are smart, they can do it.

No, computers are very dumb.  They only do exactly what you tell them to do. 

[webhead]

  fine, go ahead and pick apart my words.

i know that, i guess i should have used the word "capable" in place of "smart".

[jitspoe]

Writing a tokenizer with escape sequences is not hard...

But writing one that's compatible with the current tokenizer, and all the stuff that depends on it, is.

Double quotes seem to work fine for CSV parsers, and I think they could be implemented without breaking any of the current stuff

bind b "bind c ""say """"hello world"""""""
-> bind c "say ""hello world"""
-> say "hello world"

bind b "bind c \"say \\"hello world\\"\""
-> bind c "say \"hello world\""
-> say "hello world"

Perhaps the escape characters are cleaner, but we'd probably have to set up a full escape code set, with \t, \n, etc.  What if somebody puts \n in their name?  That could cause issues.

Oh, I just remembered something that caused headaches with my previous experiences: variables.

set somevar hello
bind a "say $somevar"
set somevar goodbye

pressing "a" will say "goodbye" as expected.  But what if you wanted it to say hello?  Putting quotes around something will make it absolute.

Also, say you wanted to use a command that cared about parameters?  If you wanted it all in the first parameter, you'd have to put quotes around it, but if you put quotes around it, it won't parse out the variable.

set somevar "string with spaces"
bind a "somecmd $somevar"

Now when you press "a", it will execute:
somecmd (1)string (2)with (3)spaces

When you really wanted
somecmd (1)"string with spaces"

But if you do:
somecmd "$somevar"

you get
somecmd (1)$somevar