> From: bill lam > > The main issue is not spawn in jtask conflict with 2!:1 but that jtask > put its spawn in z locale. If the names spawn_jtask_ or fork_jtask_ > are only set public by users (who want current task names unchanged) in > startup scripts > > spawn_z_=: spawn_jtask_ > > but for those who prefer DOJ name will put in startup > > spawn_z_=: 2!:1 > > > > Inside JAL base library or addon, use spawn_jtask_ or 2!:1 but not > spawn. > > This is done by removing these 2 lines in task.ijs > > fork_z_=: fork_jtask_ > spawn_z_=: spawn_jtask_ > > This does not resolve conflicts, but let users have their own choice > for name spawn rather favoring jtask (at the expense of linux) as it > is now.
>From my point of view this proposal has few advantages: * it does not resolve the conflicts (which IMO are the root cause of the problems) * it breaks any existing code * rather than try and improve the cross-platform utility of jtask so that it can be used to build cross-platform solutions, it implies that individual developers should come up with their own solutions. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
