JT is the structure that contains all thread variables. JT is what makes multiple instances of j.dll thread safe.
On Wed, Apr 17, 2013 at 1:09 PM, Greg Borota <[email protected]> wrote: > I am guessing JT stores information that might be useful in step by step > debugging (stack trace, noun values, etc.) plus also maybe for > Intellisense. (I still feel so awkward saying noun instead of variable :-) ) > > In Python tools for Visual Studio, they reproduce some of what I believe > Python also does internally, just to get the usual VS goodies > (Intellisense, go to definition, etc), I am wondering if in J by tapping > into JT we'd get we need for free. But I am getting a bit ahead of myself > here, I never implemented a language editor before, so I may find out later > what I am saying here is non-sense :-) > > But still knowing what's in JT is going to help regardless. The j engine > library functions all take a jt as parameter. The com layers keeps that JT > instance internal though. > > > On Wed, Apr 17, 2013 at 11:50 AM, Raul Miller <[email protected]> wrote: > >> My understanding is that JT is a J "stack frame" (or execution >> context) and A is a J array (it roughly corresponds to the result of >> 3!:1 within J - and note that this literal will typically contain many >> null characters). >> >> FYI, >> >> -- >> Raul >> >> On Wed, Apr 17, 2013 at 10:28 AM, Greg Borota <[email protected]> wrote: >> > Roger, these pointers are very much appreciated! I will be spending time >> on >> > that code shortly. I think I got some of the basics of the style already. >> > Once you get over the initial shock :-) things start to show their >> beauty. >> > Having the code in VS solution where you can go to definition, >> > intellisense, etc., for me at least, it's a huge help. >> > If you have more pointers on how to understand JT and A struct, that >> would >> > be very much appreciated too. >> > >> > >> > On Wed, Apr 17, 2013 at 1:39 AM, Roger Hui <[email protected] >> >wrote: >> > >> >> - The system is build around the parser. >> >> - The "magic" is in the the 9-row table in >> >> http://www.jsoftware.com/help/dictionary/dicte.htm . If you are >> >> interested, I recommend you read the section carefully. >> >> - The C code that implements the parser is in file p.c, which is 168 >> >> lines long, including many comment lines and blank lines. But the C >> >> coding >> >> style is likely different from what you have seen before. >> >> - The language "Rowan" uses the same parse table idea. See *Vector*, >> >> Volume 21, Number 2. http://archive.vector.org.uk/art10009240 >> >> - As Raul Miller hinted, by "parsing", some people mean (in our >> terms) >> >> parsing and tokenizing/lexing. >> >> >> >> >> >> >> >> >> >> On Tue, Apr 16, 2013 at 8:17 PM, Greg Borota <[email protected]> wrote: >> >> >> >> > I still need to get used to what I see in APL land. One hundred or two >> >> > lines of code doing stuff that may take thousands of lines in the >> >> languages >> >> > I am normally using. I can't wait until I also get to being able to >> write >> >> > this kind of code. >> >> > >> >> > >> >> > On Tue, Apr 16, 2013 at 10:06 PM, Raul Miller <[email protected]> >> >> > wrote: >> >> > >> >> > > If I understand your questions, yes. >> >> > > >> >> > > Here's the specification for J's parser: >> >> > > >> >> > > http://www.jsoftware.com/help/dictionary/dicte.htm >> >> > > >> >> > > Also, here's the specification for J's lexer: >> >> > > >> >> > > http://www.jsoftware.com/help/dictionary/d332.htm >> >> > > >> >> > > -- >> >> > > Raul >> >> > > >> >> > > On Tue, Apr 16, 2013 at 6:12 PM, Greg Borota <[email protected]> >> wrote: >> >> > > > So I took a look at trace.ijs. Just to make sure I get this right: >> >> the >> >> > > > whole j parsing algorithm is simulated with just about 200 lines >> of J >> >> > > code? >> >> > > > Will I also get to right code this concise (more of rhetorical >> >> question >> >> > > > though)? >> >> > > > This is just a simulation, illustrating how the real parser works, >> >> > right? >> >> > > > >> >> > > > >> >> > > > >> >> > > > On Tue, Apr 16, 2013 at 3:34 PM, Ian Clark <[email protected] >> > >> >> > > wrote: >> >> > > > >> >> > > >> Whilst I'm posting to the beta list, may I just say how much >> nicer >> >> the >> >> > > new >> >> > > >> JQt feels than the old GTK. Particularly welcome is the absence >> of a >> >> > > >> "Terminal" window on the Mac, which no longer conveys the >> impression >> >> > > it's >> >> > > >> built with string and sealing wax. >> >> > > >> >> >> > > >> A bouquet to the Team. >> >> > > >> >> >> > > >> >> >> > > >> On Tue, Apr 16, 2013 at 9:24 PM, Ian Clark < >> [email protected]> >> >> > > wrote: >> >> > > >> >> >> > > >> > I agree. >> >> > > >> > >> >> > > >> > It's just the sort of utility that would be of most help to a >> >> > complete >> >> > > >> > beginner, who needs telling the "obvious". >> >> > > >> > >> >> > > >> > The code is short enough it could quite easily form part of >> locale >> >> > > 'j'. >> >> > > >> > >> >> > > >> > >> >> > > >> > On Tue, Apr 16, 2013 at 8:23 PM, Raul Miller < >> >> [email protected] >> >> > > >> >wrote: >> >> > > >> > >> >> > > >> >> http://www.jsoftware.com/help/dictionary/dicte.htm says >> "Parsing >> >> > can >> >> > > >> >> be observed using the trace facility in >> >> > > >> >> system\packages\misc\trace.ijs" >> >> > > >> >> >> >> > > >> >> But in current implementations of J, trace.ijs is an addon. >> >> > > >> >> >> >> > > >> >> This is frustrating. >> >> > > >> >> >> >> > > >> >> -- >> >> > > >> >> 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 >> >> > > >> >> > ---------------------------------------------------------------------- >> >> > 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
