" Eh... if my goal was to implement J, I would not have "implement C" as an intermediate goal. "
Right, that is what I had in mind when I wrote "either directly or..." and I agree that it probably would be the best way. If I recall correctly, Roger Hui once stated that, if he had to do it again, he would implement J in J. Maybe, one could start by implementing a virtual machine, as they suggested, and coding a J core in Forth (or rather, using a couple of the GreenArrays varieties of Forths) and coding the rest of J in J. Finally, re-coding the full J interpreter in J (i.e., using Forth(s) to bootstrap J). Mind you, I am just thinking aloud and I have no expertise nor experience on this matters. Most likely you have given more thought to this subject. If so, at least, I would like to hear about it. " But, also, "dated" says a lot about how our industry keeps abandoning the practical issues involved with talking to hardware. " Right, but I was just wondering if I were to invest time and money on this kind of project, what would be the chances to be worthwhile. Nevertheless, I find the thought of having a version of J running on multiple computers in a chip, with no clocks, tantalizing. On Thu, Jun 20, 2019 at 9:59 AM Raul Miller <[email protected]> wrote: > On Wed, Jun 19, 2019 at 7:51 PM Jose Mario Quintana > <[email protected]> wrote: > > The GreenArrays chips look very interesting. > > I am pleased that someone here, besides myself, has taken a look at the > site. > > > They claim that it would not be difficult to support C. Consequently, a > > version of J would run either directly or indirectly; then again, that is > > easy to say if one is Chuck Moore. > > Eh... if my goal was to implement J, I would not have "implement C" as > an intermediate goal. I'd use the C code base as a reference, but > instead of introducing C's compromises, I'd want to iterate on direct > J implementations. (The first pass would be a "toy" and probably > discarded, relying mostly on lessons learned for the next pass...) > > Also, the chip itself has only a rather small amount of memory on each > cpu (and it's somewhere between a classic cpu and a gpu in design), so > I'd expect to have to spend some amount of effort and attempts to work > through the issues which arise when dealing with external memory. > > > The evaluation kit seems affordable; but, I am afraid, the development > cost > > (as usual) would be the dominant part (and some of their documents look > > dated). > > That's true. > > But, also, "dated" says a lot about how our industry keeps abandoning > the practical issues involved with talking to hardware. Nowadays it's > difficult to even find adequate documentation on the interfaces. > > Thanks, > > -- > Raul > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.h > <http://www.jsoftware.com/forums.htm> > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
