00:00:00 --- log: started forth/15.02.03 00:12:13 --- join: idknow (~idknow@c-73-28-150-83.hsd1.fl.comcast.net) joined #forth 00:43:40 --- nick: idknow -> idknow_ 00:48:59 --- part: idknow_ left #forth 01:02:56 --- join: lynx` (~lynx@46.21.154.83) joined #forth 01:07:12 --- quit: mnemnion (Remote host closed the connection) 01:07:42 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 01:12:13 --- quit: mnemnion (Ping timeout: 255 seconds) 01:58:25 --- quit: bluekelp (Ping timeout: 245 seconds) 02:02:55 --- join: bluekelp (~bluekelp@2001:470:1:41:ec8f:de46:766a:1d3) joined #forth 02:02:55 --- mode: ChanServ set +v bluekelp 02:11:22 --- quit: lynx` (Remote host closed the connection) 02:19:45 --- join: fantazo (~fantazo@213.129.230.10) joined #forth 02:27:48 --- quit: denysonique (Ping timeout: 250 seconds) 02:28:05 --- join: denysonique (~quassel@31.55.82.111) joined #forth 02:28:05 --- quit: denysonique (Changing host) 02:28:05 --- join: denysonique (~quassel@unaffiliated/dennisonicc) joined #forth 03:47:18 --- join: true-grue (~grue@95-27-137-181.broadband.corbina.ru) joined #forth 04:59:37 --- quit: proteusguy (Ping timeout: 250 seconds) 04:59:37 --- quit: bjorkintosh (Ping timeout: 250 seconds) 05:00:12 --- join: bjorkintosh (~bjork@ip68-13-229-200.ok.ok.cox.net) joined #forth 05:00:48 --- join: proteusguy (~proteusgu@183.89.209.51) joined #forth 05:00:48 --- mode: ChanServ set +v proteusguy 05:04:53 --- join: nighty^ (~nighty@hokuriku.rural-networks.com) joined #forth 05:08:04 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 05:12:43 --- quit: mnemnion (Ping timeout: 244 seconds) 05:46:17 --- join: ASau` (~user@46.114.46.44) joined #forth 05:49:48 --- quit: ASau (Ping timeout: 252 seconds) 05:50:11 --- nick: ASau` -> ASau 06:33:29 --- quit: denysonique (Ping timeout: 264 seconds) 06:33:50 --- join: denysonique (~quassel@unaffiliated/dennisonicc) joined #forth 06:41:52 --- quit: Bahman (Ping timeout: 246 seconds) 06:43:50 --- quit: fantazo (Quit: Verlassend) 06:45:30 --- join: Bahman (~Bahman@89.41.21.166) joined #forth 06:54:14 --- quit: proteusguy (Remote host closed the connection) 07:08:12 --- quit: darkf (Quit: Leaving) 07:15:51 --- join: proteusguy (~proteusgu@ppp-110-168-230-9.revip5.asianet.co.th) joined #forth 07:16:13 --- mode: ChanServ set +v proteusguy 07:34:44 --- quit: tangentstorm (Quit: WeeChat 0.3.2) 08:29:11 --- quit: Bahman (Ping timeout: 245 seconds) 08:30:59 --- join: Bahman (~Bahman@89.41.21.166) joined #forth 08:37:26 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 08:54:38 --- join: fantazo (~fantazo@089144208227.atnat0017.highway.a1.net) joined #forth 09:01:22 --- join: I440r (~mark4@38.122.200.194) joined #forth 09:01:22 --- mode: ChanServ set +o I440r 09:31:44 --- quit: Bahman (Quit: Gone with the wind and the rain on an airplane...) 09:52:49 --- quit: I440r (Quit: Leaving) 10:03:40 --- join: Zarutian (~Adium@168-110-22-46.fiber.hringdu.is) joined #forth 10:48:02 --- quit: joneshf-laptop (Ping timeout: 245 seconds) 10:54:45 --- join: joneshf-laptop (~joneshf@98.208.35.89) joined #forth 12:15:52 --- quit: Zarutian (Quit: Leaving.) 12:49:33 --- quit: fantazo (Quit: Verlassend) 13:22:14 --- quit: nighty^ (Quit: Disappears in a puff of smoke) 14:07:26 --- join: nighty^ (~nighty@hokuriku.rural-networks.com) joined #forth 14:22:58 --- quit: bluekelp (Ping timeout: 265 seconds) 14:23:05 --- join: bluekelp (~bluekelp@2001:470:1:41:ec8f:de46:766a:1d3) joined #forth 14:23:05 --- mode: ChanServ set +v bluekelp 14:32:11 --- join: MrMobius (~MrMobius@ip-64-134-32-114.public.wayport.net) joined #forth 14:33:58 --- nick: MrMobius -> MrMobius_ 14:38:08 --- quit: denysonique (Ping timeout: 240 seconds) 14:41:16 --- join: lynx` (~lynx@46.21.154.83) joined #forth 14:49:37 --- quit: nighty^ (Quit: Disappears in a puff of smoke) 14:51:33 --- join: nighty^ (~nighty@hokuriku.rural-networks.com) joined #forth 15:03:58 --- join: denysonique (~quassel@unaffiliated/dennisonicc) joined #forth 15:05:53 --- quit: irsol (Ping timeout: 244 seconds) 15:07:37 --- join: irsol (~irsol@unaffiliated/contempt) joined #forth 15:39:23 --- quit: true-grue (Read error: Connection reset by peer) 16:14:57 --- quit: MrMobius_ (Ping timeout: 250 seconds) 16:19:18 --- quit: nighty^ (Quit: Disappears in a puff of smoke) 16:28:12 --- join: tangentstorm (~michal@108-218-151-22.lightspeed.rcsntx.sbcglobal.net) joined #forth 17:08:05 --- quit: denysonique (Ping timeout: 264 seconds) 17:14:19 --- quit: proteusguy (Ping timeout: 250 seconds) 17:36:46 --- join: proteusguy (~proteusgu@ppp-110-168-229-209.revip5.asianet.co.th) joined #forth 17:36:46 --- mode: ChanServ set +v proteusguy 18:26:19 --- join: denysonique (~quassel@31.55.77.74) joined #forth 18:26:19 --- quit: denysonique (Changing host) 18:26:19 --- join: denysonique (~quassel@unaffiliated/dennisonicc) joined #forth 18:28:55 anybody ever use a ICOP(/DMP) eBox? 18:29:29 given the power consumption & price, they seem like a steal. 18:30:21 lynx: what are those? 18:31:35 --- join: darkf (~darkf___@unaffiliated/darkf) joined #forth 18:33:02 http://www.compactpc.com.tw/product.aspx?act=detail&id=340 18:33:20 there is a "C2" model that includes two "COM"-style RS-232 ports. 18:33:34 runs about ~$115 US. 18:36:02 first heard of it when I saw a video of one of the developers of KolibriOS boot off one. 18:37:08 runs DOS out of the box, with Linux and FreeBSD running apparently well with only minor patching. 18:39:13 I was impressed, too, that these things consume only ~5 watts while running. 18:40:42 5 watts are a lot! Its is like 20 quarter watt resistors. 18:42:36 http://www.ti.com/lsds/ti/microcontrollers_16-bit_32-bit/msp/ultra-low_power/msp430frxx_fram/products.page#p2066=4;128&p3087=91.667;110&p1342=LCD 18:43:05 something like that running off a single solar cell might do it 18:44:59 it's not a lot for PC architecture "in a box," imho. 18:45:31 granted, it doesn't touch bona fide microcontroller boards, but it comes stock with a lot of peripherals setup & rare to go. 19:02:46 lynx`: why you need a read serial port? 19:03:15 to drive a MIDI interface with low latency. 19:04:57 lynx`: also this dont looks cool, i recomment you those tvbox with hdmi out and sata port 19:05:15 what about a usb2ttl? 19:05:33 or, in another application I had in mind, to read data from a "luggable" weather station (which uses a plain ol' serial link). 19:06:58 not terribly impressed by the latency I've experience over USB interfaces. 19:07:04 --- join: saml_ (~saml@cpe-24-102-97-97.nyc.res.rr.com) joined #forth 19:08:00 what about the eBox don't you like? for an application that works mostly out of RAM once booted up, why would HDMI or SATA be a requirement? 19:08:12 s/requirement/helpful 19:12:59 (and meant to add: has minimal video requirements) 19:14:27 lynx`: all of them :] 19:14:35 list at your page above 19:19:45 --- quit: ASau (Read error: No route to host) 19:26:53 --- join: ASau (~user@46.114.46.44) joined #forth 20:37:37 --- quit: saml_ (Quit: Leaving) 21:10:44 --- quit: proteusguy (Ping timeout: 264 seconds) 21:12:49 yunfan: do you have any idea about how should we translate the English term "threaded code" into Chinese ? 21:23:55 --- join: proteusguy (~proteusgu@ppp-110-168-229-143.revip5.asianet.co.th) joined #forth 21:23:55 --- mode: ChanServ set +v proteusguy 21:25:47 xyh: isnt there any exists translation for that? 21:28:09 yunfan: do you know one? 21:29:49 xyh: http://blog.csdn.net/wxj729/article/details/313730 here they use '串线编码' 21:31:42 I know in the auther call it 線串碼 21:33:20 xyh: i dont like it , but i cant give a better solution 21:44:38 --- quit: lynx` (Remote host closed the connection) 21:50:54 --- quit: proteusguy (Remote host closed the connection) 21:51:24 does anyone knows any rationale about the creation of the term "threaded code" ? 21:51:49 not really, but i could take a guess. 21:52:05 do you know what the expression 'thread a needle' means? like in sewing? 21:56:32 --- join: dys (~user@ip-109-44-211-134.web.vodafone.de) joined #forth 22:02:31 tangentstorm: I know "thread a needle", I use to help my grandma do that. 22:05:40 :) yeah. so... you can 'thread' all kinds of little objects on the same piece of thread, making a chain. 22:05:43 well not a chain. 22:05:57 i don't know what you'd call it. 22:06:19 garland? 22:06:58 like beads on a necklace or something. 22:07:28 anyway.. that's how i've always thought of it. maybe it means something completely different. 22:07:40 --- join: proteusguy (~proteusgu@183.89.209.51) joined #forth 22:07:40 --- mode: ChanServ set +v proteusguy 22:10:59 tangentstorm: so, a function address as a bead, we have a "function address necklace", very interesting view :) 22:11:30 :) 22:27:24 tangentstorm: in the vm I am designing I will use the word "bead" to call the elements in function-body. 22:27:33 the size of each bead is four cells, two for instruction, two for the argument of the instruction. 22:30:02 --- quit: denysonique (Ping timeout: 256 seconds) 22:34:13 --- join: denysonique (~quassel@unaffiliated/dennisonicc) joined #forth 22:55:06 xyh, are you pushing beads onto the stack? 23:00:43 those are some big instructions 23:00:51 well.. how big is a cell? 23:02:58 --- join: true-grue (~grue@95-27-167-194.broadband.corbina.ru) joined #forth 23:06:44 proteusguy: no, I push objects onto argument-stack, one object is of two cell one cell for title[as type] one cell for value. [so an instruction and an argument of the instruction are all objects] 23:07:33 tangentstorm: a cell is of 32 bits in the common-lisp version of the VM. 23:16:15 --- join: impomatic_ (~chatzilla@73.156.200.146.dyn.plus.net) joined #forth 23:16:59 --- quit: impomatic (Ping timeout: 245 seconds) 23:17:08 --- nick: impomatic_ -> impomatic 23:22:21 --- join: MrMobius_ (~MrMobius@2601:f:400:1241:a461:79d6:954e:a25f) joined #forth 23:27:06 xyh, ok just making sure. :-) Those are big instructions. Are you encoding multiple instructions per cell? I'm guessing not. 23:28:41 Or by instruction do you mean op codes that build a small function? 23:32:44 I do not have instruction encoding, an "encoding" will be generated when you compile the VM. for example, "branch" "function-call""tail-function-call" "literal-char" "literal-string" ... are all instructions, [actually they are not named in this way] 23:34:13 --- quit: proteusguy (Ping timeout: 255 seconds) 23:37:52 --- quit: MrMobius_ (Ping timeout: 265 seconds) 23:48:32 actually I am not sure about the design yet, 23:48:33 an element in a function-body is [instruction, object], 23:48:33 for example [function-call, address], [tail-function-call, address], [branch, offset], ... 23:48:44 my wish is to let the instruction can be defined by user as easy as to define a function. 23:49:02 so instruction [must] have type too, some of them are primitive-instructions, 23:49:02 some of them are user-defined-instructions. 23:58:53 --- join: proteusguy (~proteusgu@183.89.209.51) joined #forth 23:58:53 --- mode: ChanServ set +v proteusguy 23:59:59 --- log: ended forth/15.02.03