Bot Development

SIFDKGNS

FSR]GSP

https://github.com/pkulchenko/serpent is pretty awesome

In the future, I would do it as described above, probably put it in a real database. I figure in this case, since I only really have one use for it, being able to look up IDs by username is more elegant than looking up usernames by ID, and there's never an urgent need to kick someone who hasn't posted in a while.

Am I not localizing some things?

You should ideally when requiring things do local module = require('module'). Keeps it per file and namespaced

Just make your module a table of functions and values that you return.

E.g. local a = foo; local b = function (potato) do salad end; return {a = a, b = b, c = 'lua'}

I don't localize them because 1) they're all needed by the main script so there's never a time they would not need to exist 2) i don't necessary require what I need in any given file

The assertions in bindings.lua are a recent change to make it more sensible to use that file without otouto.

You should at least local import your deps. They can run over each other

What do you mean by both of those sentences?

Sorry. You have HTTPS = blah at the top of bot.lua. You then say HTTPS = blah again in utilities.lua. Because that file is loaded and ran at the point it's called and HTTPS is global in both places, you now have overwritten the original bot.lua HTTPS variable. This can cause problems with some libraries that keep state throughout a file.

It overwrites what HTTPS points with the same thing that HTTPS already points to. If I remember correctly, require differs from dofile in that require checks if the file has already been loaded, and if it has, uses that.

Maybe I'm not grasping what you mean, though, so correct me, but the way I see it, as long as the module pointed to is the same, this has no potential for harm.

Also require paths. I don't know. I guess it's fine, but might as well save the overwrite and not pollute the global namespace

Would localizing them in bot.lua keep them working when a plugin uses one?

Or would it make you happy if I changed the requirements in utilities.lua to HTTP = HTTP or require('socket.http')? :b

I guess I'm mostly worried about global pollution. Now that I think about it, the require keeps it from being actually overwritten in the dofile. So it's up to you. I think locals are cleaner, and prevent you from feeling pain if somewhere in a plugin you use JSON as a variable name. I imagine you shouting cased them to make them not collide, but locals do that too.

half-assedly following the "SHOUT DEFINITIONS" principle

I haven't worked with lua, are variables in all caps, globals?

no