> For this, I would rather let the exporter define named export lists,
> so that there's better future proofing. I would hate to be the person
> adding something to the SVG module knowing that there were a bunch of
> regexps floating around the web that might cause me to clobber
> something unexpected.
This gets to my main issue with regexps (aside from the YAGNI aspect) -- it
puts too much significance into variable names, and becomes a refactoring
hazard.
> ("*Filter*" isn't even a legal regexp, so they'd get a compilation
> error, but when you have to write SVG..*Filter.*, I think it gets to
> be pretty unwieldy.)
FWIW, you could distinguish this with the regexp syntax, for example:
import SVG./.*Filter.*/;
import /.*Filter.*/ from SVG;
But ... um, well, yeah.
Dave
_______________________________________________
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
