00:00:00 --- log: started forth/19.11.11 00:25:07 --- join: dys joined #forth 00:27:49 --- join: mtsd joined #forth 00:49:40 --- join: lisbeths joined #forth 00:57:19 --- quit: lisbeths (Quit: ERC (IRC client for Emacs 26.2)) 01:07:07 --- quit: ryke (Ping timeout: 265 seconds) 01:13:25 good morning forth 01:16:15 morgen 01:19:34 Good morning 01:39:16 evening 01:39:56 evening tp! 01:40:09 heya mtst! 01:40:25 Good ! :) 01:41:22 I've just released a bootable Forth temperature sensor image for people to run on the infamous 'blue pill' board that uses the stm32f103 mcu 01:41:34 https://mecrisp-stellaris-folkdoc.sourceforge.io/project-stm32f103-lmt01.html#stm32f103-lmt01 01:42:37 Good work 01:42:45 this uses a usb driver that was based on a usb driver for cortex-m3 back in 2011 by Eckhart Köppen 01:43:29 so we have cortex drivers for ethernet and usb for Mecrisp-Stellaris, not too shabby 01:44:44 Indeed not 01:44:46 I finally sorted out the cortex-m "systick" peripheral and made a library for it which provide a accurate "ms.delay" blocking delay and some other functions 01:45:15 https://mecrisp-stellaris-folkdoc.sourceforge.io/systick-library.html#systick-library 01:46:10 I must add a example for a non-blocking delay with it 01:51:05 It is nice to be able to read the examples, thanks! 01:51:51 as a Forth beginner I have to write code like that so I can understand it myself in a year! 01:52:51 I am truly a Forth beginner, but the language fascinates me anyway. 01:52:59 --- quit: f-a (Ping timeout: 240 seconds) 01:53:22 Hope to turn myself into someone with more knowledge, in time 01:54:33 I started learning Forth in 2014, so it's been nearly 6 years so far. Forth may be easy to learn, but it's hard to master :) 01:54:53 of course the sooner one starts, the sooner they get there 01:54:57 --- join: f-a joined #forth 01:55:50 at least I'm not bored with Forth yet, which is usually what happens to me when I know something well enough 01:59:13 I discovered Forth by accident when I got involved in another language, some years ago. The creator has a background in Forth and told me about it. 01:59:26 Meeting time at the office. Back in a while :) 02:01:29 no problemo 02:08:30 --- join: Labu joined #forth 02:13:50 --- join: SysDsnEng joined #forth 02:17:02 I finally figured out my stack shuffling loop issue, so yay. I have number parsing working so the next part is adding a dictionary to my forth 02:20:47 Hi, using my J1 implementation I did add an SPI interface. I would like to use this external SPI memory to the FPGA as a block device. What additional words are required to operate on the SPI wothin eFORTH I use? 02:24:05 --- quit: mtsd (Ping timeout: 268 seconds) 02:26:23 SysDsnEng, I'm not sure any of the regulars here would have that kind of experience, I sure don't 02:26:48 SysDsnEng, why not ask James Bowman ? 02:27:47 Well I don't know he is very busy and I thought I don't botter him with this kind of 'stupid' questions... 02:28:59 he may enjoy them as you're using his design to some degree ? 02:29:06 --- quit: f-a (Read error: Connection reset by peer) 02:29:31 SysDsnEng: Woo, what are you doing with the J1? :) 02:30:31 I did use his paper and I did watch his youtube videos. However since I am more on VHDL than Verilog I did basically re-implement it in VHDL using his paper and (yes) I did look a little to the vlog code from time to time ... 02:30:40 --- join: f-a joined #forth 02:31:52 for a customer I did a very special receiver (3MBit) inside an FPGA. In order to control everything through a serial port (FTDI USB) I did implement the J1+eFORTH 02:32:36 The FPGA was cheap Lattice XP2 5K LE and the J1 is small. Threfore it was a perfect fit for me. 02:33:06 Nice 02:33:49 What I basically did was buying the evaluation kit through Mouser/Digikey and designing a custom PCB that holds all the electronics I did need for the customer project. 02:34:08 --- join: iyzsong joined #forth 02:34:38 And on this Evaluation Kit there is a SPI flash I would like to use as a block device to store various things, 02:34:58 SysDsnEng, awesome, great work! 02:35:16 maybe even FORTH source code or at least parameters or help file for the application I wrote on top of the eFORTH 'ROM' 02:35:48 --- quit: proteus-guy (Ping timeout: 268 seconds) 02:52:03 --- part: SysDsnEng left #forth 03:04:55 --- join: mtsd joined #forth 03:21:12 --- join: dave0 joined #forth 04:23:13 --- quit: mtsd (Ping timeout: 240 seconds) 04:25:18 --- join: mtsd joined #forth 04:45:49 --- join: SysDsnEng joined #forth 05:29:11 --- quit: mtsd (Remote host closed the connection) 05:47:23 --- quit: f-a (Quit: leaving) 06:34:32 --- quit: iyzsong (Ping timeout: 252 seconds) 06:38:19 --- quit: dave0 (Quit: dave's not here) 06:53:20 --- join: dddddd joined #forth 06:58:53 --- part: Labu left #forth 07:08:50 --- quit: SysDsnEng (Quit: Leaving) 07:13:15 --- quit: tabemann (Ping timeout: 276 seconds) 07:32:48 --- join: SysDsnEng joined #forth 07:49:48 --- quit: SysDsnEng (Quit: Leaving) 08:02:48 --- join: SysDsnEng joined #forth 08:15:46 --- part: SysDsnEng left #forth 08:45:31 --- join: proteus-guy joined #forth 08:48:10 --- quit: inode (Ping timeout: 245 seconds) 09:05:47 --- join: WickedShell joined #forth 09:19:25 --- quit: dys (Ping timeout: 245 seconds) 09:56:01 --- quit: proteus-guy (Ping timeout: 240 seconds) 10:11:24 --- join: dys joined #forth 10:27:02 --- join: inode joined #forth 10:49:06 --- join: TonySidaway joined #forth 11:07:18 --- join: ryke joined #forth 11:27:12 Dear Abbie, my boyfriend wants to get everybody together in a big array, but I'm a Harvard guy. If we marry, will our kids be compatible? Can a mixed marriage work? 11:29:23 "We just bought a bigger RAM chip." Von Neumann apostate reveals secret of his successful marriage with the Harvard mother of his ten subsystems. 11:31:41 "Hardware solutions are just a bandaid!" Campaigner says the battle for architectural acceptance must continue. 11:34:46 --- quit: gravicappa (Ping timeout: 268 seconds) 11:42:47 --- nick: TonySidaway -> TonySidaway_ 11:45:50 --- nick: TonySidaway_ -> TonySidaway 11:55:13 --- quit: TonySidaway (Quit: TonySidaway) 11:56:35 --- join: X-Scale` joined #forth 11:58:10 --- quit: X-Scale (Ping timeout: 265 seconds) 11:58:10 --- nick: X-Scale` -> X-Scale 12:30:58 --- join: X-Scale` joined #forth 12:31:30 --- quit: X-Scale (Ping timeout: 268 seconds) 12:31:36 --- nick: X-Scale` -> X-Scale 13:16:55 Hardware specific stuff aside, what's the minimum amount of words that I would need to implement QUIT from scratch? 14:17:37 --- join: dave0 joined #forth 14:28:56 --- join: jedb_ joined #forth 14:31:52 --- quit: jedb (Ping timeout: 265 seconds) 14:44:19 --- quit: dys (Ping timeout: 240 seconds) 15:19:30 --- quit: ryke (Quit: ryke) 15:19:41 --- join: ryke joined #forth 15:52:39 --- quit: ryke (Ping timeout: 240 seconds) 16:14:09 --- join: ryke joined #forth 16:29:39 --- quit: cheater (Ping timeout: 276 seconds) 17:24:29 does anyone here have a forth without immediate words 17:41:22 --- join: jedb__ joined #forth 17:44:14 --- quit: jedb_ (Ping timeout: 265 seconds) 17:50:17 is that even possible? 17:50:36 I can't imagine that would be a very useful forth 18:06:08 --- join: tabemann joined #forth 19:05:13 --- quit: tabemann (Ping timeout: 240 seconds) 19:29:52 --- join: tabemann joined #forth 19:38:01 --- join: cheater joined #forth 20:11:51 --- quit: WickedShell (Read error: Connection reset by peer) 20:32:47 --- join: gravicappa joined #forth 21:26:14 --- quit: dddddd (Remote host closed the connection) 22:02:38 --- join: proteus-guy joined #forth 23:02:45 --- quit: proteus-guy (Ping timeout: 265 seconds) 23:03:14 --- quit: proteusguy (Ping timeout: 265 seconds) 23:07:55 --- join: rdrop-exit joined #forth 23:11:50 hey all 23:12:26 anyone got a minute to compare a couple of syntax highlighting methods Im trying on my doc site ? 23:15:01 ryke: there's colorforth 23:15:28 --- join: proteusguy joined #forth 23:15:28 --- mode: ChanServ set +v proteusguy 23:16:04 --- join: proteus-guy joined #forth 23:16:52 colorforth has an equivalent to immediate words 23:18:07 yeah 23:18:17 it's done using colors 23:18:28 opinions ? which source looks better to you folks ? https://mecrisp-stellaris-folkdoc.sourceforge.io/_downloads/stm32-systick-library.fs.html or https://mecrisp-stellaris-folkdoc.sourceforge.io/_downloads/f103-lmt01.fs.html ? 23:19:12 it's just VIM syntax highlighting in html but two different methods 23:21:51 35,56 C 23:21:51 96,12 F <-- some fixed point Forth from my desk temperature sensor 23:22:51 First one for sure 23:22:59 The white burns my eyes 23:25:23 Jookia: are you looking for different ways to implement the behaviour of immediate words aside from in a word's definition? 23:26:30 yeah 23:28:16 c[] good afternoon Forthwrights 23:28:52 hello, forthians 23:30:23 tp: red on white will look black on white for many people due to a combination of 1. monitors having cold backlights and making red darker 2. people's eyes often having a small deficiency in red sensing cells which makes red darker again 23:30:45 tp: the white background is way too much contrast. i suggest a light warm ish gray. 23:31:07 the dark one is better, it has a lot of contrast without becoming unreadable 23:31:16 you can make out all the colors 23:31:24 in the white one, everything looks like the same color almost 23:31:33 except for links 23:32:09 white one is definitely worse. i just can't see the syntax highlighting. 23:32:14 plus it has no line nums. 23:32:36 that's my review. :) 23:33:54 tp what makes the blue pill board "infamous"? 23:34:37 I prefer not to use syntax highlighting 23:37:01 rdrop-exit: any particular reason? 23:38:17 Too busy, I find it distracting 23:55:13 --- quit: proteus-guy (Ping timeout: 240 seconds) 23:58:49 cheater, the low quality, the fake chips, wrong components, a very old cortex-m3, that kind of stuff 23:59:23 cheater and ryke, thanks for the opinion, I'll stay with the first one 23:59:59 --- log: ended forth/19.11.11