After discussing this on #epic (efnet), we reached a tentative agreement
that it would be a definite improvement if epic *didn't* support double
quoted words in the word list functions. At least by default.
Double quoted word support in epic is a very slipperly thing to nail down.
There is not, and there never has been a definitive list of
1) What features support only uwords always
2) What features support only dwords always
3) What features support dwords only after you /xdebug extractw
Although all of the builtin functions
common, diff, sort, numsort, uniq, remws, prefix, match, rmatch,
userhost, word, remw, insertw, chngw, {r,}{pattern,filter}, copattern,
corpattern, cofilter, beforew, key, channelmode, revw, shift, pop,
findw, findws, isnumber, unsplit, joinstr, tow, afterw, fromw
have always supported dwords[1] since they were written, we are going to
change that. The above functions will soon no longer support double
quoted words and will only support straight uwords. [2]
Furthermore, the builtin commands
/FE, /FOR I IN ...
will also stop supporting double quoted words for the same reason.
For backwards compatability, epic5 will support "/xdebug dword" which
will revert to backwards compatable epic4 behavior. THIS WILL NOT BE
THE DEFAULT.
This means this change is backwards incompatable, and therefore must be
publicly vetted on the list.
It is not expected that /xdebug dword would be withdrawn before the
next production release, which is YEARS AND YEARS AWAY.
Comments?
Jeremy
[1] "Dword" means "double quoted words" or "words with spaces surrounded
by double quotes". The double quotes are not part of the dword, by rule.
[2] "Uword" means "unquoted words" or "words without spaces". You cannot
have a uword with a space in it, by rule.
_______________________________________________
List mailing list
List@epicsol.org
http://epicsol.org/mailman/listinfo/list
