09:27:55 From John Helmers : Hello everyone! 09:28:10 From Liang Ng : Hello 09:35:38 From Bob Armstrong : CoSy follows Arthur Whitney's ref counting . 09:39:08 From Bob Armstrong : pair is like ' ,L catenate in CoSy 09:39:40 From Bob Armstrong : unpair is like ' lst>stk 09:39:47 From Kevin Appert : If you're not muted, please do! 10:00:17 From Bob Armstrong : Arthur W once said K was sort of lisp with n item , rather than 2 , lists 10:27:23 From Juergen Pintaske : aS THERE IS A GAP HERE, IT MIGHT BE A QUICK QUESTION: IF THERE IS ANYBODY HERE WHO LIKES THE f 10:28:26 From Juergen Pintaske : FORTH BOOKSHELF I PUBLISHED??? 10:31:03 From Adrian Blake : ok 10:41:50 From alvaro barcellos : Which LICENSE is used ? 10:42:28 From Pgm Chair Kevin : unmute and ask 10:43:11 From Francois Laagel : Over and out. 10:44:52 From Peter Forth : Hi Masa, send me to my email your contact peter4th2017@gmail.com 10:45:07 From alvaro barcellos : thanks 10:45:20 From Peter Forth : the video of punyforth is on my video channel peterforth on youtube 10:46:16 From Peter Forth : I wrote the interface from punyforth to Win32forth https://www.youtube.com/watch?v=NvZHxFj0pt8 10:47:03 From Masa : I will send you my slides and programs to you. 10:47:19 From Masa : I meant Kevin. 10:48:03 From Brad Nelson : My slides, btw: http://flagxor.github.io/svfig-talks/svfig-2020-12-19/ 10:49:11 From Dave Jaffe to Brad Nelson(Privately) : Brad - please send me the loink to your slides for posting on the SVFIG website davejaffe@stanford.edu 10:49:39 From Dave Jaffe to Brad Nelson(Privately) : thanks Brad! 10:55:08 From Brad Nelson to Dave Jaffe(Privately) : http://flagxor.github.io/svfig-talks/svfig-2020-12-19/ 10:55:23 From Brad Nelson : oh will email 10:55:41 From Dave Jaffe to Brad Nelson(Privately) : no need to email - I got it 11:09:50 From John Rible : John Rible's Link for view access to 4th Palindromes.pdf [https://drive.google.com/file/d/1v0PcW2jIarQWqqmQNgyELmaeAAZmsTs4/view] 11:21:34 From Brad Nelson : Palindrome slides: https://flagxor.github.io/svfig-talks/svfig-2020-12-19/palindromes.html 11:22:13 From Dave Jaffe to Brad Nelson(Privately) : thanks Brad! 11:23:55 From Bob Armstrong : On the BAA KenIverson centennial Thursday I believe Morten Kromberg presented a 5 token algorithm which itself was a palindrome in Dyalog APL 11:27:09 From Brad Nelson : Hah, I clearly had lower reading comprehension on the problem statement. Missed the "in columns" part :-) 11:32:26 From Shawn Chen : Does VALUE have the same functionality as CONSTANT? 11:35:51 From Brad Nelson : VALUE is a little different 11:36:04 From Brad Nelson : VALUE is meant to be a different approach to variables 11:36:07 From Brad Nelson : you can do 11:36:11 From Brad Nelson : 123 VALUE foo 11:36:17 From Brad Nelson : 456 TO foo 11:36:25 From Pgm Chair Kevin to Brad Nelson(Privately) : Brad, feel free to stop recording when the "Test and Play" section starts. 11:36:26 From Brad Nelson : and then reference foo's value just by name 11:36:52 From Brad Nelson : So similar to CONSTANT you use it just by name 11:37:07 From Brad Nelson : but like VARIABLE you can change it, though you need to use TO to do it 11:37:41 From Brad Nelson : VALUE operates similar to locales and they're compatible: 11:38:46 From Brad Nelson : : test 1 7 { a b } a to b a 1+ to a a . b . ; test ok 2 7 11:39:08 From Shawn Chen : So TO parses the next word in the input stream (the name of the VALUE) 11:39:17 From Brad Nelson : yep 11:39:32 From Brad Nelson : The parse happens at compile time 11:39:43 From Brad Nelson : So TO is implemented something like: 11:39:48 From Shawn Chen : Then it searches the dictionary for this name, and then sets the address to the new number? 11:39:54 From Brad Nelson : : TO ' >BODY ! ; 11:40:45 From Brad Nelson : yep 11:40:47 From Pgm Chair Kevin : Anyone interested in presenting a study of Name Space Overloading at the Australian Forth Programming Institute? 11:41:29 From Shawn Chen : Ah that's interesting! thanks brad 11:43:54 From Brad Nelson : Oh, one other thing, simplifying somewhat. The definition I gave above for TO is what you'd have for an interpret time implementation. A proper implementation needs to be immediate and when used at compile time parse out the variable, get the body, and then compile a literal so that you're not doing the dictionary lookup each time. 11:47:19 From Shawn Chen : Then would VALUE need to change its functionality based on STATE, or would you have separate compile-time and interpret-time variants 11:47:38 From Shawn Chen : Whoops, I meant TO when I said VALUE 11:47:41 From Brad Nelson : VALUE doesn't need to be variadic. Just TO 11:48:14 From Brad Nelson : Value can pretty much be the same as CONSTANT, but gforth for instance enforces you don't use TO on a CONSTANT 11:49:56 From Brad Nelson : Also just for your context, I believe VALUE showed up only in AnsForth94, so it was absent from a lot of earlier Forths, though I imagine things like it were common. And HP calculators for instance used something similar called STO 11:55:42 From Shawn Chen : I'd assumed the STO on my ti84 was short for "store," but it seems to be inheirited from hp 11:56:02 From Shawn Chen : or maybe just a coincidence 11:58:51 From Brad Nelson : No STO is from "store", but on the RPN HP calculators you'd do STO followed by a variable to store to it. So if anything the relationship might be the other way round, i.e. TO as a convience inspired by STO (and shorted to TO). 11:59:31 From Brad Nelson : But folks here that predate me would likely have a better idea how far back Forth folks have had TO like words 12:01:55 From Dave Jaffe : Scamp2 - Embedded Forth Computer with video (0:43) https://www.tindie.com/products/johncatsoulis/scamp 12:11:02 From Dave Jaffe : not me 12:16:44 From Brad Nelson : Shawn, here's a proper definition of VALUE & TO (I think): 12:16:45 From Brad Nelson : : VALUE create , does> @ ; : TO ' >body state @ if postpone literal postpone ! else ! then ; immediate 12:17:19 From Brad Nelson : That'll work for TO interpreting and will compile a literal and then a ! when compiling. 12:17:22 From John Helmers : Thanks to the Chair and all the presenters!