I think I see what you are getting at: C stack function calls do not
show up as stack entries for 13!:x
But, for example, if I use (".) or some user defined verb instead of
(,) as an example, I can wind up with additional stack frames from my
debug session and there will be additional C stack frames behind the
scenes which would need to be unwound when cutting back the J stack.
(This is in contrast to how threaded code can work -- in threaded code
the stack of the host programming language can be kept level when
making calls in the client language -- depending on the threading
implementation, of course...)
Thanks,
--
Raul
On Tue, May 14, 2019 at 1:47 PM Henry Rich <[email protected]> wrote:
>
> You might be remembering things like
>
> a=ravel(w);
>
> This is in C, and does the same function as a=.,w
>
> The J stack only come intos play when you are interpreting J: in other
> words, interpreting
>
> a =. ,w
>
> does some J-stack work and then eventually calls ravel(w).
>
> Henry Rich
>
> On 5/14/2019 1:43 PM, Raul Miller wrote:
> > Really?
> >
> > I thought I remembered seeing J calls being implemented as C calls?
> >
> > Thanks,
> >
>
>
> ---
> This email has been checked for viruses by AVG.
> https://www.avg.com
>
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
