2023-11-10 06:25:58 <olle        > How would I add configuration on the behaviour of a word? In OOP you'd do obj->setSettingX(y) etc
2023-11-10 06:26:40 <olle        > Are there records in Forth?
2023-11-10 06:26:57 <olle        > https://www.complang.tuwien.ac.at/forth/gforth/Docs-html/Arrays-and-Records-Tutorial.html hm
2023-11-10 06:27:09 <GeDaMo      > Not in the standard but there are various implementations
2023-11-10 06:27:43 <olle        > k
2023-11-10 09:03:19 <olle        > So anyway, a forth bot in this channel perhaps?
2023-11-10 09:05:34 <olle        > I have a server on vpsnet I don't use much
2023-11-10 09:05:49 <olle        > I trust you guys to execute random code
2023-11-10 09:13:18 <MrMobius    > olle: I have been working on a forthbot this past week :)
2023-11-10 09:13:28 <olle        > MrMobius: Hooray and huzzah!
2023-11-10 09:13:50 <MrMobius    > dunno to ask in this channel for permission to run it here
2023-11-10 09:17:44 <crc         > I'll allow a forth bot
2023-11-10 09:19:39 <crc         > nonlinear: your connection issues are becoming a problem.
2023-11-10 09:22:57 <olle        > crc: What's the procedure?
2023-11-10 09:23:01 <olle        > To add a bot
2023-11-10 09:23:36 <MrMobius    > crc, thanks. Ill show you when I have it finished
2023-11-10 09:23:49 <crc         > just let me know the nick and have it join the channel
2023-11-10 09:24:21 <olle        > Aha
2023-11-10 13:22:21 <olle        > Aaah to have a tutorial for >in
2023-11-10 13:22:32 <olle        > I do have the code example
2023-11-10 13:24:09 <GeDaMo      > >in is a variable containing an offset into the input buffer
2023-11-10 13:27:14 <olle        > GeDaMo: A reference doc <> tutorial ;)
2023-11-10 13:27:22 <olle        > I'll play around
2023-11-10 13:29:46 <GeDaMo      > What are you trying to do with >in ?
2023-11-10 13:33:00 <KipIngram   > Some quite fun games can be played with >in.  ;-)
2023-11-10 13:33:12 <KipIngram   > Do it right and you can loop in the interpreter.
2023-11-10 13:33:45 <olle        > GeDaMo: Just understand it
2023-11-10 13:33:57 <olle        > Have to leave soon tho
2023-11-10 13:35:24 <GeDaMo      > In the code I wrote for you, I fetch >in to the stack  and later restore it so I can parse the name twice without having to copy it somewhere else first
2023-11-10 13:35:25 <olle        > Why is >in @ === 1?
2023-11-10 13:35:48 <olle        > Hm
2023-11-10 13:36:22 <GeDaMo      > It's an offset to some base value, maybe there's a space at the beginning?
2023-11-10 13:36:42 <olle        > No idea :)
2023-11-10 13:36:53 <olle        > Just using gforth prompt
2023-11-10 13:38:10 <GeDaMo      > If I do >in @ . I get 6
2023-11-10 13:46:34 <KipIngram   > At the time the @ executes, you have already parsed >in @_ where _ represents the space following @.
2023-11-10 13:46:39 <KipIngram   > That's 6 characters.
2023-11-10 13:46:44 <KipIngram   > Exactly what I'd expect.
2023-11-10 13:47:23 <KipIngram   > olle, did you do the @ alone on a line?
2023-11-10 13:47:30 <KipIngram   > Because that would make 1 make sense.
2023-11-10 13:52:26 <KipIngram   > At any rate, it's where the @ is on the line that should govern the value of >in that actually gets fetched.
2023-11-10 14:33:30 <gorenbk     > i don't get it... what are actual modern forth compilers?
2023-11-10 15:27:49 <KipIngram   > Can you be more specific?  What aspect of it are confusing you?
2023-11-10 15:35:23 <KipIngram   > s/aspect/aspects/
2023-11-10 16:17:05 <gordonjcp   > they left
2023-11-10 16:17:10 <gordonjcp   > I guess it was too confusing
2023-11-10 16:19:25 <thrig       > forth is the "Wizard's Bane"
2023-11-10 16:49:21 <veltas      > The join messages are mad today
2023-11-10 18:20:41 <KipIngram   > I jimmied my config years ago to suppress those.
2023-11-10 18:21:01 <KipIngram   > I still see some of them - I saw gorenbk's join but not his departure.
2023-11-10 18:21:40 <KipIngram   > I'm getting miffed now - my copy of The Olympian Affair was supposed to come today, just in time for weekend reading, but it hasn't shown up yet.
2023-11-10 18:21:46 <KipIngram   > Grrrr...
2023-11-10 18:24:55 <KipIngram   > At any rate, I had no idea what gorenbk was trying to ask.
2023-11-10 19:00:39 <KipIngram   > Happy Saturday UTC folk.
2023-11-10 20:36:51 <KipIngram   > Amazon says they can get me a copy of The Olympian Affair by tomorrow.  That's on the way - B&N can just have their happy little copy back.
2023-11-10 20:38:04 <KipIngram   > It might not have annoyed me as much if B&N hadn't sent me about five emails throughout the week tooting the horn about my Friday delivery.
2023-11-10 20:44:21 <thrig       > the spam system is probably not hooked up to the delivery system
2023-11-10 21:07:24 <KipIngram   > Well, what really peeves me off is that the sent it via a shipping method that didn't just fall back to Saturday when a Friday delivery failed.  I'd mostly made up my mind before I checked it that it wasn't coming today, but I figured I could make it to tomorrow.
2023-11-10 21:07:35 <KipIngram   > Then it was a slap in the face to see Monday.
2023-11-10 21:14:37 <KipIngram   > I blame UPS too.  The book is here in town - tracking info says so.  It's been here in town all day.  Once UPS failed to get it onto a truck for today - the day they'd promised the sender and been paid to achieve - then they should absorb extra cost of ensuring a next day delivery.  When it's this close to the destination, at least.
2023-11-10 21:48:53 <KipIngram   > You know, this metacompile doc that got linked a day or two ago is interesting, but I'm here reading it and can't quite shake the feeling that if a system isn't interactive then I hardly feel like calling it Forth anymore.
2023-11-10 21:49:22 <KipIngram   > I know that's not any sort of "official" way of deciding whether a system is Forth or not, but I just think of the interactivity as an extremely critical part of what Forth "is."
2023-11-10 21:49:37 <KipIngram   > You're really giving up a lot if you give that up.