On Sun, 15 Apr 2012 14:15:15 +0900 Carsten Haitzler (The Rasterman) <ras...@rasterman.com> wrote:
> On Mon, 2 Apr 2012 19:53:28 -0300 Gustavo Sverzut Barbieri > <barbi...@profusion.mobi> said: > i haven't looked beyond a cursory glance thus i have no deep > meaningful insights, but let me make an attempt. :) You are one up on me then, I've not even so much as looked in its direction. > 1. eina value > > * it is heftily documented, so i can't complain. > * it's pretty darned big. > * it seems very heavyweight in a c world for holding and dealing with > "values". it smells like the kind of logic u find in bash or perl or > other scripting langs where variables are dynamically typed - they > may be a string, a number, a float etc. and they keep shifting type > based on how you use them = eg a = b + c ... will store the numeric > result of b + c... as long as both b and c are sanely interpretable > numbers (even if both strings- of both are strings of numbers etc.). > so that's what this looks like to me. find - if u are writing a > scripting engine this can be useful. > * could you please go into what eina_value is useful for? what did > you develop it for? what was the driving reason? It just so happens that I am writing a scripting engine, for an existing language. LSL, Linden Scripting Language, as invented by Linden Research for their Second Life virtual world platform. Mines a clean room implementation based on their documentation for LSL. LSL is statically typed, so that heavy weightedness that raster describes would not be good. I would prefer to not use something heavy. On the other hand, my script engine actually converts the LSL to Lua, which IS a dynamically typed language. My code has to deal with the differences between the languages, and also has to deal with a pre existing system written in C#. On the gripping hand, the converted code is acting like LSL, and the variables don't actually change type. Though I am leaving the door open to mixing LSL and Lua in scripts. I may have to deal with dynamic typing. Naturally, since I don't actually implement running of the scripts, just converting them to Lua and let Lua run them, my needs are a lot simpler. I do need to implement the LSL functions though, so sometimes the Lua has to call back into my C. Referencing back to the original LSL script from what Lua hands to the C would be useful, and I would already have structures around for that purpose. So right now, I'm not exactly sure if eina_value, or something like it, would be a good match for my scripting engine. I do intend to check it out though, when I get a chance to get back to that project. If eina_value ends up being a large increase in size for me, then I'll just not use it. Exactly the same as I did for elementary. My scripting engine already has a hand rolled solution, but it's not generic like eina_value would be. "Large increase in size" is relative off course. In this scripting engine project I'm not being as anal about size as I am in my current embedded project. lol -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world.
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
