Our standard parlance is that "dlua" is "Dungeon Lua", and "clua" is
"Client Lua", but that brings confusion when one looks in dat: there's
a "lua" folder and a "clua" folder, and it would make sense to assume
that the "clua" folder contains files related to client Lua, and the
other for dungeon or internal.

However, this is not the case! According to INSTALL.txt, "dat/clua" is
"core" Lua.

I'm not sure where the inconsistency has come from, but it's really,
really confusing. I think we need to rename the dat/clua folder into
something that makes more sense. However, renaming clua to dlua and
lua to clua doesn't help, because some of the client-based Lua
includes files in dat/clua.

Perhaps we should split it into:

dat/lua/util
dat/lua/pub
dat/lua/priv

Thus we have "util(ity)" -- shared files, "pub(lic)" -- autofight,
macros, etc, and "priv(ate)" -- markers and such. These could be
sub-divided into a "markers" folder as well if necessary. However,
that introduces another set of parlance: all of our C++ interface
files and library names still use clua/dlua. It wouldn't necessarily
be easy to change all of these to publua and privlua, but I think it
might bring some more clarity to things.

So, options:

* Rename dat/clua to dat/dlua, move common files into dat/common_lua
(say), rename dat/lua to dat/clua. No change to any of the wrapper
files as such. Easiest.
* Rename dat/clua to dat/lua/priv, move common files into
dat/lua/util, rename dat/lua to dat/lua/pub. Change the parlance in
the contained files to "publua" and "privlua" instead of "clua" and
"dlua". This would be harder but remove any current and future
confusion between crawl's "Two Luas".

-J

------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
Crawl-ref-discuss mailing list
Crawl-ref-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/crawl-ref-discuss

Reply via email to