> I see some of the oop concepts reinvented to support json syntax. This > adds another chunk of code that needs to be maintained. Replacing the > json with python will simplify the generator.
At the time the decision was made, the surface neutrality of Json was deemed more important. > And I frankly don't think anybody's rewriting the generator in another > language anytime soon. How would you know?! > > Oh, and this may be interesting to watch: > http://hg.cython.org/cython-devel/file/tip/Demos/freeze/README.txt Nice. But last time I tried Cython, not so long ago, it bombed segfault on the generator for ridiculous reasons, so I didn't take it any further. > 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. ------------------------------------------------------------------------------ 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
