00:00:00 --- log: started forth/06.05.25 00:41:47 --- quit: JasonWoof ("off to bed") 01:11:06 --- join: Ray_work (n=Raystm2@adsl-68-89-124-38.dsl.rcsntx.swbell.net) joined #forth 01:11:06 --- quit: Ray-work (Read error: 104 (Connection reset by peer)) 01:50:26 --- quit: Quartus (Read error: 104 (Connection reset by peer)) 02:29:48 --- join: nighty (n=nighty@maki.rural-networks.com) joined #forth 02:49:07 --- join: snowrichard (n=richard@adsl-69-155-177-154.dsl.lgvwtx.swbell.net) joined #forth 02:49:33 hi 02:51:02 --- quit: snowrichard (Client Quit) 02:59:15 --- join: mikett (n=nobody@80-195-208-58.cable.ubr14.live.blueyonder.co.uk) joined #forth 03:14:55 --- join: snoopy_1711 (i=snoopy_1@dslb-084-058-113-100.pools.arcor-ip.net) joined #forth 03:23:11 --- quit: Snoopy42 (Read error: 145 (Connection timed out)) 03:23:18 --- nick: snoopy_1711 -> Snoopy42 03:40:20 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 03:47:03 --- part: mikett left #forth 04:25:43 --- join: PoppaVic (n=pete@0-1pool72-200.nas24.chicago4.il.us.da.qwest.net) joined #forth 05:07:24 tathi: hey, good mornin' - did you ever see anything interesting or useful in that tarball? 05:22:25 --- quit: warpzero ("leaving") 05:22:29 --- join: warpzero (n=warpzero@wza.us) joined #forth 05:25:17 --- join: thinkinginbinary (n=tom@2001:4830:1207:1:206:5bff:fe17:2087) joined #forth 05:25:20 --- part: thinkinginbinary left #forth 05:52:43 no 05:53:09 OK. Waste of your time then, sorry/ 05:56:06 I'm always interested to see what other folks are doing 05:57:50 Well, it seems moot No good to you, and all the "interested" have gotten "busy". This results in zero feedback. 05:59:36 ah 06:00:14 So, I am writing code in a complete vaccuum, and I knew you were at least marginally interested. 06:00:43 --- join: timlarson_ (n=timlarso@65.116.199.19) joined #forth 06:01:12 oh. I thought you had a use for it. 06:01:24 I do, and keep going that way 06:01:24 I'm more interested to see what you build with it than in how the core is implemented. 06:01:29 ahh 06:02:14 There are a bazillion ways to do some kind of object core, and it really doesn't seem to matter *that* much exactly how you do it. 06:02:27 Well, support or not, I shall continue to flog it along.. However, as I told dasunt yesterday: the lack of feedback/support suggests I won't leave it "opensource" in the end. 06:03:11 tathi: I know, I'm trying to codify the Cish/forthish mess. I think you end up with a tight core and more wordlists. 06:04:27 er...I thought you were trying to replace autotools. Doesn't that sort of require an open source tool? 06:06:23 the engine? the core? No. The replacement? yes. 06:07:20 Hopefully, we'll get some opensource-support going, eventually. *sigh* As a one-man-show, it blows.. BUT, I am adamant that we need that replacement. 06:10:26 Hell, I figure Forth needs a beating more than C, and the whole sh/make mess needs the formers even more. 06:13:43 I just don't see that you're at a point yet where you really need anybody else 06:14:21 Right.. Mostly ideas/feedback - amazingly, there are very few forth-exposed folks out there. 06:14:48 I've had to nearly BEG the interested to at least try Gforth, if not other variants. 06:15:22 And, mind you: I'm all for C, but C has it's own "issues". 06:16:12 do you know what's wrong here? : accessor: ( "name" -- ) create: ] ' cell+ compile ; 06:16:30 hehe 06:16:39 * tathi isn't that familiar with retroforth 06:16:49 when I write: {accessor: car ;} then call car, it crashes. 06:19:09 I don't understand why the ] in accessor: 06:19:32 isn't it already in compile state? 06:20:16 cell+ and compile are also confuzzling 06:20:27 ..no inputs 06:20:53 I want it to compile call into cell+ to each function I create with it. 06:21:20 eh? 06:21:28 WHAT are you doing - not how. 06:21:47 Cheery: did you make this from some other code, or just write it from scratch? 06:21:47 * PoppaVic notes there IS a #retroforth channel, btw 06:22:08 write it from scratch. 06:22:11 like, example: if I would write: accessor: :cdr cell+ ; then I'd call 4 :cdr . it'd give me 12 (cell+ cell+) 06:22:34 ppl on retro aren't answerring. 06:22:59 I wonder if one here knew how that could be done. 06:23:45 hmm.. the retro folks are a like #devtools or ##C++ 06:24:08 call? execute? execute-tables? vtables? 06:24:36 * PoppaVic screams about "too many variants" yet again 06:25:34 Cheery: maybe you want [ instead of ] ? 06:25:40 I don't think ' is an immediate word 06:25:49 PoppaVic, I've lots of functions which starts with: cell+ 06:25:55 it can be, but modern stuff renames it 06:26:12 * tathi goes to look 06:26:29 I'd have thought cell+ was ( n -- a ) 06:26:50 or rather... (a n -- a' ) 06:27:17 I'd replace : xxx cell+ ... ; with :a xxx ... ; 06:28:04 `cell+' a-addr1 - a-addr2 core ``cell-plus'' 06:28:05 `1 cells +' 06:28:17 I was wrong 06:28:24 ..and that was Gforth 06:28:47 cell+ ( n -- n ) 06:28:59 or actually: ( n -- n + 4 ) 06:29:03 that's why I am tired of all the variants 06:31:16 brb - lemme' recycle 06:31:18 --- quit: PoppaVic ("Pulls the pin...") 06:32:03 : accessor: ( "name" -- ) create: ] c: cell+ ; this worsk! 06:32:56 --- join: PoppaVic (n=pete@0-3pool158-112.nas24.chicago4.il.us.da.qwest.net) joined #forth 06:35:23 : accessor: : postpone cell+ ; 06:35:32 ahhh 06:35:44 postpone... I shoulda' realized 06:36:00 and use : hehe 06:36:13 right: it's pcode 06:36:17 yeah, in a standard forth 06:37:07 : accessor: : c: cell+ ; in retro, I guess 06:37:22 is c: like postpone? 06:37:24 ewww 06:37:41 ": c: " 06:37:52 hehe 06:38:27 looks like it 06:38:33 it starts to get interesting if you write something like : : : ." hey there!" ; 06:38:43 three colons :-) 06:38:53 and all with a different meaning 06:39:00 don't need colours for that hah 06:41:20 I don't _need_ color in any event, but too many variants much with too many things - and they all use the same sorta' broken-comments and too few can't be properly searched/x-indexed 06:42:13 /much with/mulch with/ 06:49:27 hmm... I'm seeing another goddamned pattern 06:51:16 "On my hair, the clothes I wear, my savoir faire is patterns; All I see are patterns, the patterns that repeat." :P 06:51:19 tathi: To "iterate" anything, you need a Container-ref, and then you've serial or R/A issues, no? Same as files? 06:51:41 R/A ? 06:51:49 random-Access 06:51:59 indexing-concepts 06:52:09 records 06:52:25 generally one or the other is slow, if that's what you mean 06:52:27 so, serial-records or r/a records. 06:53:21 No, what I am seeing is... an Iterator can deal with one, either or both... a File is as much a "container" as a heap or a stack, queue, list, tree, etc. 06:54:19 oh. sure 06:54:26 HOW they manage to reach some content/element is irrelevant.. Seems to be repeated.. Right down until you HIT the element. 06:55:05 hmm... THis is why I ask for feedback - sometimes I see a pattern or a forest, within the damned trees ;-) 06:56:21 if you'd just write the thing without worrying about it so much, the patterns would fall out naturally, as you needed them 06:56:29 instead of wasting time on things you may very well never need 06:56:36 :) 06:58:38 well, I'm going out for a bike ride before it decides to rain 06:58:46 I tend to design top-><-bottom, and I usually think about "in C" 06:59:00 stay well, it's supposed to get wet, warm and muggy 07:04:15 I think I'll bail as well.. I've several chores to accomplish. 07:04:25 --- quit: PoppaVic ("Stay well, folks") 07:54:46 --- join: JasonWoof (n=jason@c-71-192-33-206.hsd1.ma.comcast.net) joined #forth 07:54:47 --- mode: ChanServ set +o JasonWoof 08:17:14 --- quit: nighty (Read error: 104 (Connection reset by peer)) 08:17:39 --- join: nighty (n=nighty@maki.rural-networks.com) joined #forth 09:38:54 --- quit: nighty (Read error: 104 (Connection reset by peer)) 09:39:12 --- join: nighty (n=nighty@maki.rural-networks.com) joined #forth 10:52:13 --- join: neceve (n=Clau@unaffiliated/neceve) joined #forth 11:23:44 --- nick: Raystm2 -> nanstm 11:43:32 --- join: segher_ (n=segher@dslb-084-056-191-059.pools.arcor-ip.net) joined #forth 11:47:58 --- quit: segher (Read error: 110 (Connection timed out)) 12:57:41 --- quit: Al2O3 (Remote closed the connection) 13:47:41 --- quit: Cheery ("Leaving") 13:48:08 --- quit: timlarson_ ("Leaving") 14:45:15 --- quit: neceve ("Bye people, I'm leaving") 15:39:07 --- quit: crc (Nick collision from services.) 15:39:27 --- join: crc (n=crc@pdpc/supporter/active/crc) joined #forth 15:39:28 --- mode: ChanServ set +o crc 15:42:06 --- join: tcn (n=user@pool-71-127-13-109.spfdma.east.verizon.net) joined #forth 16:03:44 --- quit: tcn (Remote closed the connection) 16:05:27 --- join: tcn (n=user@pool-71-127-13-109.spfdma.east.verizon.net) joined #forth 17:05:02 --- quit: virl (Remote closed the connection) 17:05:13 --- quit: nighty (Read error: 104 (Connection reset by peer)) 17:23:15 --- quit: tathi ("leaving") 17:59:59 --- quit: tcn (Remote closed the connection) 18:46:25 --- join: Quartus (n=trailer@CPE0001023f6e4f-CM013349902843.cpe.net.cable.rogers.com) joined #forth 18:47:05 --- quit: uiuiuiu (Remote closed the connection) 18:47:09 --- join: uiuiuiu (i=ian@dslb-084-056-224-015.pools.arcor-ip.net) joined #forth 19:44:21 --- join: snowrichard (n=richard@adsl-69-155-177-154.dsl.lgvwtx.swbell.net) joined #forth 19:44:47 hi 19:52:04 --- quit: madgarden ("?OUT OF DATA ERROR") 19:53:43 --- quit: snowrichard ("Leaving") 20:00:56 --- join: madgarden (n=madgarde@London-HSE-ppp3545531.sympatico.ca) joined #forth 21:10:12 --- nick: nanstm -> Raystm2 23:59:59 --- log: ended forth/06.05.25