Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.forth > #59057

Re: accessing current xt

From Andreas Klimas <klimas@w3group.de>
Newsgroups comp.lang.forth
Subject Re: accessing current xt
Date 2017-05-11 09:57 +0200
Organization A noiseless patient Spider
Message-ID <of15c0$27n$1@dont-email.me> (permalink)
References <oevetu$ivi$1@dont-email.me> <88eb352b-b6b9-40a3-a560-14dd76a20a2b@googlegroups.com> <oevql0$3r5$1@dont-email.me> <xKqdndnmKPRoJ47EnZ2dnUU7-YPNnZ2d@supernews.com>

Show all headers | View raw


On 2017-05-11 01:14:28 +0000, Elizabeth D. Rather said:

> On 5/10/17 9:48 AM, Andreas Klimas wrote:
>> On 2017-05-10 18:11:30 +0000, Mark Wills said:
>> 
>>> On Wednesday, 10 May 2017 17:28:54 UTC+1, Andreas Klimas  wrote:
>>>> is it possible to access the name of the word beeing compiled ?
>>>> 
>>>> fictive example
>>>> 
>>>> : log current-xt >name .log ; immediate
>>>> 
>>>> : foo log   ... ;
>>> 
>>> You might be able to access it via LATEST but it will be specific
>>> to the system you are using. Not portable at all.
>> 
>> currently I'm evaluating SwiftForth and gforth.
>> 
>> SwiftForth unfortunately doesn't have LATEST
>> gforth doesn't have >CFA
>> 
>> I'm using the evaluation version of SwiftForth, hence
>> kernel source is missing (in which recurese or immediat
>> is located).
>> 
>> I want to include some kind of introspection into
>> compiled code, for profiling, debugging, logging
>> etc. What is your (Forther) way ?
>> or don't you ?
>> you may be have another approach ?
>> If it is possible, I would go with Ansi Forth.
> 
> "Introspection" pretty much necessitates carnal knowledge of the 
> system. SwiftForth has a lot of facilities of this sort (check the 
> manual), and I assume most systems do, but they're inevitably 
> implementation-dependent.

Elizabeth, I appreciate it very much from you to get an answer.

A Google search gave me

TRAVERSE-WORDLIST

which I found also in the standard documentation.
I think this could solve all my needs.


- Andreas Klimas

> 
> Cheers,
> Elizabeth

Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

accessing current xt Andreas Klimas <klimas@w3group.de> - 2017-05-10 18:28 +0200
  Re: accessing current xt Mark Wills <markwills1970@gmail.com> - 2017-05-10 11:11 -0700
    Re: accessing current xt Mark Wills <markwills1970@gmail.com> - 2017-05-10 11:16 -0700
    Re: accessing current xt Lars Brinkhoff <lars.spam@nocrew.org> - 2017-05-10 20:20 +0200
    Re: accessing current xt Andreas Klimas <klimas@w3group.de> - 2017-05-10 21:48 +0200
      Re: accessing current xt pahihu <pahihu@gmail.com> - 2017-05-10 13:12 -0700
        Re: accessing current xt Andreas Klimas <klimas@w3group.de> - 2017-05-11 00:12 +0200
      Re: accessing current xt "Elizabeth D. Rather" <erather@forth.com> - 2017-05-10 15:14 -1000
        Re: accessing current xt Andreas Klimas <klimas@w3group.de> - 2017-05-11 09:57 +0200
          Re: accessing current xt "Elizabeth D. Rather" <erather@forth.com> - 2017-05-11 21:33 -1000
  accessing current xt gwj.nexus@gmail.com - 2017-05-10 12:56 -0700
    Re: accessing current xt Andreas Klimas <klimas@w3group.de> - 2017-05-11 00:12 +0200
      Re: accessing current xt gwj.nexus@gmail.com - 2017-05-10 22:57 -0700
  Re: accessing current xt anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-11 06:39 +0000
  Re: accessing current xt humptydumpty <ouatubi@gmail.com> - 2017-05-11 00:21 -0700
    Re: accessing current xt Lars Brinkhoff <lars.spam@nocrew.org> - 2017-05-11 09:38 +0200
      Re: accessing current xt humptydumpty <ouatubi@gmail.com> - 2017-05-11 00:49 -0700
        Re: accessing current xt Lars Brinkhoff <lars.spam@nocrew.org> - 2017-05-11 10:38 +0200
          Re: accessing current xt Julian Fondren <julian.fondren@gmail.com> - 2017-05-11 04:11 -0700
            Re: accessing current xt Lars Brinkhoff <lars.spam@nocrew.org> - 2017-05-11 14:32 +0200

csiph-web