00:00:00 --- log: started forth/05.08.03 00:08:17 --- quit: jdrake (Read error: 104 (Connection reset by peer)) 00:57:04 --- join: arke_ (~chris@p54A7E6DE.dip.t-dialin.net) joined #forth 01:06:45 --- quit: JasonWoof ("off to bed") 01:14:46 --- quit: arke (Read error: 110 (Connection timed out)) 02:25:10 --- join: Topaz (~top@spc1-horn1-6-0-cust128.cosh.broadband.ntl.com) joined #forth 04:04:46 --- quit: Topaz ("Leaving") 05:33:39 --- nick: Raystm2 -> nanst 05:39:15 --- nick: nanst -> nanstm 05:42:30 --- join: saon (1000@c-66-177-224-235.hsd1.fl.comcast.net) joined #forth 06:26:16 --- join: PoppaVic (~pete@0-1pool67-86.nas22.chicago4.il.us.da.qwest.net) joined #forth 06:26:33 G'day 08:44:22 --- quit: OrngeTide ("off to work.") 09:14:58 --- nick: arke_ -> arke 09:28:43 --- join: JasonWoof (~jason@Herkamire.student.supporter.pdpc) joined #forth 09:28:43 --- mode: ChanServ set +o JasonWoof 09:29:13 lo, herk 09:29:37 I just had a serious chuckle to offset two days of bullshit ;-) 09:34:55 hi PoppaVic 09:35:39 I spent two goddamned dubbing shit that was not at fault *sigh* 09:35:49 deBugging, too 09:37:13 then, I got the #asm boys interested - by asking questions - and then got dumped the moment I pointed out that their stupid assemblers were non-portable and so was the syntax/semantics 09:39:32 As expected, not one person admits to "seeing a problem", let alone why an assembler PROGRAM should be portable, and rely on datafiles for syntax and output. 09:40:00 I find it all amusing, after two days of skull-smashing on cinderblock 09:40:47 --- join: virl (~hmpf@chello062178085149.1.12.vie.surfer.at) joined #forth 09:40:48 to be fair, (of course), I have to admit that most can't understand what an API is, let alone an ABI 09:41:35 ..in fact, I have trouble explaining about headers/prototypes to folks that lost. 09:43:14 Then too, they usually can't really differentiate between interpreter, compiler and assembler realy clearly. 09:43:18 "really" 09:43:29 --- quit: Quartus (Remote closed the connection) 09:43:48 Anyway, 2 days of hell and a new day of "my shit works and why are you obtuse?" ;-) 09:44:14 --- join: Quartus (~trailer@ansuz.pair.com) joined #forth 09:59:34 wow, I can really focus on forth 09:59:43 I got bored on hold, and started coding 10:00:08 quite a while later (20 minutes) I notice that I have the headset on, and remember that I was on hold 10:00:18 no reccolection of being disconnected 10:00:26 hehe 10:19:02 --- join: Topaz (~top@spc1-horn1-6-0-cust128.cosh.broadband.ntl.com) joined #forth 10:43:58 --- quit: PoppaVic (Read error: 110 (Connection timed out)) 10:51:42 how much do you use 2^16 bits as a size of variables? 10:52:22 huh? 10:52:56 I think thats the most used data size of a variables, or I'm wrong ;-) 10:53:13 hehe 10:53:19 65536 bits? :P 10:53:37 I thought variables were usually 32 bits 10:53:49 depends on the architecture 10:53:51 no, 2 bytes for each variable. 10:54:02 4 bits, 8 bits, 16 bits, 21 bits, 31 bits, 32 bits... 10:54:16 65536 is a lot of bits 10:54:35 I meant 2 bytes 10:54:47 I'm on a 32 bit machine with loads of ram and disk space, so I use 32 bits for variables 10:56:32 yeah, you do. but I'm a C coder and I expect at least 2 bytes for the datatype int and so I don't use more than it's value range(0-65535) 10:58:50 I see 10:58:57 I assume int is 32 10:59:33 if there's any doubt I use int32_t or whatever from 11:00:56 why I'm asking this? because I'm working on a vm which is very simple, basically it's a forth system. and I need a default datasize(1 byte, 2 bytes, 4 bytes) for it's cell size, I wan't something which can be used on a 8bit,16bit,32bit or 64bit+ cpu, so what is the best tradeoff? 11:01:26 heh 11:01:41 I think you need to be able to hold a memory address in a cell 11:02:09 I had ideas about a sliding cell, but that would be too slow. 11:02:38 if you use more than 64K of memory, you should really have 32bit cell 11:02:52 if you're running on a 16-bit cpu, you should use 16-bit cells 11:03:06 and I don't know what to do with 8 bit 11:05:01 creating something which isn't bend to hardware is hard. 11:52:03 --- quit: I440r (Read error: 104 (Connection reset by peer)) 11:52:39 --- join: I440r (I440r@rrcs-24-242-160-169.sw.biz.rr.com) joined #forth 12:20:22 --- quit: warpzero (Read error: 104 (Connection reset by peer)) 12:23:03 --- join: warpzero (~warpzero@66.109.132.242) joined #forth 12:25:47 --- quit: warpzero (Excess Flood) 12:27:10 --- quit: ianp (Remote closed the connection) 12:27:48 --- join: warpzero (~warpzero@wza.us) joined #forth 12:31:15 anybody ever watched office space? 12:40:13 Yes. 12:40:37 anybody agree it kicks ass? :) 12:40:43 "I believe you have my stapler?" 12:41:02 Got a few laughs out of it. 12:42:11 ) 12:42:13 :) 13:10:20 --- quit: JasonWoof (kornbluth.freenode.net irc.freenode.net) 13:12:00 --- join: JasonWoof (~jason@Herkamire.student.supporter.pdpc) joined #forth 13:12:00 --- mode: irc.freenode.net set +o JasonWoof 13:36:51 --- join: jdrake (jdrake@CPE0080c6ead6a9-CM0012254195d6.cpe.net.cable.rogers.com) joined #forth 13:48:25 --- join: tathi (~josh@tathi.bronze.supporter.pdpc) joined #forth 14:30:41 --- quit: tathi ("leaving") 15:13:51 Office Space is one of my favorites 15:15:51 my favorite part is his interview with the bobs 15:47:03 Is retro forth or isforth recursive (tail call optimizing) 15:55:55 I think retroforth is, but not isforth 15:56:05 I440r doesn't like recursion 16:12:14 --- quit: Topaz ("Leaving") 16:23:57 i was reading an article (interview) regarding colour forth and it indicated that recursion was the only form of looping in it, is that correct? 16:27:56 yup 16:28:01 :) 16:28:24 and truthfully, what else do you need? :) 16:28:34 for/next is nice but thats about it imho 16:30:51 considering that you can get away with it in functional languages... :p 16:34:02 --- quit: arke ("Verlassend") 16:34:37 yeah, in herkforth I have recursion and for/next 16:35:06 I appreciate the simplicity of being able to say "do this 8 times" 16:46:20 --- join: tathi (~josh@tathi.bronze.supporter.pdpc) joined #forth 16:59:38 argh recursion is horrible 17:00:15 im liking colorforth less and less the more i hear about it :P 17:01:07 this means that you cant do a look in the middle of a definition 17:01:26 : blah ..... start-loop ......... ene-loop .... ; 17:01:39 you cant recurse into the middle of the definition 17:04:30 isn't the theory there that you should be able to simplify the word even more? 17:04:54 why can't you recurse into the middle? 17:05:01 just put a red word there so you can branch back to it? 17:05:14 thats not recursion 17:05:17 err...that last wasn't a question. 17:05:25 well, whatever. recurse back to it. 17:05:37 colorforth does tail-call elimination IIRC. 17:07:24 and you could certainly add loops to colorforth easily enough 17:08:59 wtf does "confusion in formal parameters 17:09:02 mean in gas 17:09:09 thats sooooo fucking descriptive!!!!!!!!!!!! 17:09:26 yup. what a great program! :P 17:11:06 ok, you want to hear what I think about it? 17:12:16 oh, never mind, I don't actually know what that means. 17:12:35 :) 17:12:56 your using gas for the PPC version of isforth 17:12:59 I thought it meant you had a macro call where you tried to mix just listing the parameters in order 17:13:03 with naming some of them. 17:13:17 yeah, well, I don't stretch gas very far, so I don't get screwy errors much. 17:13:29 but it looks like it has a different error message for that. 17:13:59 how do you get gas to assemble the link back to the previous word 17:14:12 in a very kludgy manner 17:14:14 im having to pass the label of teh previous word as a parameter to the header macro 17:14:15 :) 17:14:20 is that what you did ? 17:14:31 code "0=", zequals, not 17:14:38 its saying confusion in formal parameters on that 17:14:50 ive tried renaming "not" to "_not" 17:15:11 not is the previous word 17:15:15 aha. 17:15:27 looks like it means it thinks that you're trying to pass a named argument to a macro. 17:15:32 but something isn't right. 17:15:47 what do you mean by a named arg 17:16:02 ok, when you define a macro in gas, you have to name the parameters. 17:16:10 right? 17:16:18 code "not", not, xor 17:16:24 i dont gbet that same error on that definition 17:16:32 or any of th4e 50 or so previous definitions 17:16:37 yeah, it's the 0= string. 17:16:45 its a fucking string! 17:16:48 the macro parser is terrible. 17:16:57 what the fuck is it doing interpreting a fucking string 17:16:58 reads like it was written by a 5 year old 17:16:58 ok 17:17:18 is this in your ARM version? 17:17:21 yes 17:17:31 how do i pass "0=" then 17:17:32 you have it in your svn somewhere? 17:17:37 no 17:17:45 im not going to version this none 17:18:01 soon as this is finished i have a forth arm assembler that ill use to make IT metacompile itself 17:18:07 and that version will be versioned 17:18:13 It's good to version your versions. 17:18:25 .macro header nam, lab, lnk 17:18:25 .data 17:18:25 .word h_\lnk @ link back to previous header 17:18:25 h_\lab: 17:18:25 length \nam @ compute lfa length 17:18:25 .byte len | imm @ compile length byte with smudge bit 17:18:27 .ascii "\nam" 17:18:29 imm = 0 @ reset immediate flag 17:18:31 .word \lab 17:18:33 .text 17:18:35 .endm 17:18:37 heh i use subverion... its tood to subversion your versions :) 17:18:54 yah, you should use it like an undo thingy. 17:19:04 ? 17:19:28 keep everything in version control even if it's just private. 17:19:45 then you can happily delete stuff, and still be able to get it back if you decide you wanted it after all. 17:19:50 im gona version control this. once i start making it metacompile itself 17:20:09 right now all i care about is "0=" 17:20:10 lol 17:20:12 how do i pass that 17:20:13 I'm just saying I'd have it in version control now. 17:20:18 but...I bet it's the call to length. 17:20:26 it thinks you're trying to pass it a parameter by name. 17:20:30 oh i gotta quote it! 17:20:33 argh ok i know the fix 17:20:37 yah, probably. 17:20:41 why didnt it happen on any other call ? 17:20:51 becuse other calls didnt start with a digit 17:20:51 do you have any other word that is "blah=" ? 17:20:52 So the macro processing is still broken, eh? 17:20:53 duh 17:21:02 What a shame there isn't some ALTERNATIVE. :) 17:21:11 yeah, I keep meaning to write one :) 17:21:14 no the macro to calculate string length has to have one line added 17:21:19 and i need to qoute the string in the call to the macro 17:21:27 (keep getting sidetracked by more interesting stuff though) 17:21:34 I440r: can I see the old length macro? 17:21:37 All I'm hearing is that you can't make it work. 17:21:41 :) 17:22:08 Quartus: yeah, it has a completely separate parser for macro arguments. 17:22:23 so it doesn't always work the same way as everything else 17:22:28 I've been trying to convince him to use a real macro processor. 17:22:28 and sometimes it's just horribly broken. 17:22:29 Like m4. 17:22:34 lol 17:23:03 nope this didnt fix it 17:23:17 hmm...I never liked m4. 17:23:24 Funny, it speaks well of you. 17:23:55 maybe I didn't try hard enough, but it seemed tricky. 17:23:59 But it works. 17:24:13 yeah. 17:24:22 Works=good. 17:24:50 no i disagree (im not saying m4 is bad) 17:25:00 but just because something works doesnt make it good 17:25:03 gas works 17:25:08 gas is definatly NOT GOOD 17:25:12 I can just never figure out how many levels of quoting to use. 17:25:20 It always comes down to just trying things until it works. 17:26:13 I440r: paste the old length macro for me? 17:26:40 .macro length nam 17:26:40 len = 0 @ init length 17:26:40 .irpc c, "\nam" @ for each char of name 17:26:40 len = len + 1 @ increment l 17:26:40 .endr 17:26:41 @ len = len - 2 17:26:43 .endm 17:26:46 just unquote the \nam part 17:27:09 and you quoted it in the call, and it still didn't work? 17:27:10 the commentd out line is to not count teh quotes but it doesnt anyway it seems 17:27:14 yup 17:27:22 oh fuck 17:27:27 header is a sub macro 17:27:32 called by the code and colon macros 17:27:38 i bet THEY dont quote it 17:28:11 yup 17:28:13 that was it 17:28:29 good. 17:28:48 have you had problems with ; in strings? 17:29:01 fucking stupid macro processor stripping off the quotes 17:29:08 yup. :) 17:29:08 if i do ill just backslash them 17:29:20 just curious. 17:29:32 im a bit worried about "abort\"" 17:29:40 does the macro processor also strip off teh backslash ? 17:29:52 I don't remember. 17:29:57 I don't think so. 17:30:02 ok 17:30:04 hope not 17:30:05 it worked ok in isforth ppc 17:30:09 ok 17:30:18 but you gotta use .ascii for backslashes. 17:30:28 .byte doesn't work. 17:30:30 i used .ascii 17:30:36 i lucked out lol 17:30:40 :) 17:32:01 --- nick: nanstm -> Raystm2oh 17:34:46 --- nick: Raystm2oh -> Raystm2 18:04:00 --- quit: Quartus (Remote closed the connection) 18:18:53 lol ok the macro processor does not strip teh escape char from strings 18:19:05 so the length macro counts the \ as part of the string lol 18:19:10 i have to make it not do so :P 18:19:18 which is easy 18:19:21 i think 18:21:28 .ifne c,'\' 18:21:33 len = len + 1 18:21:33 ? 18:21:50 yup 18:21:59 thats what i was thunkin :) 18:22:47 hrm...looks like it only takes one expression 18:23:05 .if c != '\\' ; or something 18:23:26 err <> even 18:23:57 --- join: Quartus (~trailer@ansuz.pair.com) joined #forth 18:24:54 --- quit: madgarden (Read error: 104 (Connection reset by peer)) 18:26:44 --- quit: tathi ("laters, all.") 18:27:19 ok thats actually wrong too but it wont cause any problems 18:27:25 because \ isnt defined in teh kernel :) 18:27:31 lol 18:28:48 .ifc c, '\' 18:28:50 i think 18:30:12 erm ifnc i mean 18:32:32 nope 18:32:43 cant fucking evaluate the fucking c variable 18:32:44 fuck 18:32:55 you CANOOT test if c is equal to something 18:33:00 this is so fucking fucked up\ 18:33:02 FUCK 18:33:03 FUCK 18:33:03 FUCK 18:35:52 how the FUCK do i do this 18:37:23 Dude. 18:37:36 fucking gas is fucking with me again 18:37:39 its always fucking with me 18:37:49 the people who wrote gas should be fucking castrateed 18:38:50 you cant equate a fucking value of a variable c in a macro 18:39:02 you cannot fucing say "if c is this... do this" 18:39:09 becayse you testing if "c" is this 18:39:10 It's a cheezy little assembler macro language. 18:39:10 fuck 18:39:18 its not 18:39:19 its not 18:39:21 erm 18:39:24 its not a fucking assembler 18:39:25 at all 18:39:36 its a "fuck with mark manning" 18:39:38 Well, it assembles. So I'd have to disagree with you there. 18:39:39 thats all it fucking is 18:40:37 this is sooooo FUYCKING RETARDED 18:40:40 this is sooooo FUYCKING RETARDED 18:40:40 this is sooooo FUYCKING RETARDED 18:40:40 this is sooooo FUYCKING RETARDED 18:40:40 this is sooooo FUYCKING RETARDED 18:40:40 this is sooooo FUYCKING RETARDED 18:40:40 this is sooooo FUYCKING RETARDED 18:40:42 this is sooooo FUYCKING RETARDED 18:40:44 this is sooooo FUYCKING RETARDED 18:40:46 this is sooooo FUYCKING RETARDED 18:40:48 this is sooooo FUYCKING RETARDED 18:40:50 this is sooooo FUYCKING RETARDED 18:40:52 this is sooooo FUYCKING RETARDED 18:40:54 this is sooooo FUYCKING RETARDED 18:40:56 this is sooooo FUYCKING RETARDED 18:41:00 fuck 18:41:11 You are probably in the wrong line of work, guy. 18:41:16 the only fucking way im going to F U C K I N G do this 18:41:21 is to pass the fucking string length by had 18:41:22 fuck 18:41:30 --- mode: ChanServ set +o crc 18:56:03 --- join: madgarden (~madgarden@London-HSE-ppp3546403.sympatico.ca) joined #forth 19:17:36 --- quit: virl (Remote closed the connection) 19:19:37 --- join: sproingie (foobar@64-121-15-14.c3-0.sfrn-ubr8.sfrn.ca.cable.rcn.com) joined #forth 19:27:51 --- join: snoopy_16 (snoopy_161@dsl-084-058-128-010.arcor-ip.net) joined #forth 19:35:29 --- quit: Snoopy42 (Read error: 145 (Connection timed out)) 19:35:46 --- nick: snoopy_16 -> Snoopy42 19:39:38 --- nick: Raystm2 -> nanstm 19:41:26 --- quit: jdrake () 20:28:10 I think there are some logs that I have that are not up 20:28:10 --- quit: madgarden (Read error: 104 (Connection reset by peer)) 20:28:37 if herklog was here I have them 20:33:00 --- join: Sonarman (~cleetus@adsl-64-169-93-75.dsl.snfc21.pacbell.net) joined #forth 20:42:19 --- join: OrngeTide (~orange@rm-f.net) joined #forth 23:21:21 --- quit: sproingie ("Konversation terminated!") 23:59:59 --- log: ended forth/05.08.03