View Single Post
Old 04-15-2012, 06:44 PM   #77
dub3000
Human being with feelings
 
dub3000's Avatar
 
Join Date: Mar 2008
Location: Sydney, Australia
Posts: 3,955
Default

in my opinion, there are three ways this stuff is useful:

* moving common stuff out into libraries (still need @include)
* keeping the same code path for left and right (and/or surround) channels.
* literate programming (e.g. my floaty v2 tweaks now reads like pseudocode instead of a nest of crufty array hacks).

imho, what we've got already hits a lot of those targets (as far as the hacky nature of it allows :-) )

could the "copy" functionality be accomplished by exploiting the namespace stuff we have already? e.g.

x.foo = 1;
x.bar = 2;
y = x; // copies all x.(.*) to y.(.*)?

(although to be honest, that probably wouldn't be useful for any of the specific use cases i can think of in my own code).

while we're at it (...), would be great to have a @hidden pragma or something so we can chuck libraries in there but not have them automatically show up in the browser. this would be useful for deprecating old effects as well, btw (there's a ton of ancient cruft in the JS fx folder).
dub3000 is offline   Reply With Quote