Raul wrote: > Since J is open source, now, we can have a new > facet to these kinds of discussions
Yes. But I find these exploring these kinds of topics is infinitely more fruitful when I can augment them with experimentation. And since there's no magical one-click build-and-test system for the J source on Win64, and I'm way too lazy* to build one, I'll stick with what I can learn through the lens of the interpreter. Or maybe there is, now, a magical one-click build for J? -Dan PS: When are we going to have a serious discussion about making an curated, promoted and official open-source version of J? I think, for this to work, it has to be independent of the JSoftware version: we cannot keep the burden on them. That means one of us needs to sit at the top of the pull tree. I'd volunteer, but I'm really the wrong person to do it. I'm terrible at C, and I get lost when I try to read the macro-heavy flavor in the J source. Plus, the main reason I use J is because I hate dealing with the headaches and details of a compiled language. The only reason I'd consider touching C again is so that I could improve J (so I wouldn't have to touch C again...). But if I'm going to do that, I don't want to deal with a bunch of other obstacles in addition to it (creating a build on my OS which passes most unit tests, figuring out how to distribute my changes, etc). And I imagine I'm not the only one who feels this way. * and ignorant, though that's addressable ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
