That occurred to me as I was replying. But would it matter much in practice?
There are strings of inline code such as (=.) and (i.) which are either bad syntax or trivia (see for example http://www.jsoftware.com/jwiki/Vocabulary/eqdot?action=raw) If a special instrumented browser were to offer the user a list of expressions to dissect, such strings would appear in the list. But isn't it easier to have the browser recognize and ignore such trivia threatening to clutter the list, than encumber the jwiki coder with the demand to write ```(```i.6```)``` say rather than the nice simple `(i.6)`? That said, I notice on the page in question, that references to isolated primitives such as (=.) have been consistently written: (`=.`) not `(=.)` -- which offers a way to distinguish trivia from dissect candidates. Another thing worth making provision for when crafting a collection of sample code is to supply a set of default values for (e.g.) (x), (y), (z), (m), (n), … One of the biggest distractions for a novice from focussing the intellect on a new code example is the chore of needing to set up sample values for pronouns. J tutorial material routinely does this in a distracting way, e.g. … dissect '+/ z + i. 3 3' [ z =. 100 200 300 I suggest a judiciously-chosen set of defaults which will quickly become familiar to the J novice. Such a set is already implicit in NuVoc, though not used consistently. If a given primitive needs more elaborate sample data, then there are several good ways of overriding the basic set on the jwiki page itself. On Wed, Mar 11, 2015 at 1:43 AM, Henry Rich <[email protected]> wrote: > The gain would be that there are some sequences that are suitable for > execution, while others are merely used in passing. If you parenthesize all > J, it might be wise to distinguish the two. > > Or, you could parenthesize only the executable sequences. > > Henry Rich > > > On 3/10/2015 7:54 PM, Ian Clark wrote: >> >> I was thinking merely of `(…)` >> >> Nothing to be gained from making it over-complicated (…to update >> existing entries). >> >> On Tue, Mar 10, 2015 at 7:11 PM, Henry Rich <[email protected]> wrote: >>> >>> So you might use a tag like >>> >>> ```(```...```)``` >>> >>> ? That would be good. We should settle on a convention for flagging >>> executable bits. >>> >>> Henry Rich >>> >>> >>> On 3/10/2015 1:17 PM, Ian Clark wrote: >>>> >>>> >>>> Yes I used parens a lot more than you did. But not for the right >>>> reason – as I see it now. >>>> >>>> Back then, I used (redundant) parens to draw the eye to sub-phrase >>>> structure I wanted to emphasize. >>>> >>>> The right reason: >>>> If inline J code were consistently surrounded by (…) it would assist >>>> machine-identification of code samples for re-execute or dissect. >>>> (Plus of course drawing the eye to where it starts and ends.) >>>> >>>> Short of writing my own NuVoc browser in J, that's not a thing I know >>>> how to code yet … at least, not platform-independently. But someone >>>> will find a way. >>>> >>>> On Tue, Mar 10, 2015 at 3:57 AM, Henry Rich <[email protected]> >>>> wrote: >>>>> >>>>> >>>>> Yes, you put () in a lot of places in NuVoc, and I didn't. You were >>>>> right. >>>>> >>>>> Henry Rich >>>>> >>>>> >>>>> On 3/8/2015 9:48 PM, Ian Clark wrote: >>>>>> >>>>>> >>>>>> >>>>>> I like the () convention for in-line J code. It has potentially huge >>>>>> advantages for avoiding ambiguities, especially with trailing >>>>>> punctuation. >>>>>> >>>>>> When I get time (when…!) I'll retrofit it to the whole of NuVoc. If >>>>>> the J community's code vigilantes don't get there ahead of me :-) >>>>>> >>>>>> On Mon, Mar 9, 2015 at 12:48 AM, Henry Rich <[email protected]> >>>>>> wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> Dissect 3.7.4 released, and Labs at 1.0.90. >>>>>>> >>>>>>> Dissect labs now use the () convention for J code. >>>>>>> >>>>>>> Display of fill was seriously broken. If you have gone through the >>>>>>> Labs >>>>>>> already you might want to look at the fill section of Dissect I >>>>>>> again. >>>>>>> It >>>>>>> has changed. >>>>>>> >>>>>>> There is now a config file; you can save the current settings or >>>>>>> revert >>>>>>> to >>>>>>> the saved settings. >>>>>>> >>>>>>> On J8 only, there is a Help to take you to the Wiki page or to NuVoc. >>>>>>> Also, >>>>>>> F1 takes you to the Wiki page, and Shift+F1 takes you to NuVoc. >>>>>>> >>>>>>> ---------------------------------------------------------------------- >>>>>>> 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 >>>> >>> ---------------------------------------------------------------------- >>> 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
