On Wed, Sep 10, 2008 at 4:38 PM, ntupel <[EMAIL PROTECTED]> wrote: > > On Tue, 2008-09-09 at 23:57 +1000, Brett Morgan wrote: >> On Tue, Sep 9, 2008 at 10:31 PM, [EMAIL PROTECTED] >> <[EMAIL PROTECTED]> wrote: >> > >> > On Sep 9, 11:26 am, "Brett Morgan" <[EMAIL PROTECTED]> wrote: >> >> For C, protection against circular dependencies is on the head of the >> >> programmer, in the form of #ifdef guards. >> > >> > There is #import as a GCC extension (also used in Objective-C). >> > >> >> Which expand out to #ifdef guards, if memory serves. > > So what? It just shows you another effective way to tackle the cycle > problem. As a programmer I don't care if I use "include" or "import" or > "require" to load my dependencies. But I do care if I need to make extra > steps to not include stuff twice. I really can not believe that we have > to discuss this age old problem which has been solved so many times > already again and again. This is just plain stupid. >
Well, you could code your own include macro to achieve the affect you are after. It is an open source project, after all. -- Brett Morgan http://brett.morgan.googlepages.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
