On 06/16/10 14:00, thron7 wrote: > >> I agree that it sounds like a step back, especially when one has to deal >> with circular dependencies. (classes that try to import each other) >> >> But we have some form of import statement with any other programming >> language i'm aware of anyway. So if it will mean to get rid of the >> ./generate.py source step, I say so be it. >> > It might become also interesting from a Node.js point of view, to map to > the platform's "require" function. > > T. > >
so, i'm filing an enhancement bug then? note that ./generate.py source can still generate a separate file with proper include statements. burak ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
