Re: [Jprogramming] Extended precision question
If you don't mind some limitations, that: (*) the ... token can only be used in explicit definitions (*) the ... token must be preceded by a space (*) the resulting definitions do not actually contain the ... delimited coments (*) these definitions must use a lone ')' as the closing
Re: [Jprogramming] Extended precision question
Hey, Ed, Regarding comments, J has the NB. and a built-in Note noun. If you type in Note, hit enter, you'd get its definition (on 903 and 904) 3 : '0 0 $ 0 : 0' :[ And, whilst experimenting a bit to get the syntax highlighting for the kakoune text editor right, I can say with confidence
Re: [Jprogramming] Extended precision question
Ed, no apology required :) For the first approach: If you want that, you can just start using it. LEO came to my mind but you could as well support it in another editor. Write a function stripping your code off those comments and feeding the remaining code to J. Not much of a hassle except for
Re: [Jprogramming] Extended precision question
Hauke, My apologies: I expressed myself awkwardly. No disrespect was meant to any editor. :-). Emacs and vim would be my choices, too, were I feeling a lot more ambitious. I have the sense that there are two basic approaches under discussion. In the first (the one I think you’re
Re: [Jprogramming] Extended precision question
Smarter than emacs? Vim. :) editor wars aside, I’m having a hard time imagining any editor smarter than these two They may call themselves “smarter” but mostly that translates to “more cumbersome”. folds are natural in any coding editor, and I guess Tim Pope would come up with a solution
Re: [Jprogramming] Extended precision question
I expect that your ... could be made to work in explicit definitions, but it would be a bit of work (getting error reporting right might be a bit of a headache, and the interactive debugger would probably have to be partially rebuilt to work with this concept). Plus, of course, the actual
Re: [Jprogramming] Extended precision question
Jan-Pieter, I like that file format a lot. Like JSON, it’s human- and machine-readable. Further, a “slightly smart” editor (here I’m thinking perhaps of emacs macros) could toggle between it (one token per line with comments) and a conventional view (all tokens on one line, no comments). A
Re: [Jprogramming] Extended precision question
I actually was intending for quite a while to propose an extension to comments along the lines of the suggestions in this thread: to use ... as line continuation indicator that turns everything after it up to and including the next line break to be considered comment, and still considers the line
Re: [Jprogramming] Extended precision question
The LEO editor might be a good fit. And yes, it’s really freaking (cool). A script could generate the actual .ijs from snippets that are well documented and those snippets may well be single J tokens. Am 28.04.22 um 08:10 schrieb Ed Gottsman: LOL. Fair question. Here’s another: if J adopted a
Re: [Jprogramming] Extended precision question
Raul, D’oh. *Sigh*. It helps. Many thanks. I appreciate your patience as much as your knowledge and willingness to help. Ed Sent from my iPad > On Apr 27, 2022, at 3:36 PM, Raul Miller wrote: > > You should have used > squares =: *: x: >: ? 1e5 $ 1e11 > > Computing the square using
Re: [Jprogramming] Extended precision question
LOL. Fair question. Here’s another: if J adopted a style standard around ideograms (which are rendered vertically by default) for comments, would that on the one hand slightly increase (as a percentage) its reputation for obscurity among Western programmers but on the other dramatically
