00:00:00 --- log: started forth/17.03.27 00:19:12 --- quit: X-Scale (Read error: Connection reset by peer) 00:48:02 --- join: dual (~bonafide@subzeroup.core.rzwireless.net) joined #forth 00:50:48 --- part: mtsd left #forth 00:56:46 --- join: Bunny351 (~Bunny351@134.76.235.57) joined #forth 01:11:42 --- quit: smokeink (Ping timeout: 260 seconds) 01:28:37 --- quit: luser1 (Ping timeout: 260 seconds) 01:40:29 --- quit: proteusguy (Read error: Connection reset by peer) 01:44:05 oh boy another weekind with which to play with forth so dandy 01:44:28 and golly gee is it swell to experience under the influence of marijuana, the safest drug there is. 01:45:07 so how you played with forth? 01:51:35 implementing my types right now 01:51:40 --- join: smokeink (~smoke@175.20.93.32) joined #forth 01:52:31 I am not going to make a full fledge typechecking system but there will be a way for the programmer to figure out what the type of the thing they are looking at is 02:00:07 --- quit: irsol (Remote host closed the connection) 02:01:22 --- join: irsol (~irsol@unaffiliated/contempt) joined #forth 02:03:42 --- quit: smokeink (Ping timeout: 268 seconds) 02:04:06 --- join: smokeink (~smoke@175.20.93.43) joined #forth 02:12:43 --- quit: smokeink (Ping timeout: 258 seconds) 02:14:30 --- part: Bunny351 left #forth 02:18:27 --- join: smokeink (~smoke@175.20.93.53) joined #forth 02:18:30 --- quit: dual (Ping timeout: 240 seconds) 02:47:29 --- quit: smokeink (Ping timeout: 268 seconds) 02:47:51 --- join: smokeink (~smoke@175.20.93.53) joined #forth 02:57:38 --- join: lvo (~user@D57DDE7B.static.ziggozakelijk.nl) joined #forth 02:59:49 --- quit: smokeink (Ping timeout: 268 seconds) 03:01:18 --- join: smokeink (~smoke@175.20.93.85) joined #forth 03:06:50 --- join: GeDaMo (~GeDaMo@212.225.82.133) joined #forth 03:16:03 --- quit: nighty- (Quit: Disappears in a puff of smoke) 03:17:11 --- join: mtsd (4d6e3d64@gateway/web/freenode/ip.77.110.61.100) joined #forth 03:36:23 --- join: dual (~bonafide@subzeroup.core.rzwireless.net) joined #forth 03:51:02 --- quit: dual (Ping timeout: 246 seconds) 03:52:57 --- join: dual (~bonafide@subzeroup.core.rzwireless.net) joined #forth 03:59:44 --- join: nighty- (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth 04:18:15 --- quit: lvo (Remote host closed the connection) 04:34:26 --- join: ACE_Recliner (~ACE_Recli@c-50-165-178-74.hsd1.in.comcast.net) joined #forth 04:35:21 --- part: mtsd left #forth 04:57:24 meh I have writers block 04:57:52 I have kind of already figured out some of the main datastructures I want but I have been lazy implementing it 04:58:54 the problem is until you get it to print back nice handy strings to you you are just passinga round alot of numbers 04:59:09 and the samll numbers are usually math numbers and the large numbers are usually pointers 05:00:16 what would be useful is a type that can wrap up a single number into a type 05:00:31 that way I can deal with really complex things on the stack before implementing any of my datastructures 05:18:22 yeah thats exactly what I need is just a way to keep metadata about everything on the stack 05:18:28 and print that out in a string 05:19:26 > but I have been lazy implementing it 05:19:29 oh you don't say? 05:29:52 --- join: vsg1990 (~vsg1990@static-72-88-80-103.bflony.fios.verizon.net) joined #forth 06:16:06 lol yeah 06:16:15 always be lazy try to save yourself the most effort 06:16:21 laziness will set you free 06:22:10 --- quit: dual (Ping timeout: 240 seconds) 06:23:14 always do the thing that will take less work not the thing that will take more work 06:23:43 I just need a word that will take a single number on the stack at let me store metadata bout that number e z p z 06:23:58 --- join: dual (~bonafide@subzeroup.core.rzwireless.net) joined #forth 06:38:06 --- join: proteusguy (~proteus-g@2405:9800:b408:bc31:4a51:b7ff:fe38:d966) joined #forth 06:38:06 --- mode: ChanServ set +v proteusguy 06:40:29 --- quit: ACE_Recliner (Ping timeout: 240 seconds) 06:49:27 --- join: gravicappa (~gravicapp@83.237.166.60) joined #forth 07:03:19 --- quit: dual (Ping timeout: 240 seconds) 07:30:42 --- quit: beretta (Quit: Leaving) 07:51:42 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 07:52:10 --- quit: Zarutian (Read error: Connection reset by peer) 07:52:54 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 07:56:27 --- join: neceve (~ncv@86.125.247.109) joined #forth 07:56:27 --- quit: neceve (Changing host) 07:56:27 --- join: neceve (~ncv@unaffiliated/neceve) joined #forth 08:05:13 --- join: dual (~bonafide@cpe-74-75-153-119.maine.res.rr.com) joined #forth 08:25:36 --- quit: smokeink (Quit: Lost terminal) 08:30:30 --- join: impomatic_ (~impomatic@host109-149-157-102.range109-149.btcentralplus.com) joined #forth 08:37:44 --- quit: Zarutian (Quit: Zarutian) 08:46:00 --- join: mstevens (~mstevens@ceres.etla.org) joined #forth 09:32:11 --- quit: neceve (Quit: Konversation terminated!) 09:48:22 --- join: true-grue (~true-grue@176.14.222.10) joined #forth 10:07:46 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 10:13:15 --- join: X-Scale (~ARM@214.20.108.93.rev.vodafone.pt) joined #forth 10:53:16 --- join: luser1 (~luser1@h69-21-248-248.crlbnm.broadband.dynamic.tds.net) joined #forth 11:08:50 --- quit: luser1 (Ping timeout: 268 seconds) 11:19:38 --- quit: gravicappa (Ping timeout: 260 seconds) 11:34:41 --- join: gravicappa (~gravicapp@ppp83-237-169-108.pppoe.mtu-net.ru) joined #forth 12:20:08 --- join: luser1 (~luser1@h69-21-248-248.crlbnm.broadband.dynamic.tds.net) joined #forth 12:25:34 --- join: bavier (~bavier@chippewa-nat.cray.com) joined #forth 12:36:54 --- quit: ggherdov` (Ping timeout: 255 seconds) 12:38:28 --- join: ggherdov` (sid11402@gateway/web/irccloud.com/x-wtkgxqpirkvzisct) joined #forth 12:44:32 --- quit: rgrinberg (Ping timeout: 255 seconds) 12:47:32 --- join: rgrinberg (uid50668@gateway/web/irccloud.com/x-faqmpndatnkwaxpb) joined #forth 12:47:41 --- quit: rprimus (Ping timeout: 255 seconds) 12:47:48 --- join: rprimus (~micro@178.79.128.27) joined #forth 12:48:11 --- nick: rprimus -> Guest18348 13:45:33 --- quit: luser1 (Remote host closed the connection) 13:54:39 --- quit: GeDaMo (Remote host closed the connection) 14:30:37 --- quit: gravicappa (Ping timeout: 258 seconds) 15:21:42 --- quit: mstevens (Quit: leaving) 15:26:10 --- quit: vsg1990 (Quit: Leaving) 15:33:53 --- quit: dual (Quit: I was standing in the park wondering why frisbees got bigger as they get closer. Then it hit me.) 15:52:42 --- quit: true-grue (Read error: Connection reset by peer) 16:05:50 --- join: dual (~bonafide@74.75.153.119) joined #forth 16:10:44 --- join: luser1 (~luser1@h69-21-248-248.crlbnm.broadband.dynamic.tds.net) joined #forth 16:29:56 --- quit: nighty- (Quit: Disappears in a puff of smoke) 16:32:42 --- quit: Zarutian (Quit: Zarutian) 16:35:34 --- quit: impomatic_ (Ping timeout: 260 seconds) 16:37:07 --- quit: impomatic (Ping timeout: 258 seconds) 16:37:14 --- join: impomatic_ (~impomatic@host86-170-205-91.range86-170.btcentralplus.com) joined #forth 16:37:19 --- nick: impomatic_ -> impomatic 17:05:17 --- join: neceve (~ncv@unaffiliated/neceve) joined #forth 17:07:24 --- join: Guest16519 (~rob@99-158-26-90.lightspeed.miamfl.sbcglobal.net) joined #forth 17:38:42 --- join: qzo (~nate@2601:281:8300:f6c0::8) joined #forth 17:42:26 Does anyone here have any experience with running a forth interpreter on an 8 bit microproccessor (like an 8088) like early home computers such as the C64 ran BASIC? 17:58:19 --- quit: impomatic (Ping timeout: 240 seconds) 18:01:05 --- join: nighty- (~nighty@d246113.ppp.asahi-net.or.jp) joined #forth 18:10:18 --- quit: luser1 (Ping timeout: 260 seconds) 18:14:55 --- join: smokeink (~smoke@175.20.93.85) joined #forth 18:20:56 --- join: luser1 (~luser1@h69-21-248-248.crlbnm.broadband.dynamic.tds.net) joined #forth 18:21:23 not me..but curious about your question 18:21:47 --- join: impomatic (~impomatic@host86-170-205-91.range86-170.btcentralplus.com) joined #forth 18:36:41 I have built a 8088 based computer (using the schematics of the RC2014) and I am not a huge fan of either BASIC or CP/M. 18:37:28 (and I think a Forth environment would be neat) 18:37:50 oo..would be fun to make a forth in it! 18:38:20 i just wrote a Forth interpreter in..PERL! 18:39:07 have you seen the Jones forth, code? 18:39:59 --- quit: X-Scale (Ping timeout: 240 seconds) 18:40:25 --- join: [X-Scale] (~ARM@214.20.108.93.rev.vodafone.pt) joined #forth 18:40:29 --- quit: impomatic (Ping timeout: 240 seconds) 18:41:02 I am actually looking at that right now 18:41:17 jones forth is terrible. if you want to cheat off of someone else, I recommend brad rodriguez's chromium (metaforth) and mark4th's x4 (found here https://github.com/mark4th/x4) 18:41:40 well, I shouldn't say it's terrible. it's okay to get you started, but there is a lot wrong with it 18:42:03 I said this as someone whose first exposure to forth was jonesforth 18:42:07 s/said/say 18:42:29 I just compiled x4, getting a segfault and I havent really looked into why yet. I guess there are no existing solutions, so I will work on putting resources together to create my own implementation. 18:43:03 oh, I've never actually built x4. I just peek at it every so often when I'm not sure how to best go about writing parts of mine 18:43:07 yea..i looked at Jones forth..and from reading it..i just wrote my own in Perl 18:43:12 --- nick: [X-Scale] -> X-Scale 18:44:03 jonesforth works, it's just that a lot of it is erroneous (like his definition of ', which he even has a comment exclaiming it's a clever optimation but what he actually did was reimplement lit, which is not what ' is supposed to do) 18:44:31 ah...gotcha 18:45:05 and his create doesn't parse a word, stuff like that. the behavior of a lot of jonesforth words are not compliant with canonical forths, which made it very confusing to someone like me who wasn't already familiar with forth 18:46:14 Forth was fun..but it felt like coding assembler! 18:46:38 remove the "but" and that sentence makes more sense 18:46:51 coding assembler is fun 18:47:11 the "BUT" comes in, for the tediousness 18:47:41 something i could code in Perl in 5 minutes, took me ALL day in Forth! 18:48:38 keeping the stack "in my head" while coding used up too much brain power.. 18:49:15 When I am writing in Forth I usually just keep a sheet of paper handy that I use to diagram the stack etc. 18:49:18 some forth graybeard would tell you your words are too complicated if that's your trouble 18:49:38 my words were probably too complicated..im sure 18:49:49 as i had to spend a ton of time refactoring 18:50:17 but yes, I agree it's tedious. I think I'm only just starting to get into the groove of being able to write words without having to stop and think about the stack for too long 18:50:27 but man..,if i had an error, or changed code in a word which was used all other the place... i enter a world of headache 18:50:50 Do you all just use GForth, or maybe something else? 18:51:00 I'm building my own from scratch 18:51:00 i used my own Forth 18:51:04 hahaha 18:51:24 well, have built my own. I'm now in the process of making it self-hosting 18:51:45 Haha you people are crazy 18:51:55 I guess I might do that as well. 18:51:56 no argument from me 18:52:05 you learn a TON writing your own 18:52:21 and its not a lot of code either! 18:52:36 unless you are self-hosting.. 18:53:16 wanna hear crazy! 18:53:31 i just got an old HP 200LX..which is a palm top IBM PC 8086 18:53:36 running DOS 5.0 18:53:46 it has DOS DEBUG.EXE 18:53:52 and a text editor.. 18:54:08 oh very neat 18:54:21 from there..im going to write assembly code by piping Text into DEBUG.EXE's STDIN 18:54:50 qzo: Yep, we are. I'm currently thinking how to properly write a parallel Forth. 18:54:58 I have some thoughts, but no code, yet. 18:55:02 and im going to write the assembly code source code in that shit text editor 18:55:16 on device 18:55:21 you should write it in parallel 18:55:34 zy]x[yz: I'm not sure what that even *means*. 18:55:53 almost all of my code appears on parallel lines 18:56:31 what would you do with it though? 18:56:41 I parallelize it 18:56:57 Guest16519: Partly proof of concept to myself, partly learning experience. 18:57:09 Or, to use the Internet term: 'for the lulz'. 18:57:50 on a real CPU or a virtual CPU? 18:58:08 Guest16519: Virtual machine of some kind. 18:58:21 Real CPU is a bit beyond me at the moment, but I'd like to try some time. 18:58:45 a currently existing Virtual CPU? or roll ya own 18:59:09 FPGAForth when? 18:59:26 Maybe that should be my project... a Forth in verilog. 19:02:01 one day i will learn some hardware and build an old 8bitter..like a VIC20/C64/AppleII/trash80 19:02:48 Guest16519: I don't have an FPGA handy, and all the existing VMs are kinda ehh. 19:02:53 So I'll roll my own. It'll be fun! 19:04:27 that would be fun!! 19:04:58 i had this "dream" of using MAME as my CPU machine 19:06:12 write forth for an old arcade board 19:28:53 I like Forth because writing complex stuff in it always ends up in the paradox where everything simultaniosly seems like a hack but also conforms to langauge standards and acceptable useage. 19:29:13 ha 19:37:41 --- quit: luser1 (Ping timeout: 260 seconds) 20:05:54 --- quit: neceve (Quit: Konversation terminated!) 20:22:03 --- join: neceve (~ncv@86.125.247.109) joined #forth 20:22:03 --- quit: neceve (Changing host) 20:22:03 --- join: neceve (~ncv@unaffiliated/neceve) joined #forth 20:25:32 --- quit: neceve (Client Quit) 20:36:59 --- quit: fiddlerwoaroof (Ping timeout: 240 seconds) 20:49:01 --- join: fiddlerwoaroof (~fiddlerwo@unaffiliated/fiddlerwoaroof) joined #forth 20:51:28 --- join: [X-Scale] (~ARM@214.20.108.93.rev.vodafone.pt) joined #forth 20:53:50 --- quit: X-Scale (Ping timeout: 240 seconds) 20:53:50 --- nick: [X-Scale] -> X-Scale 21:14:55 --- quit: qzo (Quit: WeeChat 1.6) 21:34:24 --- join: wa5qjh (~Thunderbi@121.54.90.143) joined #forth 21:48:01 --- join: [X-Scale] (~ARM@230.37.103.87.rev.vodafone.pt) joined #forth 21:49:22 --- quit: X-Scale (Ping timeout: 256 seconds) 21:49:47 --- nick: [X-Scale] -> X-Scale 22:06:47 --- quit: fiddlerwoaroof (Ping timeout: 258 seconds) 22:12:55 --- join: fiddlerwoaroof (~fiddlerwo@unaffiliated/fiddlerwoaroof) joined #forth 22:24:34 --- quit: proteusguy (Remote host closed the connection) 22:32:19 --- quit: fiddlerwoaroof (Ping timeout: 240 seconds) 22:39:03 --- join: fiddlerwoaroof (~fiddlerwo@unaffiliated/fiddlerwoaroof) joined #forth 22:56:24 --- join: proteusguy (~proteus-g@180.183.116.224) joined #forth 22:56:25 --- mode: ChanServ set +v proteusguy 23:25:06 --- join: impomatic (~impomatic@host86-170-205-91.range86-170.btcentralplus.com) joined #forth 23:26:16 qzo, isn't fig forths was available for 8bit cpus? 23:59:59 --- log: ended forth/17.03.27