00:00:00 --- log: started forth/14.12.18 00:05:02 --- join: samrat (~samrat@61.12.96.226) joined #forth 00:26:54 --- quit: MrMobius (Disconnected by services) 00:27:07 --- join: MrM0bius (~Joey@c-98-223-189-47.hsd1.in.comcast.net) joined #forth 00:30:14 --- quit: nisstyre (Ping timeout: 240 seconds) 00:31:40 --- join: fantazo (~fantazo@089144225051.atnat0034.highway.a1.net) joined #forth 00:57:51 --- join: Azel1 (~Thunderbi@ANice-653-1-542-113.w86-205.abo.wanadoo.fr) joined #forth 00:58:30 --- quit: Azel (Ping timeout: 264 seconds) 00:58:44 --- join: nisstyre (~yourstrul@li611-52.members.linode.com) joined #forth 01:21:58 --- quit: samrat (Quit: Computer has gone to sleep.) 01:24:54 --- join: Azel (~Thunderbi@ANice-653-1-542-113.w86-205.abo.wanadoo.fr) joined #forth 01:25:23 --- quit: Azel1 (Ping timeout: 258 seconds) 01:26:48 --- join: gabriel_laddel (~user@2601:9:4f81:acb0:221:6aff:fea4:6db8) joined #forth 01:27:00 --- quit: gabriel_laddel (Changing host) 01:27:00 --- join: gabriel_laddel (~user@unaffiliated/gabriel-laddel/x-9909917) joined #forth 01:33:31 --- join: samrat (~samrat@61.12.96.226) joined #forth 01:40:20 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 01:45:08 --- quit: mnemnion (Ping timeout: 272 seconds) 03:40:01 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 03:44:15 Is it correct behaviour to clear the entire stack if an invalid word is attempted to be executed? 03:44:27 --- quit: mnemnion (Ping timeout: 256 seconds) 03:46:55 Seems a rather unfriendly thing to do when working in an interpreter and making a simple typo. 03:47:45 --- join: Zarutian (~Adium@168-110-22-46.fiber.hringdu.is) joined #forth 03:49:07 --- quit: samrat (Quit: Computer has gone to sleep.) 03:50:25 Yes, it is. 03:51:06 In fact, it is hard to defend the opposite. 03:51:23 You have raised exception. 03:51:50 Essentially you executed "abort", thus you have to perform what you do at "throw" usually. 03:52:15 If you don't clear the stack, "-1 throw" shouldn't either, which is... strange. 04:00:57 I understand when executing code... but for a sloppy typist just working at the interpreter it's painful. Forth doesn't have a way of catching this exception and stopping this behaviour temporarily does it? 04:03:32 not that I know of 04:07:34 You can break it, sure, but then you introduce inconsistency in exception handling. 04:08:16 ASau, I'd just like to temporarily have it leave the stack intact while I'm experimenting. 04:08:48 Again, you can do it, 04:08:56 be nice to be able to redefine the existing behaviour of abort or be able to catch the exception and change how it's handled. 04:09:02 but you introduce quite serious inconsistency. 04:09:24 How do you do it? 04:10:18 Basically, you introduce weird behaviour into compiler and weird interaction between compiler and interpreter. 04:10:39 yes I'm aware of that... 04:11:33 If you want to do that, you can always go and modify "outer" interpreter. 04:11:58 * ASau shrugs. 04:12:06 Can I do that in place? I'd have to restart my forth machine wouldn't I? 04:12:52 You have to hack your implementation. 04:13:11 Right that's what I thought. So forth doesn't support such a thing at all. 04:14:22 You seem not to understand that this is fundamental stuff. 04:15:33 I do understand entirely. You were just referencing exception handling and I thought it implied there was some support in forth for catching the exception and changing its behaviour. 04:16:35 Catching exception and replacing exception mechanism are two very much different things. 04:17:37 Catching an exception and not being able to intercept/alter the system's resulting behaviour is hardly proper exception handling. 04:18:11 You definitely don't understand the issue then. 04:18:31 What you want is _not_ just catching exceptions. 04:18:42 You want to change exception mechanism _fundamentally._ 04:19:23 I understand the issue. We're just using the same words to mean different things. So tell me, a) how can you catch an exception and b) what can you do with it once caught? 04:19:44 a) with "catch" 04:20:18 b) analyse single-cell value, restore stacks, and do something. 04:32:11 --- join: saml_ (~saml@pool-71-190-5-214.nycmny.east.verizon.net) joined #forth 04:36:53 --- join: nighty-_ (~nighty@hokuriku.rural-networks.com) joined #forth 04:50:59 --- quit: fantazo (Quit: Verlassend) 04:52:13 ...reading a bit on it... still trying to get my head around how it works but will check out the source and understand better. 04:56:02 --- join: impomatic (~chatzilla@140.62.115.87.dyn.plus.net) joined #forth 05:40:01 --- quit: Zarutian (Quit: Leaving.) 06:08:46 --- quit: nisstyre (Changing host) 06:08:46 --- join: nisstyre (~yourstrul@oftn/member/Nisstyre) joined #forth 07:16:40 --- join: samrat (~samrat@123.236.183.195) joined #forth 07:25:24 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 07:38:32 --- join: DocPlatypus (~skquinn@c-76-31-212-235.hsd1.tx.comcast.net) joined #forth 07:54:41 --- quit: protist (Quit: Konversation terminated!) 07:54:46 --- quit: samrat (Quit: Computer has gone to sleep.) 07:56:43 --- quit: darkf (Ping timeout: 272 seconds) 07:57:26 --- join: samrat (~samrat@123.236.183.195) joined #forth 08:40:10 --- quit: true-grue (Read error: Connection reset by peer) 08:43:41 --- join: Zarutian (~Adium@168-110-22-46.fiber.hringdu.is) joined #forth 08:59:40 --- nick: MrM0bius -> MrMobius 09:07:11 Anyone know what the block editor is for isforth? 09:23:50 --- join: tangentstorm (~michal@108-218-151-22.lightspeed.rcsntx.sbcglobal.net) joined #forth 09:23:57 --- quit: saml_ (Ping timeout: 250 seconds) 09:34:33 proteusguy: which stack are you not clearing? SP or RP ? 09:35:23 my forths just reset RP and leave SP alone on typos. 09:37:33 --- join: true-grue (~grue@95-27-185-33.broadband.corbina.ru) joined #forth 10:15:48 SP, isforth and gforth both clear it and I understand that's the standard behaviour as well. 10:27:49 --- join: mark4 (~mark4@cpe-68-203-183-77.tx.res.rr.com) joined #forth 10:29:19 cleared in interactive mode too? 10:29:52 err immediate mode, rather. 10:38:12 yeah... that's lame. I don't reset my stack. 10:40:32 reset your stack? 10:41:10 yeah... that would get annoying in immediate mode. 10:41:26 in interpret mode you mean? 10:41:36 yeah. 10:41:37 stack should only be reset on error 10:41:46 I knew it was an 'I' mode :) 10:41:55 :) 10:42:26 yeah, on simple word look-up error, I don't bother to reset it. 10:43:05 of course, my compile mode, doesn't leave compile mode on error either. 10:43:49 abort should reset stack. and jump into quit. quit is usually : quit ] begin .... again ; 10:43:49 --- quit: Zarutian (Quit: Leaving.) 10:44:03 where ... enters your interpreter 10:44:34 yeah... I know. But I don't like that action. proteusguy was asking about that earlier, btw. 10:45:35 he was? 10:45:39 I don't really follow any standards, though. 10:45:59 neither do i 10:47:02 course, I don't use a line buffer either :) 10:47:41 look at query/expect i like them better than "accept" 10:48:09 huh... will do, any particular flavor of forth? 10:49:36 what OS do you use? 10:50:00 oh... looks like expect and query are ANS. 10:50:03 Linux 10:50:48 expect and query are not usually what ans forths use. they predate ans 10:50:53 what distribution of linux? 10:51:15 dah... Debian. 10:51:22 doh! 10:51:29 my forth does not get along with debian 10:51:51 because debian's binutils do not produce binaries with pax headers 10:52:12 ahh.. EXCEPT looks like a c-str style ACCEPT. 10:52:16 debian claims to be pax aware. ok so its pax aware... its not pax compliant 10:52:56 i stopped using debian about the time potato was released 10:53:43 hmm... I'm using it only because I couldn't get newer Fedora or Ubuntu working on my box. 10:54:19 Fedora refused to boot, and Ubuntu could handle my marginal older graphic card. 10:54:38 of "pax", I know not. 10:54:38 ubuntu IS debian 10:54:59 pax is not something you need to worry about in general 10:56:31 pax is an archiver, from what google decides to tell me. 10:57:21 no. pax is a security thing 10:57:33 a memory security thing 10:57:42 google "pax headers" 11:02:11 why are you using pax? 11:02:27 because gentoo systems come pax compliant 11:02:51 im not running a hardened gentoo but my system is still pax compliant 11:03:18 debian systems are "pax aware" but their binutils do not produce files that have a pax section in their elf headers 11:03:36 my forth expects that to be there. if it is not... the binaries you create with it WONT RUN 11:03:45 i could fix that problably if i had time 11:03:54 oh ok... gotcha. 11:05:27 install gentoo, you could use isforth then :) 11:05:34 or arch. it probably runs under arch too 11:05:47 jsut not under any debian or debian derivative 11:07:30 wow... it's been away since I perused ANS forth, or used any sort of standard forth, for that matter. 11:07:54 what forths have you used in the past? 11:08:20 i started coding forth on FPC for dos, an 83 standard forth 11:08:46 when i started this channel i set a channel limit to 83 people, a joke, limit the channel to the 83 standard :) 11:08:46 I make my own. I started with porting JonesForth to the 6809. Then just started doing my own thing. 11:08:55 jonesforth SUCKS 11:09:40 its a nice learning tool, but you're right, there is some wonky stuff in there. 11:09:59 the entire source file looks like a clusterfuck of badly written source puke 11:10:05 isforth.com, server not found 11:10:15 because my dns registration expired :( 11:10:23 i have to renew 11:11:26 dzho wants the tar.bz2 for isforth? 11:11:36 probably not 11:12:07 it's interesting to see what's out there, but for the amount of forth programming I do, various of the easy apt-gettable c forths are fine with me. 11:12:48 ya if your using apt-get then isforth wont work for you. well the precompiled forth will but nothing you fsave out will 11:12:56 I do wish I could sort out why I'm not able to get amforth on the atmega boards I have, but I'm sure that's just because I know so little about putting microcontrollers through their paces. 11:13:21 dzho i have an atmega32u4 forth i wrote. well its not 100% completed yet 11:13:29 but i wrote the avr assembler for isforth first 11:13:35 then write the avr forth 11:13:52 if I get desperate for more bare to the metal forth, I suppose I could just fire up one of the ppc macs sitting around and plunk away at openfirmware 11:13:57 also not released yet. i didnt get the talker part working yet 11:14:02 i want a usb talker 11:14:17 OF is not really forth :) 11:14:36 well, in your lights C forths aren't really forths either, iirc 11:14:40 etc etc etc 11:14:43 no true scotsman 11:14:55 cf comments re jonesforth above 11:15:25 but that's ok. 11:15:38 it's sort of cute to see defenders of the faith growling over their little slice of heaven 11:16:13 :) 11:16:25 lol 11:17:03 I would dare say anything with two stacks and RPN is forth. 11:17:30 I like some of the ideas the Retro forth people do too. 11:17:33 Pf. 11:17:40 quotes and the such. 11:20:16 what's a usb talker, btw? 11:20:59 target forth has no compiler built in. host forth (your pc) does all the compilation. you interact with the target over the talker. a usb cdc link 11:21:20 its called a teathered forth 11:21:30 ahh... gotcha.. yeah, teathered. 11:22:24 basically, it's like a tiny monitor program no... @ ! and exec ? 11:22:41 you have those too 11:22:58 on your host you just say target 11:23:01 --- join: Mat4 (~claude@ip18861915.dynamic.kabel-deutschland.de) joined #forth 11:23:03 now your interacting with the target 11:23:06 : foo bar bam ; 11:23:19 the HOST does the compilation and sends the code to the target 11:23:21 foo 11:23:26 the target runs foo 11:23:33 it should be totally seamless 11:23:50 there's some oddities with the immediate words though, no? 11:23:56 no 11:24:02 because all of that happens on the host 11:24:19 * beretta ponders. 11:24:56 the dictionary is where ? 11:25:28 I think on the host side 11:26:31 the dictionary is on the host for sure. 11:26:35 no headers on the target at all 11:26:40 that saves space on the target 11:26:44 I do a bunch of programming w/o the dictionary on the host 11:27:49 https://sites.google.com/site/cocoboot2/ 11:28:24 I mostly retro compute, in case you were wondering 11:30:05 beretta: Do you know the Coco 3 FPGA clone project ? 11:30:23 sure. 11:31:16 * dzho makes note of http://www.6809.org.uk/xroar/ just for giggles 11:37:42 the coco fpga project is uber cool. I wish I knew enough to get my hands on one. 11:41:44 There exist an eight core stack-design (Hive) which is hosted on Open Core. It should be somewhat compatible with the used board (or easy adjustable). Together with the existing code from this project I think that can be a very good target for your project 11:41:57 http://www.ebay.com/itm/like/190857622750?lpid=82 11:42:07 still no Jupiter Aces out there 11:44:01 you want an ace? 11:44:11 never really appealed to me 11:44:19 i have the vic20 forth cart here tho 11:44:38 by tom zimmer. same guy that did FPC for dos and win32forth 11:45:58 http://www.ebay.com/itm/Rare-Jupiter-Ace-4000-with-16K-Ram-Pack-/321617214489?pt=UK_VintageComputing_RL&hash=item4ae1e13c19 too rich for a whim purchase 11:53:16 I would prefer building one myself: http://searle.hostei.com/grant/JupiterAce/JupiterAce.html 11:53:38 however, not my preferred home computer 12:09:01 --- quit: bjorkintosh (Ping timeout: 264 seconds) 12:23:28 --- join: xyh (~xieyuheng@2001:250:3002:5550:6ea1:cc0f:bcb2:b187) joined #forth 12:31:19 dang! Mat4. Did you make the ls74 chips yourself too ? :) 12:32:59 no, I would use an AVR micro controller for emulation 12:36:11 thats a lot of ICs just for the keyboard :( 12:42:13 anyhow, it is a working clone and doable. An alternative is the AX81 which more integrated and simply based on software emulation (AVR) 12:42:51 http://www.jcwolfram.de/projekte/avr/ax81b/main.php 12:43:52 --- quit: samrat (Ping timeout: 245 seconds) 12:46:36 avr's are my fave uC's now 12:47:07 --- join: samrat (~samrat@123.236.183.195) joined #forth 12:47:08 they just beat 8051 for the #1 position :) 12:47:46 ick. why torture yourself with progmem in the 21st century? 12:48:02 8051's from si labs are good 12:48:08 but avr's are better 12:48:51 still 8 bit hardvard architecture 12:48:56 :( 12:49:22 even arm and x86 are basically harvard arch 12:49:34 they just overlay code and data spaces into the same memory region 12:49:40 they are STILL harvard architecture 12:49:45 no, arms vary according to typr 12:49:47 type 12:49:55 well true 12:49:59 the cortex-m is harvard tho 12:50:07 and x86 definately is 12:51:36 how is cortex-m hardvard then? you dont have to do the same silliness using functions to load any data from flash 12:52:22 MrMobius, they use the same physical memory for both code and data but they are still harvard arch 12:52:30 erm theres a term for it erm gimme a sec 12:53:09 harvard architecture with unified memory space 12:54:30 I could live with that (given forth) 12:55:27 usually you write a indirect threaded forth in a harvard arch. my 8051 forths were all direct threaded. i should do a sub threaded one 12:55:44 my AVR forth is sub threaded so is the ARM port of isforth 12:55:55 --- quit: samrat (Quit: Computer has gone to sleep.) 12:56:12 the Android NDK port of isforth had to be indirect threaded because of the android security features 12:56:23 i cant write to code space, i cant execute data space 13:01:24 mark4, interesting. so, if you read data on an arm with modified Harvard architecture, how does the compiler know whether you want to read from ram or flash? 13:01:40 address 13:02:22 but with hardvard cant you have the same address point to either data or flash? 13:02:45 harvard does not mean FLASH is mirrord by RAM 13:02:51 i understand 13:02:56 it means code and data are on separate busses 13:03:01 right 13:03:07 in this case both busses go to the same memory 13:03:21 so you can have data in flash and ram and code in flash and ram 13:03:34 what dictates the type of memory you are reading is the address you reference 13:03:52 so both ram and flash have two ports each? 13:03:54 --- quit: mnemnion (Remote host closed the connection) 13:04:08 no i dont think so 13:04:25 there is only ONE memory region. it contains both flash and ram 13:04:39 but it has a data line connected to it and a code line connected to it 13:04:41 but you can access a byte of data from flash and a byte of instruction from flash on the same cycle? 13:05:24 thats what this suggests lol 13:05:34 depends whether the cpu does pipelining, I guess. 13:05:39 so its essentially von neuman but a code access and data access can take place on the same cycle instead of taking turns? 13:05:54 but then... intel always claimed their 8086 processors had a "modern instruction pipeline" 13:06:12 erm no. not till the 386 did intel use pipelines 13:06:16 or.. so the story goes 13:06:58 MrMobius, its not VN according to arm. its a unified harvard architecture 13:07:41 mark4, I understand im just asking how it works. separate addresses like VN so the only thing it has in common with Harvard it sounds like is able to access data and code concurrently. 13:08:02 they claim it can 13:16:05 MrMobius: Some Harvard architectures features a third bus (interface) which interconnects between the separated code and data bus. For these processors writing to program memory is possible with some limitations (mainly decreased performance for memory access). This apporach is labelled as 'modified Harvard architecture'. What mark4 mean is the internal separation between code and data in between machine-code dispatch which is a techni 13:16:07 que mainly common for Intel CPU's 13:16:22 ^approach 13:17:05 the si labs can write to flash, for a ling time they were the only uCs on the market that could write to flash by executing the flash write code OUT of flash... they had the patent on it for a while 13:17:42 for a LONG time even blargh 13:17:46 must l2 type 13:21:56 how do i make gnu make echo something? 13:22:27 i got some Dallas and Atmel single-cycle 8051s but I havent tried the is labs ones 13:22:42 i like the dallas ones, dual DPTR 13:22:56 but the silicon labs ones are a LOT faster 13:23:04 not 1mhz but 100mhz 13:23:10 well 25 to 100 13:23:14 I know the 8051 to be a very bad choice for Forth 13:23:19 wow... 13:23:26 mat4 not really 13:23:47 if you keep your forth kernel SUPER minimal the 8051 is actually really good for forth 13:23:57 do you know a Forth for the 8051 which I can study ? 13:24:09 mat4 erm i can send you one maybe 13:25:15 err maybe not lol 13:25:15 I was curious about the 8051 because it has an external bus. I compared it to other chips running C code and it was really slow. 13:25:23 but thats probably because SDCC 13:25:37 MrMobius, the 8051 is kinda slow heh 13:26:07 but the si labs variants are on a faster clock and they take fewer clock cycles to execute 13:26:20 the original 8051's took 12 clock cycles per instruction cycle 13:26:23 I've found these forth: http://www.camelforth.com/page.php?4 13:26:48 interesting, it seem to be mentioned in 'starting forth' 13:26:51 ya thats an ok one, i prefer my own tho lol.. tho i cant seem to find it 13:27:16 mark4, right. those dallas ones take 1 cycle instead of 12. they are still much slower than the msp430 i compared it to which takes 1-7 cycles 13:27:57 oh i DO have a version of my 8051 forth but im not sure its functional. i only have it in source format for my DOS version of isforth lol 13:28:11 msp430 is a more modern uc 13:28:27 with a totally orthagonal instruction set 13:28:31 sure 13:28:47 tho the 8051 opcode encodings are super trivial :) 13:35:45 hmmm.. sorta 6502'ish 13:39:42 the msp430 ISA looks somewhat familiar for those who know the ti9900 13:40:07 nice MCU (specially the FRAM versions) 13:42:46 --- quit: xyh (Ping timeout: 265 seconds) 13:44:34 --- join: xyh (~xieyuheng@2001:250:3002:5550:6ea1:cc0f:bcb2:b187) joined #forth 13:45:50 i once cracked the copy protection on a c64 game in bought and wanted to keep a copy of (keep the master copy, run off of copy copy) 13:46:05 it used the x2 crash bug and the indirect jump bug of the 6502 13:46:17 thats the only copy protection i ever cracked lol 13:46:58 it used a lazer burned sector on the disk. if it could write to and read that sector it was a copy 13:47:35 i dont even remember what game it was but it was by EA 13:54:44 --- quit: true-grue (Read error: Connection reset by peer) 14:03:32 --- join: bjorkintosh (~bjork@ip68-13-229-200.ok.ok.cox.net) joined #forth 14:19:59 --- quit: nighty-_ (Quit: Disappears in a puff of smoke) 14:23:37 interesting - i miss the c64 though i never did anything other than basic programming on it 14:27:45 one of my first programs for the C128 was a MS-DOS inspired shell environment (in basic!) *lol* 14:28:08 later I switched to Pascal and Forth 14:30:05 --- quit: proteusguy (Ping timeout: 250 seconds) 14:32:52 --- join: Zarutian (~Adium@168-110-22-46.fiber.hringdu.is) joined #forth 14:43:47 --- join: proteusguy (~proteusgu@ppp-110-168-229-74.revip5.asianet.co.th) joined #forth 14:43:48 --- mode: ChanServ set +v proteusguy 14:56:51 ciao 14:56:56 --- part: Mat4 left #forth 15:17:57 --- quit: gabriel_laddel (Ping timeout: 258 seconds) 15:30:13 --- quit: Azel (Ping timeout: 258 seconds) 15:35:26 --- join: socash (~16Bitt@108-205-173-124.lightspeed.fyvlar.sbcglobal.net) joined #forth 15:45:14 --- quit: Zarutian (Remote host closed the connection) 16:23:35 --- quit: ErhardtTheWhite (Read error: Connection reset by peer) 16:23:44 --- join: ErhardtMundt (~quassel@93-43-163-57.ip92.fastwebnet.it) joined #forth 16:26:10 --- quit: KipIngram (Quit: WeeChat 0.3.7) 16:29:56 --- join: KipIngram (~kip@209.40.205.22) joined #forth 16:29:56 --- mode: ChanServ set +v KipIngram 16:53:53 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 17:26:49 --- quit: socash (Ping timeout: 264 seconds) 17:27:47 --- join: socash (~16Bitt@108-205-173-124.lightspeed.fyvlar.sbcglobal.net) joined #forth 18:21:08 --- join: ASau` (~user@46.114.24.48) joined #forth 18:22:14 --- quit: ASau (Ping timeout: 250 seconds) 18:45:24 --- quit: xyh (Remote host closed the connection) 18:54:19 --- join: darkf (~darkf___@unaffiliated/darkf) joined #forth 19:05:10 --- quit: darkf (Ping timeout: 258 seconds) 19:16:56 --- join: darkf (~darkf___@2601:7:1780:18f:e1f4:457d:664d:ed1a) joined #forth 19:16:57 --- quit: darkf (Changing host) 19:16:57 --- join: darkf (~darkf___@unaffiliated/darkf) joined #forth 20:14:29 --- nick: ASau` -> ASau 20:16:39 --- quit: impomatic (Ping timeout: 250 seconds) 20:30:49 --- quit: ASau (Remote host closed the connection) 20:39:26 --- join: Savoyard (~Savoyard@unaffiliated/savoyard) joined #forth 20:40:40 --- join: ASau (~user@46.114.24.48) joined #forth 20:46:27 --- quit: Savoyard (Quit: Be back later ...) 20:58:12 --- join: gabriel_laddel (~user@2601:9:4f81:acb0:221:6aff:fea4:6db8) joined #forth 20:58:26 --- quit: gabriel_laddel (Changing host) 20:58:26 --- join: gabriel_laddel (~user@unaffiliated/gabriel-laddel/x-9909917) joined #forth 21:38:54 --- join: Savoyard (~Savoyard@unaffiliated/savoyard) joined #forth 21:45:49 --- quit: Savoyard (Quit: Be back later ...) 21:48:16 --- join: Savoyard (~Savoyard@unaffiliated/savoyard) joined #forth 21:49:14 --- join: protist (~javery@197.249.69.111.dynamic.snap.net.nz) joined #forth 21:52:28 --- quit: Savoyard (Ping timeout: 244 seconds) 22:02:33 --- quit: gabriel_laddel (Ping timeout: 258 seconds) 22:10:37 --- join: samrat (~samrat@61.12.96.226) joined #forth 22:16:16 mark4, how do you read/write blocks in isforth? there's no use command for file access? also what, if any, editor is available for it? 22:20:48 --- join: xyh (~xieyuheng@2001:250:3002:5550:6ea1:cc0f:bcb2:b187) joined #forth 22:20:51 mark4, also did I read correctly earlier that you have a forth for ARM with an assembler? Does it run on RPi? Would love to see it. 22:30:18 --- quit: xyh (Ping timeout: 265 seconds) 22:41:12 --- join: xyh (~xieyuheng@2001:250:3002:5550:6ea1:cc0f:bcb2:b187) joined #forth 22:56:55 --- join: Savoyard (~Savoyard@unaffiliated/savoyard) joined #forth 23:01:27 --- quit: Savoyard (Ping timeout: 264 seconds) 23:18:55 --- quit: protist (Ping timeout: 245 seconds) 23:59:59 --- log: ended forth/14.12.18