Re: [sc-users] SuperCollider 3.3. alpha release

["James Harkins" <jamshark70@xxxxxxxxx>]

On Fri, Dec 26, 2008 at 10:12 AM, Eric Lyon <audiodidact@xxxxxxxxx> wrote:
> It's easy enough to fix, but perhaps it would be better if, upon
> encountering duplicate class definitions, SC were to simply print a warning,
> and then choose one of the two class files, rather than render the entire
> application inoperable.

Hmm... my first thought is, I understand the frustration of the lib
not compiling, but I think the current behavior is reasonable. If
there's a discrepancy, it's better policy (more stable) to insist on
the discrepancy being fixed before continuing. You might have two
classes with the same name that do totally different things. The
compiler can't magically resolve that.

That's not to mention the thorny problems of choosing one class file
over another. Should it prefer files in ./SCClassLibrary over
extension directories? There could be duplicates in two different
extension libraries... which is "more important"? (Hint: No matter
which policy you choose, somebody somewhere will be unhappy with it.)

hjh


-- 
James Harkins /// dewdrop world
jamshark70@xxxxxxxxxxxxxxxxx
http://www.dewdrop-world.net

"Come said the Muse,
Sing me a song no poet has yet chanted,
Sing me the universal."  -- Whitman

_______________________________________________
sc-users mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: https://listarc.bham.ac.uk/marchives/sc-users/
search: https://listarc.bham.ac.uk/lists/sc-users/search/