01:26:08 <Gretell> Unstable branch on crawl.develz.org updated to: 0.22-a0-580-gd5db89c (34)
01:56:38 <Gretell> Windows builds of master branch on crawl.develz.org updated to: 0.22-a0-580-gd5db89c
02:56:23 <Gretell> Monster database of master branch on crawl.develz.org updated to: 0.22-a0-580-gd5db89c
03:11:45 <Rotatell> Unstable branch on crawl.beRotato.org updated to: 0.22-a0-580-gd5db89c (34)
04:17:54 -!- amalloy is now known as amalloy_
12:19:45 <Leszczynek> hi
12:19:56 <Leszczynek> is there any user manual of crawl's clua and dlua?
12:20:11 <Leszczynek> i.e. if anyone ever documented available functions and so on
12:20:35 <Leszczynek> google's telling me "no", but i might have missed something
12:36:17 <ebering> Leszczynek: google's pretty close to correct
12:36:34 <ebering> Leszczynek: there's at least a partial list of dlua documentation in docs/develop/level/advanced.txt
12:36:37 <ebering> well
12:36:45 <ebering> list of functions mostly
12:37:21 -!- amalloy_ is now known as amalloy
12:37:23 <ebering> The lua bindings available in c/dlua are defined by the various files l-*.cc
12:37:53 <ebering> the lists of functions are in modulename_clib and modulename_dlib for c/dlua
12:38:01 <Leszczynek> i know, i'm looking through these
12:38:12 <Leszczynek> but maybe i don't have to write it down myself if someone's done it before
12:38:58 <ebering> that's the best there is to my knowledge
12:43:15 <ebering> !learn add ebering[3] s|$|, document c/dlua|
12:43:16 <Sequell> ebering[3/4]: s|$|, document c/dlua|
12:43:22 <ebering> oops
13:54:58 <Leszczynek> ebering: i knew i've seen it somewhere, and here it is: https://crawl.develz.org/wiki/doku.php?id=dcss:help:maps:lua:modules:start
13:55:02 <Leszczynek> though very incomplete
15:14:59 <ebering> Leszczynek: thanks!
15:31:31 <gammafunk> I think the best starting point for documentation for those is doxygen comments on the lua functions
15:32:57 <gammafunk> someone could run doxygen on the source and we could probably host the results somewhere
21:24:57 -!- amalloy is now known as amalloy_
21:40:11 -!- amalloy_ is now known as amalloy
22:18:04 <aidanh> doxygen is already used for c++ docs and it'd be strange to mix those and docs for lua APIs, given the different target audience
22:23:26 <aidanh> I have somewhere a list of crawl's lua api functions
22:24:56 <aidanh> that might be as good a place to start writing documentation as any
22:25:26 <aidanh> plain text is better than nothing, and it can be fleshed out into luadoc or whatever later
22:26:02 <aidanh> the main problem is finding people with the time and inclination to write documentation
22:28:47 <chukamok> !tell johnstein Hello, I have a gooncrawl game on cbro that keeps crashing.  Would you delete the save?  Username chukamok.  Thanks.
22:28:47 <Sequell> chukamok: OK, I'll let johnstein know.
22:34:28 <gammafunk> aidanh: why would it be strange?
22:34:59 <gammafunk> It's not even true that there's a different target audience, especially for dlua; I guess you could make the case for that for clua
22:35:37 <aidanh> good point about dlua
22:35:45 <gammafunk> It wouldn't preclude someone writing some other guide, but it seems to me like documenting the code within the code itself is the best way to go, at least
22:36:17 <gammafunk> Maybe there's some other better system for lua documentation, like how python has pydoc
22:36:21 <aidanh> does doxygen have any sort of lua-specific stuff?
22:37:01 <gammafunk> I see a perl module to "make doxygen support lua"
22:37:17 <aidanh> lua has ldoc, which I believe can also extract comments out of c++ files doxygen-style
22:37:28 <gammafunk> nice
22:37:42 <gammafunk> hrm, looks like ldoc uses markdown?
22:38:16 <gammafunk> yeah the example I see is very doxygen-like
22:38:54 <gammafunk> Looking over http://lua-users.org/wiki/DocumentingLuaCode
22:40:20 <gammafunk> I guess one issue with this is that we'd tend to want to put the lua documentation in the l-FOO.cc file itself
22:40:43 <gammafunk> but then it's documentation for lua in a C++ file
22:40:57 <gammafunk> not sure if that's actually a problem, but I imagine ldoc wants to have a lua file as input
22:43:13 <gammafunk> ebering: so after all that bit about mnoleg, I finally actually looked at mnoleg and he doesn't even have chain of chaos, but "call of chaos"
22:43:28 <gammafunk> but the non-self-harming thing was still necessary, so we're fine!
22:48:51 <ebering> it's getting late
22:49:04 <ebering> I somehow thought chaos champions were 1) still in the game and 2) had chain of chaos
22:53:30 <gammafunk> nice, so we both thought different wrong things
22:53:51 <gammafunk> Truly this is the essense of collaboration on crawl code
22:54:17 <gammafunk> ebering: I'll be pushing that PR tonight hopefully, but with some additional changes I've made
22:54:24 <ebering> cool
22:55:06 <aidanh> either one would work I guess
22:55:32 <aidanh> I pasted the function list at https://ptpb.pw/Qxvm
22:55:33 <ebering> too bad you can't !lg * vmsg~~'hasted by the player' ;)
22:56:53 <gammafunk> aidanh: yeah, good first step is just a list like that with a cleaned up list of which lua lib the lua function is in
22:57:16 <gammafunk> that's actually already clear in most cases I think
22:57:35 <gammafunk> but it could be cleaned up to have the actual correct lua function call
22:57:57 <gammafunk> interesting, l_you_monster versus you_god
22:58:19 <gammafunk> guess just different c++ function naming schemes by the implementer
22:58:41 <gammafunk> wasn't even aware that there was a food lua lib
22:59:02 <gammafunk> rip food_isfruit
23:07:58 <aidanh> it'd be good to make that naming consistent too
23:34:30 <gammafunk> yeah, I didn't check but vaguely suspect there may be different macros to make the function name thingies
23:34:48 <gammafunk> and the macros don't necessarilly use the same format