Good idea. Perhaps for the beginner looking into coding with Lua/LÖVE, ËNVY would be a great place to start if you added a barebones game that showed a few coding conventions and good ideas.Merkoth wrote:The only thing I'd suggest is to also add a "blank" game to the distribution.
__type isn't part of standard Lua.Tad2020 wrote:Is it just me or is LÖVE not calling the metamethod __type? I'm having problems with ËNVY's vector class causing C STACK OVERFLOWS, I traced it down to the type calls returning "table" instead of "vector". I figured something might be wrong with my OOP module (using own, not ËNVY's), but tostring is fine and __type works when called directly.
That's strange, I sworn that I've used it with the standalone Lua bin before, I guess my memory is mistaken. Time to override type() thenKaze wrote:__type isn't part of standard Lua.
Yeah.... I think I put back a isinstanceof() function to my object system instead (or just check for x & y). That was a crazy idea, I stopped overriding things in Lua years ago.osuf oboys wrote:I believe it would be better if you used a custom function for this. Some libraries for optimizations, serialization, copying, and the like may need to know whether your data is stored as a table or not.
Code: Select all
-- This is the worst thing since Garry Glitter.
local rawtype = type;
-- This is the worst thing since Garry Glitter.
type = function(variable)
local metatable = getmetatable(variable);
-- Check if the type is valid.
if (metatable and metatable.__type) then
return metatable.__type(variable);
else
return rawtype(variable);
end;
end;
I think his name is with one "r", Gary Glitter.Kudomiku wrote:Code: Select all
-- This is the worst thing since Garry Glitter.
Code: Select all
-- Called when a vector is added with another variable.
function vector:__add(a)
if type(a) == "number" then
return vector(self.x + a, self.y + a)
elseif a.__vector then
return vector(self.x + a.x, self.y + a.y)
end
end