00:00:00 --- log: started forth/18.09.27 00:03:41 --- join: dave9 (~dave@90.20.215.218.dyn.iprimus.net.au) joined #forth 00:14:02 --- quit: wa5qjh (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) 00:48:06 --- join: wa5qjh (~quassel@175.158.225.203) joined #forth 00:48:07 --- quit: wa5qjh (Changing host) 00:48:07 --- join: wa5qjh (~quassel@freebsd/user/wa5qjh) joined #forth 01:01:08 --- join: lemonpepper24 (~lemonpepp@nat-x098-040.reshsg.uci.edu) joined #forth 01:04:57 --- join: ncv (~neceve@unaffiliated/neceve) joined #forth 01:06:13 --- quit: dave9 (Quit: one love) 02:00:20 --- join: dave9 (~dave@90.20.215.218.dyn.iprimus.net.au) joined #forth 02:02:47 --- quit: ashirase (Ping timeout: 260 seconds) 02:07:02 --- join: ashirase (~ashirase@modemcable098.166-22-96.mc.videotron.ca) joined #forth 02:17:39 --- join: tabemann_ (~tabemann@2602:30a:c0d3:1890:ccf2:f6ec:5a58:6b88) joined #forth 02:18:16 --- quit: tabemann (Ping timeout: 264 seconds) 02:28:30 --- quit: groovy2shoes (Quit: moritura te salutat) 02:33:37 --- quit: nighty- (Quit: Disappears in a puff of smoke) 03:53:30 --- quit: wa5qjh (Ping timeout: 252 seconds) 03:55:18 --- join: wa5qjh (~quassel@175.158.225.205) joined #forth 03:55:19 --- quit: wa5qjh (Changing host) 03:55:19 --- join: wa5qjh (~quassel@freebsd/user/wa5qjh) joined #forth 04:00:48 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 04:32:42 --- quit: gravicappa (Ping timeout: 260 seconds) 04:34:48 --- join: gravicappa (~gravicapp@ppp83-237-174-131.pppoe.mtu-net.ru) joined #forth 05:18:28 --- join: nighty- (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth 06:00:28 --- quit: wa5qjh (Remote host closed the connection) 06:09:34 --- join: Guest5800_ (uid172710@gateway/web/irccloud.com/x-bwipozwsgsuwctdk) joined #forth 06:13:59 --- join: groovy2shoes (~groovy2sh@unaffiliated/groovebot) joined #forth 06:39:57 are there any forths with included "on-screen" stack monitor ? 07:13:08 --- quit: lemonpepper24 (Ping timeout: 272 seconds) 07:13:12 --- quit: pierpal (Read error: Connection reset by peer) 07:18:50 --- quit: tabemann_ (Ping timeout: 250 seconds) 07:35:17 --- join: pierpal (~pierpal@host102-235-dynamic.181-80-r.retail.telecomitalia.it) joined #forth 07:42:34 --- quit: NB0X-Matt-CA (Remote host closed the connection) 07:43:55 --- join: NB0X-Matt-CA (~nonlinear@unaffiliated/discrttm) joined #forth 07:44:03 --- quit: dave9 (Quit: one love) 07:46:30 --- quit: pierpal (Ping timeout: 252 seconds) 07:48:15 --- join: pierpal (~pierpal@host102-235-dynamic.181-80-r.retail.telecomitalia.it) joined #forth 07:50:53 --- quit: pierpal (Read error: Connection reset by peer) 07:51:11 --- join: pierpal (~pierpal@host102-235-dynamic.181-80-r.retail.telecomitalia.it) joined #forth 07:55:52 --- quit: pierpal (Ping timeout: 252 seconds) 08:30:30 --- quit: gravicappa (Ping timeout: 252 seconds) 08:44:21 --- quit: Zarutian (Ping timeout: 244 seconds) 08:51:30 --- join: Zarutian (~zarutian@173-133-17-89.fiber.hringdu.is) joined #forth 08:55:00 --- quit: NB0X-Matt-CA (Remote host closed the connection) 08:56:19 --- join: NB0X-Matt-CA (~nonlinear@unaffiliated/discrttm) joined #forth 09:10:53 some of the interfaces for retro show the stack as part of the ui (ri [console, ncurses], and the next iOS version) 09:25:35 crc: wanted to ask you about the i/o interfacing with retro. Where does that happen exactly? 09:26:37 --- join: pierpal (~pierpal@host102-235-dynamic.181-80-r.retail.telecomitalia.it) joined #forth 09:34:52 The interface layer typically adds opcodes for io, and words are then written to use these 09:37:41 crc: right, so how can an retro image go about detecting which set opcodes are being used? 09:37:57 e.g., https://pastebin.com/fgH2Agcb 09:39:12 Retro doesn't provide a means of detecting additional opcodes at this point. The glossary lists words and the interface layers that provide them. 09:41:03 this is one of the reasons why I like the 'hardware' interface model of DCPU-16. Easy discovery/enumeration of what is available 10:41:09 --- join: dys (~dys@p54BF567D.dip0.t-ipconnect.de) joined #forth 10:42:23 It'd be interesting to explore, but I'm unlikely to work on it until I have an application that needs it. 11:13:41 --- quit: ncv (Remote host closed the connection) 12:02:28 --- quit: pierpal (Ping timeout: 240 seconds) 12:22:48 --- join: john_metcalf (~digital_w@host86-191-55-174.range86-191.btcentralplus.com) joined #forth 13:01:45 --- join: pierpal (~pierpal@host168-226-dynamic.104-80-r.retail.telecomitalia.it) joined #forth 13:06:46 --- quit: john_metcalf (Ping timeout: 246 seconds) 13:08:24 --- join: john_metcalf (~digital_w@host109-148-228-105.range109-148.btcentralplus.com) joined #forth 13:44:33 --- quit: ashirase (Ping timeout: 252 seconds) 13:52:26 --- join: gravicappa (~gravicapp@ppp83-237-171-252.pppoe.mtu-net.ru) joined #forth 14:14:47 --- quit: gravicappa (Remote host closed the connection) 14:15:44 --- join: lemonpepper24 (~lemonpepp@dhcp-v072-027.mobile.uci.edu) joined #forth 14:19:23 --- quit: reepca (Read error: Connection reset by peer) 14:41:26 --- join: wa5qjh (~quassel@175.158.225.212) joined #forth 14:41:26 --- quit: wa5qjh (Changing host) 14:41:26 --- join: wa5qjh (~quassel@freebsd/user/wa5qjh) joined #forth 14:51:17 --- quit: wa5qjh (Remote host closed the connection) 14:54:09 --- join: ashirase (~ashirase@modemcable098.166-22-96.mc.videotron.ca) joined #forth 14:55:33 --- join: wa5qjh (~quassel@175.158.225.212) joined #forth 14:55:33 --- quit: wa5qjh (Changing host) 14:55:33 --- join: wa5qjh (~quassel@freebsd/user/wa5qjh) joined #forth 15:30:56 --- quit: lemonpepper24 (Ping timeout: 240 seconds) 15:42:24 I like the Nga VM a lot 15:42:55 MISC is real nice 15:57:44 --- quit: Guest5800_ (Quit: Connection closed for inactivity) 16:09:59 --- quit: dys (Ping timeout: 245 seconds) 16:45:56 --- quit: lonjil (Ping timeout: 240 seconds) 17:23:05 --- join: tabemann_ (~tabemann@110-84-181-166.mobile.uscc.net) joined #forth 17:28:31 --- nick: tabemann_ -> tabemann 18:03:32 --- quit: tabemann (Ping timeout: 260 seconds) 18:30:43 --- join: tabemann (~tabemann@2602:30a:c0d3:1890:ccf2:f6ec:5a58:6b88) joined #forth 18:31:53 --- quit: NB0X-Matt-CA (Remote host closed the connection) 18:33:16 --- join: NB0X-Matt-CA (~nonlinear@unaffiliated/discrttm) joined #forth 18:48:11 --- join: lonjil (~quassel@2a02:418:6050:ed15:ed15:ed15:e741:32d6) joined #forth 18:55:20 --- join: lemonpepper24 (~lemonpepp@nat-x097-121.reshsg.uci.edu) joined #forth 19:20:52 --- join: dave9 (~dave@90.20.215.218.dyn.iprimus.net.au) joined #forth 19:23:26 hi 19:27:29 --- quit: wa5qjh (Ping timeout: 245 seconds) 19:29:14 --- join: wa5qjh (~quassel@175.158.225.213) joined #forth 19:29:14 --- quit: wa5qjh (Changing host) 19:29:14 --- join: wa5qjh (~quassel@freebsd/user/wa5qjh) joined #forth 19:45:27 hi gays 19:45:31 sorry, guys 19:45:52 hi yunfan 19:45:54 that's the first time I've seen anyone make that typo 19:46:13 yunfan: not that there's anything wrong with that 19:46:22 that was my thought too 19:46:26 why correct yourself 19:46:45 * tabemann should get a Make America Gay Again hat 19:48:01 I wasted a bunch of time because S" doesn't work in interpreted contexts 19:48:43 and I was trying to execute S" 1 1 + ." EVALUATE and was wondering why it was crashing 19:49:30 Forth is rad 19:50:55 tabemann: not everyone is gay, so i am sorry 19:51:10 have you guys every heard of the nucleus os? 19:51:21 no I haven't 19:51:21 i just found its kernel is very tiny, only 2kb 19:51:31 and provide much extending features 19:51:46 is it written in forth? 19:51:48 it used to be installed on a vari of dumb cellphone 19:51:56 i dont konw, its closed source 19:52:19 and i am guess that too, that's why i came here asking 19:52:24 the thing to me, though, is why would I spend my own time working with something that's closed source 19:53:18 well. just ask 19:55:07 --- quit: dddddd (Read error: Connection reset by peer) 19:56:06 too bad Open Firmware isn't around anymore 19:56:19 yes 19:56:33 but there's little kernel 19:56:39 almost on every android phone 19:56:55 if someone could port a forth on it i thinks that would be very interesting 19:57:59 the main thing with porting Forth to Android devices are the drivers 19:58:19 because I presume the driver functionality for each given phone is closed 19:58:41 meaning that for any indivdual phone you'd have to reverse-engineer the hardware interfaces 19:59:19 you might be better off writing a Forth targeted for Android that executes in userspace 19:59:33 where then it'd essentially be a Linux application 19:59:45 tabemann: i am not meaning porting forth to android os 20:00:27 tabemann: almost every android phone has a bootloader mode, and that os use a kernel named little kernel which is open sourced 20:00:32 and its a RT os 20:02:34 ah 20:15:08 --- quit: pierpal (Ping timeout: 240 seconds) 20:38:15 also check here https://hackaday.com/2018/05/15/retro-computer-badge-for-hackaday-belgrade-has-everything-you-wished-for-back-in-the-day/ 20:38:25 i think a forth would be better than the origin tiny basic 20:49:20 --- quit: dave9 (Quit: dave's not here) 21:45:58 --- join: reepca (~user@208.89.170.250) joined #forth 22:06:18 --- quit: reepca (Read error: Connection reset by peer) 22:22:17 --- join: tusj (~tusj@185.176.245.99) joined #forth 22:31:49 --- join: dys (~dys@p54BF5525.dip0.t-ipconnect.de) joined #forth 22:38:48 --- quit: NB0X-Matt-CA (Remote host closed the connection) 22:40:08 --- join: NB0X-Matt-CA (~nonlinear@unaffiliated/discrttm) joined #forth 22:48:52 --- quit: john_metcalf (Ping timeout: 264 seconds) 22:51:07 --- quit: lemonpepper24 (Ping timeout: 260 seconds) 23:16:42 --- join: dave9 (~dave@90.20.215.218.dyn.iprimus.net.au) joined #forth 23:17:00 --- quit: tusj (Ping timeout: 244 seconds) 23:32:53 --- join: tusj (~tusj@185.176.245.99) joined #forth 23:48:17 --- quit: jedb (Ping timeout: 260 seconds) 23:48:35 --- join: jedb (~jedb@199.66.90.209) joined #forth 23:59:59 --- log: ended forth/18.09.27