Approximately what I expected, but wasn't sure if I had missed anything. Is there any sort of "beginners guide" to the J GPL source?
On a related note, a route to which I've given some consideration is to place calls to libJ from another codebase with better support for the programming styles of which we're interested. Does anyone have information with regards to the overhead of jinit / jfree? If it's sufficiently lightweight, spinning up a number of J worker tasks from another environment could be an interesting route. Thanks! -- Ian On Tue, Jul 16, 2013 at 11:25 AM, Raul Miller <[email protected]> wrote: > frp would require much more implementation work than sdasync. > > That's because it would cover more ground and involve a greater part > of the J implementation. > > Thanks, > > -- > Raul > > On Tue, Jul 16, 2013 at 10:34 AM, I.T. Daniher <[email protected]> > wrote: > >> Finally, I should also note that there's other models for interaction > >> which can serve this same space. (trigger/dependencies, and > >> functional reactive programming.) > > > > FRP is definitely of interest for this application, but I'm not sure if > > it'd be any easier to realize FRP paradigms than async paradigms in J > as-is? > > > > On Tue, Jul 16, 2013 at 10:27 AM, Raul Miller <[email protected]> > wrote: > > > >> On Tue, Jul 16, 2013 at 10:04 AM, Eric Iverson < > [email protected]> > >> wrote: > >> > There is no sdasync on platforms other than windows. The facility > >> > could be constructed and is a medium to small project. But given that > >> > select works, I don't think it is worth the effort. With select you > >> > can do quite a bit. That is, a J task can wait on select for events on > >> > any number of sockets and process them as desired. One of the sockets > >> > that task waits on could be from your user GUI interface task. > >> > >> I certainly agree that it is not worth your effort. > >> > >> However, some development styles work better with the sdasync > >> mechanism than with the select mechanism. If I might be > >> oversimplistic, I'd point out that sdasync can be concise in some > >> contexts. > >> > >> Another perspective here is that this kind of project can serve as > >> training for a developer wishing to become comfortable with the J > >> implementation. > >> > >> Finally, I should also note that there's other models for interaction > >> which can serve this same space. (trigger/dependencies, and > >> functional reactive programming.) > >> > >> Thanks, > >> > >> -- > >> Raul > >> ---------------------------------------------------------------------- > >> For information about J forums see http://www.jsoftware.com/forums.htm > >> > > ---------------------------------------------------------------------- > > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
