00:00:00 --- log: started forth/17.02.27 00:38:19 --- quit: wa5qjh (Read error: Connection reset by peer) 00:40:32 --- join: wa5qjh (~Thunderbi@112.198.69.213) joined #forth 00:44:36 --- quit: wa5qjh (Remote host closed the connection) 00:46:32 --- join: wa5qjh (~Thunderbi@112.198.68.221) joined #forth 01:12:51 --- join: impomatic (~impomatic@host86-164-38-224.range86-164.btcentralplus.com) joined #forth 01:21:26 --- quit: wa5qjh (Remote host closed the connection) 01:23:11 --- join: wa5qjh (~Thunderbi@112.198.69.117) joined #forth 02:08:08 --- join: newcup (newcup@peruna.fi) joined #forth 02:25:00 --- quit: proteusguy (Remote host closed the connection) 02:35:05 --- quit: nighty (Quit: Disappears in a puff of smoke) 03:05:38 --- quit: pdewacht_ (Remote host closed the connection) 03:21:22 --- join: proteusguy (~proteus-g@49.228.114.112) joined #forth 03:21:22 --- mode: ChanServ set +v proteusguy 03:25:01 --- join: pdewacht (~repent@kulon.2k38.be) joined #forth 03:27:37 --- join: nighty (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth 04:17:27 --- join: GeDaMo (~GeDaMo@212.225.112.221) joined #forth 05:48:58 --- quit: dual (Ping timeout: 260 seconds) 05:50:26 --- join: dual (~bonafide@subzeroup.core.rzwireless.net) joined #forth 05:59:20 --- quit: wa5qjh (Remote host closed the connection) 07:02:32 --- quit: dual (Ping timeout: 264 seconds) 07:37:42 --- join: dual (~bonafide@cpe-74-75-153-119.maine.res.rr.com) joined #forth 07:53:18 --- join: dual_ (~bonafide@cpe-74-75-153-119.maine.res.rr.com) joined #forth 08:10:39 --- join: true-grue (~true-grue@176.14.222.10) joined #forth 08:16:15 --- join: neceve (~ncv@unaffiliated/neceve) joined #forth 08:19:32 --- quit: dual_ (Quit: Make it idiot proof and someone will make a better idiot.) 08:42:10 --- quit: neceve (Quit: Konversation terminated!) 09:11:00 --- nick: josh5ton1 -> josh5tone 09:52:03 interesting. what is pumpkindb for? the docs say "event store" but that doesn't mean anything to me. looks maybe like a simple pub/sub or similar? 09:58:35 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 09:59:14 --- join: Zarutian_ (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 09:59:14 --- quit: Zarutian (Read error: Connection reset by peer) 09:59:14 --- nick: Zarutian_ -> Zarutian 10:12:30 I'm playing with a little bytecode VM, and thinking of storing type- and GC-metadata in the top 16 bits of an x86-64 pointer (since only 48 bits are actually used). 10:12:38 I know there are a few implementers who frequent this channel 10:12:49 does anyone know of specific drawbacks for doing this? 10:13:18 it has the benefit that I can treat all cells in my stack as (void*), and still handle all the metadata I want for non-stack objects you'd use pointers for 10:15:11 yunfan: I be interested to know how pumpkindb compares to forthql. https://www.reddit.com/r/programming/comments/5wav06/pumpkindb_01_an_event_sourcing_database_engine/dea8xla/ 10:23:57 John[Lisbeth]: other than having to mask out those bits? not that I know of. 10:24:08 sorry John[Lisbeth] 10:24:19 meant josh5tone 10:29:37 I checked, and apparently there's a nuance in x86-64 -- if the 48th bit is a 1, you extend 1s to the high bits 10:29:40 0s otherwise 10:30:10 but it seems that 64-bit Windows and Linux kernels cap user space memory at 0x7f... 10:30:15 that happens when the value is treated as a pointer, no? 10:30:20 yes 10:30:30 and I did some testing -- I do have to mask it, otherwise it'll bork and I get a bus error 10:30:42 (sure would be nice if I didn't have to mask it!) 10:30:44 if you do the masking out as above then you wont run into the issue 10:30:54 there you go 10:31:33 some things are easy to find (and Stackoverflow will give you a hundred answers), but others are surprisingly difficult 10:33:49 another trick, to handle various +, - and such operations polymorphically is to use the type tag as an index into an jump table, if there is no sensical course of action for a particular operation then the entry in the jump table for it just points to an exception thrower. 10:59:54 that's really interesting... my current interpreter uses computed goto for instruction dispatch -- I could add something like that after the arithmetic op has been reached 11:00:36 --- join: gravicappa (~gravicapp@ppp83-237-165-33.pppoe.mtu-net.ru) joined #forth 11:00:46 could even make it handle casting of differing types by multiplying the type tags or something to create all possible operations 11:09:38 http://www.forth.org/svfig/kk/02-2010-Falvo.pdf 11:15:21 --- join: user10001012 (~user@h69-21-248-248.crlbnm.broadband.dynamic.tds.net) joined #forth 11:22:20 --- quit: Zarutian (Quit: Zarutian) 12:16:11 --- quit: user10001012 (Read error: Connection reset by peer) 12:45:01 --- quit: gravicappa (Ping timeout: 240 seconds) 13:04:11 --- quit: John[Lisbeth] (Ping timeout: 255 seconds) 13:05:56 --- quit: GeDaMo (Remote host closed the connection) 13:15:47 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 13:15:59 --- quit: Zarutian (Read error: Connection reset by peer) 13:36:08 --- quit: impomatic (Ping timeout: 255 seconds) 13:36:47 --- join: impomatic_ (~impomatic@host86-144-19-161.range86-144.btcentralplus.com) joined #forth 13:36:51 --- nick: impomatic_ -> impomatic 13:42:56 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 13:44:29 --- quit: true-grue (Read error: Connection reset by peer) 13:45:50 --- join: newuser|53046 (5744116b@gateway/web/cgi-irc/kiwiirc.com/ip.87.68.17.107) joined #forth 15:12:43 --- quit: dys (Ping timeout: 268 seconds) 15:52:09 --- quit: nighty (Quit: Disappears in a puff of smoke) 15:56:08 --- quit: zy]x[yz (Read error: Connection reset by peer) 15:57:49 --- join: zy]x[yz (~corey@unaffiliated/cmtptr) joined #forth 16:01:36 --- quit: ovf (Ping timeout: 245 seconds) 16:02:02 --- quit: tangentstorm (Ping timeout: 245 seconds) 16:02:23 --- join: tangentstorm (michal@2600:3c03::f03c:91ff:fec8:caab) joined #forth 16:02:26 --- quit: Vendan (Ping timeout: 245 seconds) 16:06:49 --- join: ovf (sid19068@gateway/web/irccloud.com/x-tcxueksuzhpeemvl) joined #forth 16:10:19 --- join: Vendan (~Vendan@li469-176.members.linode.com) joined #forth 16:20:33 how can i decipher error codes regarding files on gforth linux? 16:37:37 --- join: nighty (~nighty@d246113.ppp.asahi-net.or.jp) joined #forth 16:40:54 --- quit: dograt_ (Ping timeout: 268 seconds) 16:48:06 --- join: vsg1990 (~vsg1990@static-72-88-80-103.bflony.fios.verizon.net) joined #forth 16:49:18 --- quit: Zarutian (Ping timeout: 260 seconds) 18:07:14 newuser|53046: my guess is they're just linux/unix errno() codes? (disclaimer: i'm not a gforth user) 18:13:32 yup , thanks , found it here : /usr/include/errno.h 18:14:50 hmm - oddly, for me, it doesn't work :) 18:15:09 but searching online I found: 18:15:12 s" foo.in" r/o open-file throw Value fd-in 18:15:38 gives a plaintext message. the number on the stack didn't seem to (?) correspond to anything in errno.h (on my system) 18:22:46 you could get strerror from string.h if you wanted using the C interface 18:23:37 --- quit: newuser|53046 (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client) 18:24:16 --- join: newuser|10459 (57440351@gateway/web/cgi-irc/kiwiirc.com/ip.87.68.3.81) joined #forth 18:44:26 --- quit: LeCamarade (Ping timeout: 240 seconds) 18:49:52 --- join: LeCamarade (~revence@139.59.111.106) joined #forth 19:11:42 --- join: neceve (~ncv@86.125.230.85) joined #forth 19:11:42 --- quit: neceve (Changing host) 19:11:42 --- join: neceve (~ncv@unaffiliated/neceve) joined #forth 20:05:19 josh5tone, it's an interesting idea. I'm working on a strongly typed stack based threaded language and have yet to decide on my implementation detail but something like that is consideration. 20:24:55 --- quit: newuser|10459 (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client) 20:37:32 --- join: ACE_Recliner (~ACE_Recli@c-50-165-178-74.hsd1.in.comcast.net) joined #forth 20:42:38 --- quit: ACE_Recliner (Ping timeout: 260 seconds) 20:46:50 --- join: ACE_Recliner (~ACE_Recli@c-50-165-178-74.hsd1.in.comcast.net) joined #forth 21:46:20 --- join: dograt (~dograt@unaffiliated/dograt) joined #forth 21:51:22 --- quit: vsg1990 (Quit: Leaving) 22:33:44 --- join: dys (~dys@ip-109-40-2-98.web.vodafone.de) joined #forth 23:18:42 --- quit: neceve (Quit: Konversation terminated!) 23:59:59 --- log: ended forth/17.02.27