00:00:00 --- log: started forth/07.07.30 00:46:18 --- quit: jns (Read error: 113 (No route to host)) 00:47:09 --- quit: skas_wk ("I'm outta here.") 01:26:14 --- join: kefeer (n=kefeer@82.193.155.229) joined #forth 01:26:46 --- quit: kc5tja (Remote closed the connection) 01:34:58 --- join: kc5tja (n=kc5tja@c-24-6-88-51.hsd1.ca.comcast.net) joined #forth 02:37:28 --- part: edrx left #forth 05:39:28 --- join: timlarson_ (n=timlarso@65.116.199.19) joined #forth 05:54:17 slava32, no idea. Why? 05:55:45 --- join: Quartus__ (n=Quartus_@205.205.50.2) joined #forth 06:17:47 --- quit: Quartus (Read error: 110 (Connection timed out)) 07:08:50 --- quit: H4ns ("using sirc version 2.211+ssfe") 07:09:11 --- join: H4ns (i=hans@netzhansa.com) joined #forth 07:33:11 --- quit: Quartus__ (Read error: 104 (Connection reset by peer)) 07:45:34 --- join: Crest (n=crest@p5489FB71.dip.t-dialin.net) joined #forth 08:29:44 --- join: Quartus__ (n=Quartus_@205.205.50.1) joined #forth 09:22:57 i've got a question again, which is a result of my inexperience with forth. in maisforth, emit, emit?, key and key? are just simple routines, non-vectored. maisforth is supposed to be standard ANS forth, and what i'd like to do is set up a vectoring mechanism so that i can change the i/o channel for key/emit at run time. 09:23:53 i propably need to define one or more variables pointing to the words that should be called when one of the four routines is called. now, is there a standard mechanism to do an indirect call to an address that comes from a variable? 09:24:24 (i'm aware that this may not be a standard forth question and may require ansforth knowledge, but maybe it is not?) 09:25:34 --- join: yumehito (n=yumehito@b-internet.87.103.254.70.snt.ru) joined #forth 09:27:09 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 09:27:09 --- mode: ChanServ set +o tathi 09:29:55 h4ns there used to be a word caled perform 09:29:59 : perform @ execute ; 09:30:33 dont know if its in the standard. they may have renamed it to @execute or something 09:30:51 CODE EXECUTE D X TFR REG D PULS X ) JMP END-CODE 09:30:56 that looks cool, thanks! 09:31:01 these days the usual way is to use DEFER (http://forth200x.org/deferred.html) 09:31:11 but looks like maisforth is older than that :) 09:31:27 i'd rather use a more modern forth, but i'm using a 6809 which basically is dead :) 09:34:16 do you have the word defer ? 09:34:19 defer blah 09:34:44 that creates what tathi was talking about, a deferred word. which is basically a self executing variable 09:35:01 ya. can be defined in standard forth, in fact that page at forth200x.org gives an implementation. 09:35:04 no, defer is not there. 09:35:17 erm mor like a self executing constant that you can change... 09:35:23 ok 09:35:32 maisforth is derived of another old 6809 forth, and i think that it is ans. but i'm not sure. 09:36:00 i doubt it, its more likely 83 std or 79 or even fig 09:36:05 --- quit: H4ns (Remote closed the connection) 09:36:11 i would be supprised if it was ans 09:36:35 --- join: H4ns (i=hans@netzhansa.com) joined #forth 09:36:38 dang. 09:36:40 lol 09:36:43 no, defer is not there. 09:36:45 do you have the word postpone defined? 09:36:59 if you have postpone its an ans(ish) forth 09:37:07 yep, postpone is there 09:37:17 otherwise you will have the words compile and [compile] which may also be tehre 09:37:19 there 09:37:26 maisforth appears to be camelforth updated to ANS compliance 09:37:30 my most hated word in all ans forth heh 09:37:30 right. 09:37:43 aha 09:37:43 i don't have much of a choice, really. 09:37:47 camelforth was good! 09:38:01 i'm looking for a forth that i can run in a fpga, and i already had a 6809 based system running. 09:38:16 i was also looking at microcore, but there does not seem to be interactive forth available for it. 09:38:38 where isforth does the xor on the immediate flags of a word with current state to decide weather to execute or compile... thats from camel i believe 09:40:11 H4ns: just use the definitions of DEFER and IS from forth200x.org/deferred.html 09:40:15 they should work for you 09:40:51 i'll look into that, thanks! 09:41:23 ah, great! that looks similar to what amforth has. 09:42:23 thanks for helping with my babysteps. 09:50:46 --- quit: Quartus__ ("used jmIrc") 09:51:00 --- join: Quartus__ (n=Quartus_@205.205.50.1) joined #forth 10:14:04 --- quit: Quartus__ (Read error: 104 (Connection reset by peer)) 10:48:26 --- quit: H4ns (Read error: 110 (Connection timed out)) 11:04:39 --- join: edrx (n=Eduardo@200.217.105.44) joined #forth 11:17:32 --- quit: kefeer ("WeeChat 0.1.9") 11:25:27 --- join: Al2O3 (n=Al2O3@adsl-75-40-29-254.dsl.rcsntx.sbcglobal.net) joined #forth 11:45:43 --- join: Quartus__ (n=Quartus_@205.205.50.1) joined #forth 11:56:45 --- quit: Al2O3 (Read error: 104 (Connection reset by peer)) 12:27:59 --- join: smalltalk (n=dr@Le6e9.l.pppool.de) joined #forth 12:31:01 --- quit: Quartus__ (Read error: 104 (Connection reset by peer)) 12:39:25 --- join: JasonWoof (n=jason@c-24-63-217-45.hsd1.ma.comcast.net) joined #forth 12:39:25 --- mode: ChanServ set +o JasonWoof 13:00:52 --- part: smalltalk left #forth 13:23:29 --- quit: timlarson_ ("Leaving") 13:43:35 --- join: snoopy_1711 (i=snoopy_1@dslb-084-058-186-028.pools.arcor-ip.net) joined #forth 13:49:59 --- quit: Snoopy42 (Read error: 131 (Connection reset by peer)) 13:50:15 --- nick: snoopy_1711 -> Snoopy42 14:42:19 --- join: H4ns (i=hans@netzhansa.com) joined #forth 14:48:05 --- join: Quartus__ (n=Quartus_@205.205.50.1) joined #forth 14:50:03 hey 14:50:58 hi 14:52:09 how goes it? 14:58:20 ok 14:58:21 you? 14:59:32 another day, another 63 cents after taxes 14:59:52 --- join: gihgi (n=irc@bzq-88-155-128-198.red.bezeqint.net) joined #forth 15:02:08 --- join: crest_ (n=crest@p5489F6AD.dip.t-dialin.net) joined #forth 15:06:04 you're rich! 15:06:11 :) 15:06:41 well-off, at least :). Halfway to a cup of coffee 15:11:06 --- part: edrx left #forth 15:18:27 --- join: Al2O3 (n=Al2O3@adsl-75-40-29-254.dsl.rcsntx.sbcglobal.net) joined #forth 15:19:39 --- quit: Crest (Read error: 110 (Connection timed out)) 15:20:54 tathi: i forgot, how do i sign exend a byte on ppc? 15:31:11 --- quit: gihgi ("BitchX: it's what's for lunch") 15:31:43 slava, what makes you think Doty vanity-surfs the log? 15:32:49 slava: srwa? 15:33:05 there's an a in there somewhere 15:33:09 a is for arithmetic 15:36:17 sraw 15:36:21 just looked it up 15:39:47 that's a right shift 15:46:09 --- join: Quartus (n=neal@CPE0001023f6e4f-CM001947482b20.cpe.net.cable.rogers.com) joined #forth 15:46:09 --- mode: ChanServ set +o Quartus 15:50:42 Doesn't PowerPC have a 'load byte signed' instruction? 15:50:50 no 15:51:01 there's load halfword signed 15:51:05 I know it has signed and unsigned variants of loading a half-word and word. 15:51:27 hmmm... 15:52:38 If the PowerPC had become the dominant processor architecture, it either already would have been added as an instruction by now, OR, I'd know how to synthesize its capability. :) 15:52:46 The quickest way is to use a look-up table. :D 15:53:02 Not sure if you're willing to invest 1KiB for that though. :) 15:54:52 http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.aixassem/doc/alangref/extsb.htm 15:57:08 I still cannot help but think that IBM was waiting for YEARS to capitalize on the opportunity to introduce a CPU with a real EIEIO instruction. 16:01:52 --- join: Al2O3_ (n=Al2O3@adsl-75-30-128-126.dsl.rcsntx.sbcglobal.net) joined #forth 16:16:03 --- quit: Al2O3 (Connection timed out) 16:21:45 lol 16:22:01 kc5tja: by "load" you mean fetch from memory? 17:34:01 slava: extsb 17:34:43 EXTend Signed Byte 17:35:35 oh, kc5tja said it first 17:39:39 and with more style and panache! 17:40:07 hehe 17:41:18 kc5tja: And don't forget the LFSUX instruction. :) 17:53:03 JasonWoof: Yes. 17:54:38 Load Float Signed Update-index-register ______ ? 17:55:47 Oh, I see -- so the *real* assembly operations use 'x' to indicate indexed. 17:56:20 * JasonWoof looks it up 17:56:36 lfsux: load floating-point register using single-precision and indexd addressing with EA update 17:56:39 sheesh, that's a mouthful 18:02:07 Interestingly, there's no STFU instruction. :) 18:02:24 It comes the closest with the POWER2 instruction STFQU. ;) 18:05:04 it's got eieio... what more could you possibly ask for ;) 18:05:20 6809 has a real HCF instruction. :) 18:05:28 Which does precisely as you'd expect apparently. 18:05:37 Halt and Catch Fire. 18:05:43 --- join: nighty^ (n=nighty@p2136-adsau16honb13-acca.tokyo.ocn.ne.jp) joined #forth 18:07:34 (It's a "test" opcode Motorola used with the chip which is formally undocumented, but which causes the CPU to drive the bus with a valid address and some data on D0-D7. It'd be innocently innocuous were it not for the fact that the R/W line is configured for READING when it's driving the databus; hence, the CPU tends to short one or more of its data pins to ground if RAM says Dx is high and it drives the same pin low. oops.) 18:09:12 nice 18:30:50 --- quit: Al2O3_ (Client Quit) 18:31:43 tathi: ah, that's it 18:31:44 thanks 18:41:51 --- quit: tathi ("'night all") 18:54:32 --- quit: paf ("Leaving") 21:20:13 --- join: jeberle (n=jeberle@adsl-75-36-174-113.dsl.pltn13.sbcglobal.net) joined #forth 21:39:56 --- join: Al2O3 (n=Al2O3@pool-71-164-169-103.dllstx.fios.verizon.net) joined #forth 22:02:32 --- part: jeberle left #forth 22:14:43 --- quit: Al2O3 () 22:16:03 --- join: Al2O3 (n=Al2O3@pool-71-164-169-103.dllstx.fios.verizon.net) joined #forth 23:16:42 --- quit: Al2O3 () 23:32:02 --- quit: slava () 23:59:59 --- log: ended forth/07.07.30