The debugger integration is not for understanding other people's code,
but for debugging your new work.
I think of Dissect as the sentence debugger, and Debug as the
explicit-definition-and-higher debugger. The idea is, you write
something. Then, full of hope, you run it. Of course it crash
Henry, you must be congratulated on a slick, 24-carat tool.
Having seen earlier versions of dissect, I applaud the emergence of
"dissect" labs. There's scope to fine-tune them, but they already
deliver.
I'm a believer in labs. You only ever run them once, and then you
forget how helpful they've b
"
But dissect will never look inside an explicit verb. Maybe I could start a
debug window, but that's the most I could do.
"
The above makes sense to me.
"
I thought about an options to expand tacit verbs before dissecting, or to
apply f. so that dissect 'verb f. noun' would expand verb bef
I think putting () around all J within ordinary text would be a good idea.
Not needed when J is the only sentence on the line.
Another convention I would like to see in explaining J or sending J in
e-mail is something to mark a continuing line/wrap on a long J line.
Maybe using () could be used f
Will do on the link to Wiki.
I thought about letting a click on a primitive in the sentence open up
the NuVoc for it. It's hard to know when to stop adding features.
Henry Rich
On 3/5/2015 7:18 PM, Jose Mario Quintana wrote:
Yes, I think that would do it nicely.
A simple suggestion: Add an
Yes, I think that would do it nicely.
A simple suggestion: Add an item "About" (or "Quick Guide") to the dissect
Help drop down menu that merely opens the Wiki entry which I find very
useful as a quick reference.
On Thu, Mar 5, 2015 at 3:42 PM, Henry Rich wrote:
> There can be a config file for
would this be better?
The sentence ' +/y ' takes the sum of y -or " +/y "
might fit more common quote format
The single bracket ( +/y) suits me better than (( +/y))
Don Kelly
On 05/03/2015 4:58 AM, Henry Rich wrote:
(I wasn't suggesting you as a first-time J user, but a first-time user
There can be a config file for dissect. I'll work on that.
I classed the switches into two classes, one set that persists across
the whole J session and one that applies to just the current sentence.
The whole-session switches are sizes & tooltips, show @ @:, and show
full modifier-names. I t
I am leaning toward putting () around all J, including y.
Dissect doesn't look inside verbs. If there is a demand for it, I will
add a feature that lets you click on the name of a tacit verb to open a
new dissect window opening that verb.
But dissect will never look inside an explicit verb
Personally, I prefer the last one but the first option would be fine as
well.
One suggestion: It would be nice to be able to save and load the
preferences settings; even starting with the last settings would make the
use of dissect a lot easier for me (I find myself checking the "Show ]["
and "Sho
Let me think about this a bit - and others please step in.
I remember translating J for C and I basically remember just the . being a
real problem sometimes in flowing text at the end of a speach sentence and
the J sentence at the end of it without some separation.
.;():"[]and{} are all part of b
(I wasn't suggesting you as a first-time J user, but a first-time user
of dissect and its labs.)
Do you think it would be sufficient to put () around J symbols? We did
that in some places but not all. What about for names like u, v, and y?
The sentence (+/ y) takes the sum of items of (y).
We...
I am not sure how well I qualify as a first time user.
I do try to put my eyes on issues for newcomers.
As always J symbols can not well mix with ordinary speach so one thing to
note is to not place J sentences nor parts there of in a line with
something else.
. after a J sentence can
If you're going to go through the labs in detail, we would much
appreciate any comments you have about how they can be made easier for a
first-time user.
Also, use Package Manager every now and again to check for a new version
- we are adding sections and fixing wording.
Henry Rich
On 3/4/2
I think the interaction of debug with the labs may be an issue.
But there may be some debug problems too; if you can report them
concisely we can work on them.
Henry Rich
On 3/4/2015 9:26 AM, Björn Helgason wrote:
I like this dissect addon and labs.
At the end of dissect II lab I sometimes
I like this dissect addon and labs.
At the end of dissect II lab I sometimes get stack error trying to play
with the debug
Dissect lab II
── ((7) 11 of 11) Assignment statements ─
Did you notice anything unusual in the Dissect displays as
you were single-stepping throug
This is great!!
I put a fairly complicated sentence with a hook into dissect and the
display is nice and then the explanation on pointing at elemnents quite
inomative andgood
Have not had time to go through the labs yet but intending to shortly.
Look forward testing/using this and finally gettin
Version 3.7 of the Dissect addon is released, for j6.02 and J8.03+.
Dissect aims to be the easiest-to-use and most complete tool for
learning J and debugging J sentences, and I think this version is a big
step in that direction. Check it out if you haven't yet.
This release has:
* Tutorial
18 matches
Mail list logo
