Hello Gabriel and good morning. It is 7:30a.m. here.
I think that one of eLua's aims is to be small in code and memory use,
so mainline avoids adding features that are not necessary in the core.
For your project, you could implement that function in Lua, in an
include file (oops, sorry, a "require" file) and in less code.
In general, when people only know one language and then meet a second
one, they usually try to program in the first language using the
second by #defining the second to look like the first, simply because
the first language forms your way of thinking about computer
programming, and provides your first vocabulary for programming
concepts.
I think the classic example is the original Bourne Shell, which was
written in C #defined to look like ALGOL, complete with IF THEN ELSE
ENDIF macros.
It's good as a personal programming exercise to help you understand
the correspondences between the two languages, but if you write real
programs in your new dialect, you isolate yourself from the community
that already speaks the second language.
Not that I like eLua's libraries - I would have implemented luaposix,
luasockets, luafs and their friends, specifically to unite with the
existing community and to be able to use hundreds of standard
libraries, but at least everyone understands what I mean if I use the
eLua constructs...
Welcome to eLua!
M
--
You received this message because you are subscribed to the Google Groups "Mizar32" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mizar32+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
_______________________________________________
eLua-dev mailing list
eLua...@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/elua-dev