00:00:00 --- log: started forth/18.01.06 00:19:02 --- quit: proteusguy (Ping timeout: 248 seconds) 00:35:46 --- join: ncv_ (~neceve@unaffiliated/neceve) joined #forth 00:55:48 --- join: proteusguy (~proteus-g@2405:9800:bc10:1ca:c85f:7ef2:509a:cf6f) joined #forth 00:55:48 --- mode: ChanServ set +v proteusguy 01:08:38 --- quit: gravicappa (Ping timeout: 248 seconds) 01:10:18 --- quit: carc (Quit: QUIT) 01:11:35 --- join: carc (~carc@unaffiliated/carc) joined #forth 01:57:17 --- join: xek_ (xek@nat/intel/x-teajzthdlureicxq) joined #forth 01:59:46 --- join: xek__ (xek@nat/intel/x-jmdilktekkimaceh) joined #forth 01:59:47 --- quit: xek_ (Remote host closed the connection) 01:59:50 --- quit: xek (Ping timeout: 248 seconds) 04:02:32 --- join: gravicappa (~gravicapp@h62-133-162-39.dyn.bashtel.ru) joined #forth 04:32:24 --- quit: proteusguy (Ping timeout: 252 seconds) 05:44:19 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 06:45:01 --- quit: proteus-guy (Remote host closed the connection) 06:45:44 --- join: proteus-guy (~proteusgu@183.88.73.138) joined #forth 08:23:19 --- join: lijero (~lijero@unaffiliated/lijero) joined #forth 08:48:52 --- quit: ncv_ (Ping timeout: 252 seconds) 09:28:42 --- join: ncv_ (~neceve@2a02:c7d:c5c9:a900:c792:a3e8:397d:b37) joined #forth 09:28:42 --- quit: ncv_ (Changing host) 09:28:42 --- join: ncv_ (~neceve@unaffiliated/neceve) joined #forth 10:03:23 --- join: s0n1cB00m (~s0n1cB00m@cpc83309-brig21-2-0-cust565.3-3.cable.virginm.net) joined #forth 10:38:55 --- quit: s0n1cB00m () 11:11:01 --- quit: gravicappa (Remote host closed the connection) 11:39:40 --- join: jcob (~user@cpe-172-74-189-35.nc.res.rr.com) joined #forth 11:41:40 Is the preffered way for having a word that makes and passes a big chunk of data to `xnum cells allot` and write to `here`? 11:41:45 Or is that a bad idea? 11:42:09 I guess I mean to ask, is writing to `here` a good idea or a bad idea 11:48:16 depends on the way the data is used. If it stops being used only after anything that gets allotted after it, then it's fine, since you can easily unallot the entire thing and reuse the space. Otherwise you'll have to either set up a heap-like system for random-order freeing or keep stuff around for longer than is necessary. Also if you're allotting data that's basically meant to be there forever, like in the case of compiling, then it's 11:48:16 not an issue. 11:58:36 --- join: Gromboli (~Gromboli@static-72-88-80-103.bflony.fios.verizon.net) joined #forth 12:08:29 reepca: "heap-like system for random order freeing" sounds very interesting. Has anyone reimplemented the heap in forth? 12:08:38 reepca: also thanks for the advice 12:08:57 see the standard words "allocate" and "free". 12:54:10 --- quit: ncv_ (Ping timeout: 252 seconds) 12:56:54 --- quit: jcob (Ping timeout: 265 seconds) 13:42:07 --- quit: Keshl (Quit: Konversation terminated!) 15:02:31 is there a good reputation of gforth? 15:03:20 depends on who you ask, like most questions of reputation. 15:08:43 the engine is written in C, which some dislike, but most of the system is still forth I think. It's got pretty good error handling / messages in my experience (0 @ doesn't crash, just clears the stacks and prints an error message, and stack underflows get reported pretty nicely) 15:14:31 it does a pretty good job as an ANS-conformant implementation, good for learning how to use forth, but its weakness is in showing how to write a forth, which a lot of forthers are interested in. I've only had two major WTFs with it (aside from building it) - one involving errno being cleared by the outer interpreter due to using C library stuff, and one involving a mysterious name collision when I tried writing a c interface to some SDL 15:14:31 functions (one of SDL's names from its headers collided with one from the gforth interface's headers...). Both got fixed pretty quickly, though, and the authors are pretty responsive in my experience. 15:15:15 anyway, that's my experience with gforth. 15:20:11 so it is fairy complete ANS FORTH implementation 15:20:36 is it koshre to write forth for a byte code virtual machine? 15:20:36 ryoshu: I often recommend to people that are intrested in learning how a Forth works to look into eForth and possibly mecrisp. 15:20:58 kosher* 15:21:49 sure, but some virtual machines that forths target are dual stack machines. See Philip Koopman, Stack Machines The New Wave (iirc) 15:22:09 I target a UNIX kernel, not 8-bit microcontroller, so I'm fine with C (unless it hits the performance) 15:24:13 ryoshu, hmm in that case you could also look into what crc here has done with ngaro vm. 15:25:14 personally I find targetting a small and very well specified dual stack vm aids in efforts of ultra portability. 15:25:44 like how you can write an brainfuck interpreter and run some interesting bf programs ontop. 15:26:35 OK, thanks! enough information for now, I need to find out all that 15:26:46 starting with ngaro vm 15:30:33 http://forthworks.com/retro good, tested on my host OS - NetBSD, giving it a try 17:06:23 --- join: mark4 (~mark4@99.30.241.51) joined #forth 17:17:54 --- join: proteusguy (~proteus-g@184.22.248.235) joined #forth 17:17:54 --- mode: ChanServ set +v proteusguy 17:31:22 --- quit: proteusguy (Ping timeout: 252 seconds) 18:06:00 --- quit: dddddd (Remote host closed the connection) 19:57:30 --- join: proteusguy (~proteus-g@2001:44c8:4407:502a:c85f:7ef2:509a:cf6f) joined #forth 19:57:30 --- mode: ChanServ set +v proteusguy 20:03:44 --- quit: Gromboli (Quit: Leaving) 20:08:02 --- quit: proteusguy (Ping timeout: 265 seconds) 20:20:05 --- join: boltsO3J6TA (~tkeeq@165.16.66.58) joined #forth 20:20:05 12,06▄10,02▄10,05▄09,13▄12,12▄11,10▄13,11▄04,02▄08,13▄13,10▄04,11▄03,07▄04,03▄13,13▄11,04▄07,13▄09,05▄12 LRH IS LIVE NOW!! TODAYS EDITION SLIMER GETS FUCKED IN VEGAS!! https://www.youtube.com/user/l0de/live CALL 315-505-4666 qauckt: phadthai proteus-guy nerfur 12,11▄07,09▄07,12▄08,13▄12,03▄03,11▄12,03▄11,11▄05,13▄10,13▄ 20:20:06 --- quit: boltsO3J6TA (Remote host closed the connection) 20:38:20 --- join: Techman023NKP (~pekpburk@187.16.217.86) joined #forth 20:38:25 13,06▄06,03▄05,08▄11,06▄10,09▄05,06▄12,09▄04,05▄02,12▄12,11▄04,08▄09,11▄09,11▄05,10▄07,12▄07,10▄07,13▄02,08▄04,09▄05 LRH IS LIVE NOW!! TODAYS EDITION SLIMER GETS FUCKED IN VEGAS!! https://www.youtube.com/user/l0de/live CALL 315-505-4666 lzssdcqw: rprimus ecraven lonjil 09,13▄05,08▄10,07▄02,06▄03,05▄07,08▄02,09▄10,08▄04,08▄09,05▄04,02 20:38:25 --- quit: Techman023NKP (Remote host closed the connection) 20:47:44 --- quit: lijero (Remote host closed the connection) 23:11:06 --- quit: groovy2shoes (Ping timeout: 252 seconds) 23:56:22 --- quit: mark4 (Ping timeout: 252 seconds) 23:59:59 --- log: ended forth/18.01.06