Thread: [Flashforth-devel] LCD-Shield für Arduino UNO
Brought to you by:
oh2aun
Menu
▾
▴
flashforth-devel
|
From: Peter H. <p.h...@we...> - 2023-03-24 19:14:26
Attachments:
LCD-Shield_UNO.rtf
LCD-Shield_Uno.jpg
|
Hallo liebe Forthfreunde, ich wollte FlashForth neben Programm-Monitor auch via LCD-Anzeige auf dem UNO laufen lassen, aber leider habe ich dafür kein einfaches Source-Beispiel im WEB gefunden, -> ausgenommen das Beispiel für PICDEM2 + board im "*ff5-tutorial-guide-2014-05-12.pdf*". Dieses habe ich als Vorbild hergenommen und "schlecht und recht" versucht für den UNO umzusetzen. Es ist noch nicht fertig, funktioniert jedoch bis auf die Tastenabfrage ganz gut (nur beim LCD-Shield). *Fragen:* - gibt es fertige LCD-Beispiele im WEB, die ich nicht gesehen/gefunden habe ? - hat jemand schon separate Hitachi-44780 LCD's (1/2/4 zeilen via 4 Datenpins angesteuert? viele Grüße Peter PS: Vielen Dank an Mikael für die Hilfe --> *' lcd_emit 'emit !* . ------------------------------------------------------------------------------------------------------------------- Hello dear Forth friends, i wanted to run the FlashForth besides program monitor also via LCD display on the UNO, but unfortunately I didn't find a simple example for this in the WEB, -> except the example for PICDEM2 + board in "*ff5-tutorial-guide-2014-05-12.pd*f". I have taken this as a model and tried "badly and fairly" to implement for the UNO. It is not quite finished yet, but works quite well except for the key query (only for the LCD Shield). *Questions:* - are there ready LCD examples in the WEB, which I have not seen/found ? - has anyone already separately Hitachi-44780 LCD (1/2/4 lines via 4 data pins controlled? many greetings Peter PS: Many thanks to Mikael for the help -->*' lcd_emit 'emit ! *. |
|
From: Peter J. <p.j...@uq...> - 2023-03-24 23:25:19
|
In case you find it useful, there is an updated HTML rendering of that tutorial at https://htmlpreview.github.io/?https://github.com/pajacobs-ghub/pajacobs-ghub.github.io/blob/main/flashforth/ff5-tutorial-guide.html The source is in ASCIIDOC. The final section (number 16) is the example of the 44780 LCD driven in 4-bit mode. Cheers, Peter J. ________________________________ From: Peter Höhne <p.h...@we...> Sent: Saturday, 25 March 2023 5:14 AM To: fla...@li... <fla...@li...> Subject: [Flashforth-devel] LCD-Shield für Arduino UNO Hallo liebe Forthfreunde, ich wollte FlashForth neben Programm-Monitor auch via LCD-Anzeige auf dem UNO laufen lassen, aber leider habe ich dafür kein einfaches Source-Beispiel im WEB gefunden, -> ausgenommen das Beispiel für PICDEM2 + board im "ff5-tutorial-guide-2014-05-12.pdf". Dieses habe ich als Vorbild hergenommen und "schlecht und recht" versucht für den UNO umzusetzen. Es ist noch nicht fertig, funktioniert jedoch bis auf die Tastenabfrage ganz gut (nur beim LCD-Shield). Fragen: - gibt es fertige LCD-Beispiele im WEB, die ich nicht gesehen/gefunden habe ? - hat jemand schon separate Hitachi-44780 LCD's (1/2/4 zeilen via 4 Datenpins angesteuert? viele Grüße Peter PS: Vielen Dank an Mikael für die Hilfe --> ' lcd_emit 'emit ! . ------------------------------------------------------------------------------------------------------------------- Hello dear Forth friends, i wanted to run the FlashForth besides program monitor also via LCD display on the UNO, but unfortunately I didn't find a simple example for this in the WEB, -> except the example for PICDEM2 + board in "ff5-tutorial-guide-2014-05-12.pdf". I have taken this as a model and tried "badly and fairly" to implement for the UNO. It is not quite finished yet, but works quite well except for the key query (only for the LCD Shield). Questions: - are there ready LCD examples in the WEB, which I have not seen/found ? - has anyone already separately Hitachi-44780 LCD (1/2/4 lines via 4 data pins controlled? many greetings Peter PS: Many thanks to Mikael for the help --> ' lcd_emit 'emit ! . |
|
From: Brian K N. <bkn...@gm...> - 2023-03-25 00:56:52
|
I found using the hitachi lcd datasheet and the instructions on how to initialize the lcd by instruction the most useful thing. Essentially you're putting bit patterns (instructions) on a port in the uno board using c! and strobing the the enable pin setting it high and low using mset and mclr. If you find a youtube video where people use switches and manually bring up the lcd you'll understand the process better. In the end I think its a useful process to write your own driver for the board because there is quite a bit of functionality that is glossed over by many tutorials geared toward arduino ide users. viel Glück brian-in-ohio On Fri, Mar 24, 2023 at 7:26 PM Peter Jacobs <p.j...@uq...> wrote: > In case you find it useful, there is an updated HTML rendering of that > tutorial at > > https://htmlpreview.github.io/?https://github.com/pajacobs-ghub/pajacobs-ghub.github.io/blob/main/flashforth/ff5-tutorial-guide.html > > The source is in ASCIIDOC. The final section (number 16) is the example > of the 44780 LCD driven in 4-bit mode. > > Cheers, > Peter J. > ------------------------------ > *From:* Peter Höhne <p.h...@we...> > *Sent:* Saturday, 25 March 2023 5:14 AM > *To:* fla...@li... < > fla...@li...> > *Subject:* [Flashforth-devel] LCD-Shield für Arduino UNO > > > Hallo liebe Forthfreunde, > > ich wollte FlashForth neben Programm-Monitor auch via LCD-Anzeige auf dem > UNO laufen lassen, > aber leider habe ich dafür kein einfaches Source-Beispiel im WEB gefunden, > -> ausgenommen das Beispiel für PICDEM2 + board im " > *ff5-tutorial-guide-2014-05-12.pdf*". > > Dieses habe ich als Vorbild hergenommen und "schlecht und recht" versucht > für den UNO umzusetzen. > > Es ist noch nicht fertig, funktioniert jedoch bis auf die Tastenabfrage > ganz gut (nur beim LCD-Shield). > > *Fragen:* - gibt es fertige LCD-Beispiele im WEB, die ich nicht > gesehen/gefunden habe ? > - hat jemand schon separate Hitachi-44780 LCD's (1/2/4 > zeilen via 4 Datenpins angesteuert? > > viele Grüße > Peter > PS: Vielen Dank an Mikael für die Hilfe --> *' lcd_emit 'emit !* . > > > ------------------------------------------------------------------------------------------------------------------- > > Hello dear Forth friends, > > i wanted to run the FlashForth besides program monitor also via LCD > display on the UNO, > but unfortunately I didn't find a simple example for this in the WEB, > -> except the example for PICDEM2 + board in " > *ff5-tutorial-guide-2014-05-12.pd*f". > > I have taken this as a model and tried "badly and fairly" to implement for > the UNO. > > It is not quite finished yet, but works quite well except for the key > query (only for the LCD Shield). > > *Questions:* - are there ready LCD examples in the WEB, which I have not > seen/found ? > - has anyone already separately Hitachi-44780 LCD > (1/2/4 lines via 4 data pins controlled? > > many greetings > Peter > PS: Many thanks to Mikael for the help -->* ' lcd_emit 'emit ! *. > _______________________________________________ > Flashforth-devel mailing list > Fla...@li... > https://lists.sourceforge.net/lists/listinfo/flashforth-devel > |
|
From: Mikael N. <mik...@fl...> - 2023-03-25 06:42:20
|
Hi, Here is one example https://theforth.net/package/lcd-hd44780 Side note: I needed to control the display using just as serial line so wrote this simple C program for a PIC16 chip that I soldered on the backside of a HD44780 display. https://github.com/oh2aun/serial-lcd BR Mikael On 2023-03-24 21:14, Peter Höhne wrote: > Hello dear Forth friends, > > i wanted to run the FlashForth besides program monitor also via LCD display on the UNO, > but unfortunately I didn't find a simple example for this in the WEB, > -> except the example for PICDEM2 + board in "ff5-tutorial-guide-2014-05-12.pdf". > > I have taken this as a model and tried "badly and fairly" to implement for the UNO. > > It is not quite finished yet, but works quite well except for the key query (only for the LCD Shield). > > Questions: - are there ready LCD examples in the WEB, which I have not seen/found ? > - has anyone already separately Hitachi-44780 LCD (1/2/4 lines via 4 data pins controlled? > > many greetings > Peter > PS: Many thanks to Mikael for the help --> ' lcd_emit 'emit ! . > _______________________________________________ > Flashforth-devel mailing list > Fla...@li... > https://lists.sourceforge.net/lists/listinfo/flashforth-devel -- -- Mikael |
|
From: Mikael N. <mik...@fl...> - 2023-04-26 06:20:37
|
You could use conditional compilation instead.
: ?\ ( fl --- )
0=
if
postpone \
then
; immediate
Described by Marc Petremann here:
https://sourceforge.net/p/flashforth/discussion/726813/thread/6257e78a31/
BR Mikael
On 2023-04-25 16:56, Tristan Williams wrote:
> Hello Mikael,
>
> Thank you for your reply.
>
>> What is the use case for this.
>
> I'm not sure which size of the PIC18Fx6Q761 (or other PIC) I'm going
> to use in my project and so a mcu pin attached to given piece of
> hardware may change as result this or may just change as the project
> develops. I want to write some of the firmware at the same time as I
> test out the hardware and the mcu choices. Having synonym would allow
> me to map a descriptive pin name to its actual pin easily. I have pins
> defined as RA0 RA1 etc. where RA0 results in ( -- mask port ) so I
> could map
>
> alias motor_enable RA0
> alias fan_enable RA1
>
> and then use motor_enable in subsequent code and only need to change
> the
> mapping at the top of the file
>
|
|
From: Tristan W. <ho...@tj...> - 2023-05-01 05:50:07
|
Thanks to a huge amount of help from Mikael the code for SYNONYM is below
Best wishes,
Tristan
_synonym_
marker _synonym_
decimal
: synonym ( "new-name" "old-name" -- )
flash create immediate ' , ram
does> @ state 0= over c>n immed? or
if execute else cf, then
;
\ examples
synonym plus +
synonym sum plus
: other1 + ;
: other2 plus ;
: other3 sum ;
10 1 plus -11 sum
10 1 other2 -11 other3
: other4 10 1 plus -10 sum -1 sum ;
: other5 10 1 + -10 + -1 + ;
other4
other5
see +
see other1
see other2
see other3
see other4
see other5
\ synonym is the STANDARD word but alias is easier to type
\ synonym alias synonym
|
|
From: Mikael N. <mik...@fl...> - 2023-03-25 08:55:53
|
Actually there is one implementation right in the FF AVR repository ! https://sourceforge.net/p/flashforth/code/ci/master/tree/avr/forth/mt128.fs BR Mikael On 2023-03-25 07:30, Mikael Nordman wrote: > Hi, > > Here is one example > > https://theforth.net/package/lcd-hd44780 > > Side note: > I needed to control the display using just as serial line so wrote this > simple C program for a PIC16 chip that I soldered on the backside > of a HD44780 display. > > https://github.com/oh2aun/serial-lcd > > BR Mikael > > On 2023-03-24 21:14, Peter Höhne wrote: > >> Hello dear Forth friends, >> >> i wanted to run the FlashForth besides program monitor also via LCD display on the UNO, >> but unfortunately I didn't find a simple example for this in the WEB, >> -> except the example for PICDEM2 + board in "ff5-tutorial-guide-2014-05-12.pdf". >> >> I have taken this as a model and tried "badly and fairly" to implement for the UNO. >> >> It is not quite finished yet, but works quite well except for the key query (only for the LCD Shield). >> >> Questions: - are there ready LCD examples in the WEB, which I have not seen/found ? >> - has anyone already separately Hitachi-44780 LCD (1/2/4 lines via 4 data pins controlled? >> >> many greetings >> Peter >> PS: Many thanks to Mikael for the help --> ' lcd_emit 'emit ! . >> _______________________________________________ >> Flashforth-devel mailing list >> Fla...@li... >> https://lists.sourceforge.net/lists/listinfo/flashforth-devel > > -- > -- > Mikael > _______________________________________________ > Flashforth-devel mailing list > Fla...@li... > https://lists.sourceforge.net/lists/listinfo/flashforth-devel -- -- Mikael |
|
From: Tristan W. <ho...@tj...> - 2023-05-05 09:53:43
|
I've decided to spend some of my free time in 2023 making an alternative m328 tester [1][2] using FlashForth and one of the PIC18Fx6Q71 mcu family. This should free my bench from my collection of homebrew meters and provide some fun along the way. I plan to post any FF related code on the mailing list and I've put up an activity log here https://tjnw.co.uk though there is not a lot there yet! Best wishes Tristan [1] https://www.mikrocontroller.net/articles/AVR_Transistortester [2] https://www.youtube.com/watch?v=B4YM_ljELl4 |
|
From: Tristan W. <ho...@tj...> - 2023-04-02 08:17:50
|
Hello, Has anybody tried/succeeded using flashforth on a PIC18F26/46/56Q71? https://ww1.microchip.com/downloads/aemDocuments/documents/MCU08/ProductDocuments/DataSheets/PIC18F26-46-56-Q71-Microcontroller-XLP-Data-Sheet-DS40002329.pdf The mcu seems to have a very capable mix of digital and analogue peripherals which would simplify my current and future projects considerably. Grateful for any thoughts/insights on running flashforth on this mcu. Kind regards and thanks, Tristan |
|
From: Tristan W. <ho...@tj...> - 2023-05-08 16:53:27
|
Taking a break from reading the extensive m328 tester documentation to experiment with a couple of modules on the Q71 ; the Peripheral Pin Select Module (PPS) and the Reference Clock Output Module (CLKREF) Activity log here https://tjnw.co.uk/ppsclkr/ppsclkr.html Some Forth code is there also, but as it is likely to change next week I have not posted it to the list. Best wishes, Tristan |
|
From: Mikael N. <mik...@fl...> - 2023-04-02 09:49:04
|
Hi Tristan Added support for PIC18FX6Q71. Not tested but runs in the simulator, although the sim seems a bit unstable. BR Mike On 2023-04-02 10:59, Tristan Williams wrote: > Hello, > > Has anybody tried/succeeded using flashforth on a PIC18F26/46/56Q71? > > https://ww1.microchip.com/downloads/aemDocuments/documents/MCU08/ProductDocuments/DataSheets/PIC18F26-46-56-Q71-Microcontroller-XLP-Data-Sheet-DS40002329.pdf > > The mcu seems to have a very capable mix of digital and analogue > peripherals which would simplify my current and future projects > considerably. > > Grateful for any thoughts/insights on running flashforth on this mcu. > > Kind regards and thanks, > > Tristan > > > > _______________________________________________ > Flashforth-devel mailing list > Fla...@li... > https://lists.sourceforge.net/lists/listinfo/flashforth-devel -- -- Mikael |
|
From: Tristan W. <ho...@tj...> - 2023-05-11 22:38:15
|
The next entry will be something analog. However, I wanted to combine the NCO and CLKREF modules and highlight a change in the PPS forth (use of pps+ and pps-). Activity log here https://tjnw.co.uk/ncoclkr/ncoclkr.html Best wishes Tristan |
|
From: Tristan W. <ho...@tj...> - 2023-07-22 09:30:05
|
An update on my Q71 project with some (limited) alternative floating point on pic18 https://tjnw.co.uk/20230606/20230606.html Best wishes, Tristan |
|
From: Tristan W. <ho...@tj...> - 2023-04-03 09:00:36
|
Hi Mike, Thank you! I've ordered a dev board and look forward to trying it out. Kind regards and thanks, Tristan On 02Apr23 12:48, Mikael Nordman wrote: > Hi Tristan > Added support for PIC18FX6Q71. > > Not tested but runs in the simulator, although the sim seems a bit unstable. > > BR Mike > > On 2023-04-02 10:59, Tristan Williams wrote: > > Hello, > > > > Has anybody tried/succeeded using flashforth on a PIC18F26/46/56Q71? > > > > https://ww1.microchip.com/downloads/aemDocuments/documents/MCU08/ProductDocuments/DataSheets/PIC18F26-46-56-Q71-Microcontroller-XLP-Data-Sheet-DS40002329.pdf > > > > The mcu seems to have a very capable mix of digital and analogue > > peripherals which would simplify my current and future projects > > considerably. > > > > Grateful for any thoughts/insights on running flashforth on this mcu. > > > > Kind regards and thanks, > > > > Tristan > > > > > > > > _______________________________________________ > > Flashforth-devel mailing list > > Fla...@li... > > https://lists.sourceforge.net/lists/listinfo/flashforth-devel > > -- > -- > Mikael > > > _______________________________________________ > Flashforth-devel mailing list > Fla...@li... > https://lists.sourceforge.net/lists/listinfo/flashforth-devel > |
|
From: Tristan W. <ho...@tj...> - 2023-05-19 18:28:40
|
Something analog. The end result is an adjustable 30uA to 1000uA current source between two i/o pins. Activity log https://tjnw.co.uk/analog1/analog1.html Best wishes Tristan |
|
From: Tristan W. <ho...@tj...> - 2023-05-24 06:22:30
|
Debug statements that are in compiled code when you want them but not when you don't. This is a variation on ?\ https://sourceforge.net/p/flashforth/discussion/726813/thread/6257e78a31/?limit=25#cfcb but can be used within a colon definition. Best wishes Tristan _debug_ marker _debug_ true value DEBUG : || DEBUG invert if postpone \ then ; immediate : ex1 cr || [char] + || emit cr [char] * emit cr ; false to DEBUG : ex2 cr || [char] + || emit cr [char] * emit cr ; ex1 + * ok<$,ram> ex2 * ok<$,ram> see ex1 5b20 ecc9 call cr 5b24 0e2b movlw 2b 5b26 6eec movwf (+sp) a 5b28 6aec clrf (+sp) a 5b2a ec88 call emit 5b2e ecc9 call cr 5b32 0e2a movlw 2a 5b34 6eec movwf (+sp) a 5b36 6aec clrf (+sp) a 5b38 ec88 call emit 5b3c efc9 goto cr see ex2 5b46 ecc9 call cr 5b4a 0e2a movlw 2a 5b4c 6eec movwf (+sp) a 5b4e 6aec clrf (+sp) a 5b50 ec88 call emit 5b54 efc9 goto cr |
|
From: Tristan W. <ho...@tj...> - 2023-04-07 13:19:49
|
Update I bought an EV01G21A [1] development board to experiment with FlashForth and the P18FxxQ71 family of mcu. The mcu has two UARTs, and on the dev board UART2 is internally connected [2] to a combined CDC usb-uart bridge/debugger. The dev board has the largest of the mcu family and perhaps because of this I needed to change the peripheral pin selection (PPS) in the distribution pic18fxxq72.inc file to reflect this. I now have a working serial prompt on UART2 via the builtin CDC/debugger and also on UART1 via an external usb-uart bridge - not at the same time. When using the dev board, setting a weak pullup via WPUx for the pin designated to be mcu UART2 TX pin (whilst it is still an input by default) prior to the TX pin being made an output by the UART2 peripheral seems to remove some observed noise on the line when the CDC/debugger first interacts with the FlashForth serial port. This noise seems to be a reproducible issue that is fixed with a weak pullup. I used pic-as 2.41 with mplabx 6.05 to build FlashForth. This is a new experience for me as I have, until now, stuck with FlashForth from the MPASM era. Grateful for any help on solving the two issues below > BUILD SUCCESSFUL (total time: 55ms) > Loading code from /Users/tw/ng/ff/pic18/FF.X/dist/default/production/FF.X.production.hex... > Error: /Users/tw/ng/ff/pic18/FF.X/dist/default/production/FF.X.production.hex contains code that is located at addresses that do not exist on the PIC18F56Q71. > Code incompletely loaded starting at 0x700000 (0x02). > Configuration Bits: address 0x300006: BBSIZE = 255 does not match any valid value in the device database. Best wishes Tristan [1] https://www.microchip.com/en-us/development-tool/EV01G21A [2] by default On 03Apr23 09:35, Tristan Williams wrote: > Hi Mike, > > Thank you! > > I've ordered a dev board and look forward to trying it out. > > Kind regards and thanks, > > Tristan > > On 02Apr23 12:48, Mikael Nordman wrote: > > Hi Tristan > > Added support for PIC18FX6Q71. > > > > Not tested but runs in the simulator, although the sim seems a bit unstable. > > > > BR Mike > > > > On 2023-04-02 10:59, Tristan Williams wrote: > > > Hello, > > > > > > Has anybody tried/succeeded using flashforth on a PIC18F26/46/56Q71? > > > > > > https://ww1.microchip.com/downloads/aemDocuments/documents/MCU08/ProductDocuments/DataSheets/PIC18F26-46-56-Q71-Microcontroller-XLP-Data-Sheet-DS40002329.pdf > > > > > > The mcu seems to have a very capable mix of digital and analogue > > > peripherals which would simplify my current and future projects > > > considerably. > > > > > > Grateful for any thoughts/insights on running flashforth on this mcu. > > > > > > Kind regards and thanks, > > > > > > Tristan > > > > > > > > > > > > _______________________________________________ > > > Flashforth-devel mailing list > > > Fla...@li... > > > https://lists.sourceforge.net/lists/listinfo/flashforth-devel > > > > -- > > -- > > Mikael > > > > > > _______________________________________________ > > Flashforth-devel mailing list > > Fla...@li... > > https://lists.sourceforge.net/lists/listinfo/flashforth-devel > > > > > _______________________________________________ > Flashforth-devel mailing list > Fla...@li... > https://lists.sourceforge.net/lists/listinfo/flashforth-devel > |
|
From: Mikael N. <mik...@fl...> - 2023-04-07 14:18:39
|
Congrats to getting it working On 2023-04-07 16:19, Tristan Williams wrote: >> BUILD SUCCESSFUL (total time: 55ms) >> Loading code from >> /Users/tw/ng/ff/pic18/FF.X/dist/default/production/FF.X.production.hex... >> Error: >> /Users/tw/ng/ff/pic18/FF.X/dist/default/production/FF.X.production.hex >> contains code that is located at addresses that do not exist on the >> PIC18F56Q71. >> Code incompletely loaded starting at 0x700000 (0x02). I get this error for all PIC18 builds, and I have not figured out what to do about it. But everything seems to work fine anyway on the PIC. >> Configuration Bits: address 0x300006: BBSIZE = 255 does not match any >> valid value in the device database. You can configure the configuration bits in MPLABX, generate the source code and copy paste it into the FF device config file. If the compiler does not recognize some of them, there must be a problem with the Microchip device config pack. BR Mikael |
|
From: Tristan W. <ho...@tj...> - 2023-04-14 06:04:57
|
Update #2 TRISx LATx PORTx do not appear to be in the access bank for the PIC18F56Q71 and perhaps PIC18FxxQ71 family. Best wishes, Tristan -tw-led marker -tw-led ( The EV01G21A dev board has an active low LED on RC7 ) $c142 constant latc $c14a constant trisc $c152 constant portc 1 constant b, : banksel, ( a -- ) 8 rshift $f and movlb, ; : s, ( a n -- b, ) over banksel, b, ; : led ( -- ) %10000000 trisc mclr ; \ This will not work on PIC18F56Q71 as TRISx LATx PORTx do not \ appear to be in access bank on this mcu \ : +led ( -- ) [ latc 7 a, bcf, ] ; \ : -led ( -- ) [ latc 7 a, bsf, ] ; \ This will work and is compact : +led ( -- ) [ latc 7 s, bcf, ] ; : -led ( -- ) [ latc 7 s, bsf, ] ; \ This will work and is (perhaps) clearer \ : +led ( -- ) [ latc banksel, latc 7 b, bcf, ] ; \ : -led ( -- ) [ latc banksel, latc 7 b, bsf, ] ; |
|
From: Tristan W. <ho...@tj...> - 2023-04-25 08:52:11
|
Hello, I'm trying to make the forth word SYNONYM (which I have renamed alias) and I am not sure what is the best way to do so in FlashForth? I first looked at https://forth-standard.org/standard/tools/SYNONYM which I tried to replicate in FlashForth below. : alias flash create immediate ' , ram does> @ state @ 0= over immed? or if execute else cf, emit then ; This worked at the console but not within a : definition. > alias copy 1+ \ gives OK > 100 copy \ places 101 on stack > : other copy ; \ adds 1 to TOS *whilst* being defined > 100 other ; \ does not result in TOS=101 "see"-ing other shows just a return statement Removing the immediate from the create : alias flash create ' , ram does> @ state @ 0= over immed? or if execute else cf, emit then ; > alias copy 1+ \ gives OK > 100 copy \ places 101 on stack > : other copy ; \ gives OK > 100 other ; \ places 101 on stack This worked at the console and within a : definition. However ' 1+ immed? and ' copy immed? are not the same, so copy is not a synonym of 1+ in all ways. Will this come back to bite me at some point? Best wishes, Tristan |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X