My apologies here on this issue (non issue), I am not used to thinking in forth, still stuck in procedural language thinking.
Regards, John S On Tue, Jan 20, 2026 at 11:12 AM John Sarabacha <[email protected]> wrote: > Hi Tristan, > Your information was very useful here, it looks like I jumped the gun here. > I needed to understand what was happening in this sequence in order to > clone the functionality for the DTC. > > Thank you again, > John S > > On Tue, Jan 20, 2026 at 8:47 AM John Sarabacha <[email protected]> > wrote: > >> Hi Tristan, >> I will check this out. >> >> Thank you, >> John S >> >> >> >> >> On Tue, Jan 20, 2026 at 4:34 AM <[email protected]> wrote: >> >>> Hi John, >>> >>> A direct reply. I will reply to the list later. Is this what you are >>> seeing? >>> >>> https://tjnw.co.uk/amforth-rv/20231224/20231224.html >>> >>> Let me know if it fixes your problem. >>> >>> Best wishes, >>> Tristan >>> >>> >>> >>> On 2026-01-20 05:22, John Sarabacha wrote: >>> > Hi Tristan and Martin, >>> > >>> > In the file shared\literal.s >>> > IMMED "literal", LITERAL >>> > .word XT_COMPILE >>> > .word XT_DOLITERAL <======= >>> > .word XT_COMMA >>> > .word XT_EXIT >>> > >>> > This needs to be reviewed as this combination is causing a problem on >>> > the data stack (effectively doing savetos twice - DOLITERAL & >>> > DOVALUE). Not sure what the intent was here, the XT_DOLITERAL normally >>> > has a .word number following it. From what I have seen this will mess >>> > up the ITC, the DTC needs to know the correct sequence here also to >>> > operate correctly. >>> > >>> > Best Regards, >>> > John S >>> >> _______________________________________________ Amforth-devel mailing list for http://amforth.sf.net/ [email protected] https://lists.sourceforge.net/lists/listinfo/amforth-devel
