2023-04-09 02:13:11 <veltas      > You can't plunge that coffee immediately!
2023-04-09 02:13:18 <veltas      > You have to wait 5 minutes
2023-04-09 20:34:45 <vms14       > veltas: now the bot should be more "stable" xD
2023-04-09 20:35:05 <vms14       > but meh, it's likely to end doing nothing
2023-04-09 20:35:50 <vms14       > I can't do much using this module as it runs it's own loop, but it lets me hook a function that will be called every X seconds so I made a watcher program and send it a line every second
2023-04-09 20:35:51 <thrig       > ... full of sound and fury, signifying nothing
2023-04-09 20:36:17 <vms14       > if the watcher does not receive a line will kill the bot and itself
2023-04-09 20:36:36 <vms14       > so supposedly now if runs into a endless loop it will die
2023-04-09 20:36:38 <KipIngram   > veltas: That's the sense I was talking about - sounds like some interesting bit manipulations and so on.  I used to enjoy trying to do things on my HP41CV using only the stack and no storage registers; this sounds like it has some similar aspects.
2023-04-09 20:36:53 <KipIngram   > Computing the roots of a quadratic in-stack is kind of fun.
2023-04-09 20:37:11 <vms14       > endless loops won't trigger the tick hook, so the line won't be sent and the bot will restart
2023-04-09 20:37:34 <vms14       > but anyways if aat restart it can't establish a connection with the watcher it will fail xd
2023-04-09 20:38:10 <vms14       > I have to reas the irc protocol so I can make the bot from the scratch and run my own loop
2023-04-09 20:38:47 <vms14       > anyways if you want to play with it, just /query ohbot
2023-04-09 20:39:10 <vms14       > whatever you tell it will evaluate that
2023-04-09 20:39:43 <vms14       > it's a bit annoying to see the bot reconnecting every time so I won't put it on groups until I make a better version xd
2023-04-09 20:40:10 <vms14       > but this way people can play with the bot as long as it does not fail
2023-04-09 20:40:24 <vms14       > and it's running on my tablet so if someone screws something I don't care
2023-04-09 20:40:32 <vms14       > :D
2023-04-09 20:40:37 <vms14       > Hi KipIngram btw
2023-04-09 20:42:13 <vms14       > needs documentation anyways
2023-04-09 20:47:52 <KipIngram   > Hi vms14.
2023-04-09 20:53:52 <vms14       > :D
2023-04-09 20:58:36 <vms14       > ohbot: 'oh . cr
2023-04-09 20:58:36 <ohbot       > vms14: oh
2023-04-09 20:58:38 <ohbot       > ..[]
2023-04-09 20:59:42 <vms14       > ohbot: " Hello, world!" .cr
2023-04-09 20:59:42 <ohbot       > vms14: Hello, world!
2023-04-09 20:59:42 <ohbot       > ..[]
2023-04-09 20:59:52 <vms14       > I made a weird hello world
2023-04-09 21:00:59 <vms14       > ohbot: 'a 'z range dup 'uc map 2 list flatten.list [ dup [ #$ . ] # colon ] do.list : ! '! .cr ; : , ', .sp ;
2023-04-09 21:00:59 <ohbot       > vms14: []
2023-04-09 21:01:06 <vms14       > ohbot: H e l l o , W o r l d !
2023-04-09 21:01:07 <ohbot       > vms14: Hello, World!
2023-04-09 21:01:07 <ohbot       > ..[bot bot bot bot bot bot bot bot]
2023-04-09 21:01:09 <vms14       > xd
2023-04-09 21:01:34 <vms14       > it defines every letter from a to Z to be a word that prints itself
2023-04-09 21:01:44 <vms14       > and two colon words for the comma and !
2023-04-09 21:16:09 <KipIngram   > What if you want to do something other than print with your letters?
2023-04-09 21:17:35 <vms14       > you can remove them or assign them with scope
2023-04-09 21:19:08 <vms14       > scope is a bit weird
2023-04-09 21:19:34 <vms14       > there's two types of scope, a colon word own scope and the current scope
2023-04-09 21:23:23 <vms14       > when a colon word is executed, a new scope is created and this scope becomes the cuurrent scope, also inherits from the previous scope and the word own scope
2023-04-09 21:24:55 <vms14       > ohbot: : oh meh ;  24 :meh  oh
2023-04-09 21:24:55 <ohbot       > vms14: [24]
2023-04-09 21:25:51 <vms14       > ohbot: 24 :meh  : oh 1 :meh ah ;   : ah meh ;
2023-04-09 21:25:51 <ohbot       > vms14: []
2023-04-09 21:25:57 <vms14       > ohbot: ah
2023-04-09 21:25:58 <ohbot       > vms14: []
2023-04-09 21:26:14 <vms14       > ohbot: oh
2023-04-09 21:26:14 <ohbot       > vms14: [1]
2023-04-09 21:26:35 <vms14       > well this does not explain it well :/
2023-04-09 21:26:41 <vms14       > I need to document it properly
2023-04-09 21:27:04 <vms14       > but it's likely I'll have to rewrite it soon again
2023-04-09 21:28:08 <vms14       > ohbot: 'ah word.environment 'oh... .meh!  ah
2023-04-09 21:28:08 <ohbot       > vms14: ['oh...']
2023-04-09 21:28:19 <vms14       > ohbot: 'ah word.environment
2023-04-09 21:28:19 <ohbot       > vms14: [{meh:'oh...'}]
2023-04-09 21:28:28 <vms14       > ohbot: environment
2023-04-09 21:28:29 <ohbot       > vms14: [{channel:'##forth' who:'vms14' watcher:IO::Socket::INET body:'environ
2023-04-09 21:28:52 <vms14       > and also the packages
2023-04-09 21:29:12 <vms14       > ohbot: package
2023-04-09 21:29:13 <ohbot       > vms14: []
2023-04-09 21:29:29 <vms14       > ohbot: 'main package current.package
2023-04-09 21:29:29 <ohbot       > vms14: []