On 21 June 2011 13:46, Philip Schweiger <[email protected]> wrote: > Ok, that makes a bit more sense. I can see that working when you have > complex code with different dependencies loading at different times. I > think it makes a bit less sense when dealing with smaller, self- > contained modules as opposed to namespaces, though - in that case, I > still think it would make more sense to throw an error. So I suppose > it comes down to the use case - are you working with objects as a > large namespace, or objects as a self-contained module. >
Yeah, the point is to remove dependencies - you shouldn't have to rely on a.b.c being created before you can create a.b.d. It's partly to do with whether you're creating a library or an application I guess, and as always, "it depends"! -- Nick Morgan http://skilldrick.co.uk @skilldrick -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
