{"ref":"refs/heads/master","push_id":55087370,"commits":[{"sha":"4bfaa14d2360253a5218a9a5c357056bedca9dda","author":{"email":"54234b27fef504da340909df6dcfdd8e7524fa74@gnu.org","name":"Miles Bader"},"url":"https://api.github.com/repos/snogglethorpe/snogray/commits/4bfaa14d2360253a5218a9a5c357056bedca9dda","message":"Makefile.am: tweak the way we pass CFLAGS to Lua Makefile\n\nUse the variable CFLAGS instead of MYCFLAGS, as this lets us just\noverride everything, and pass in all of the compile flags we use\ninstead of just $(EXTRA_COMPILE_FLAGS)."},{"sha":"e651c128912439a79c1802fc7c58272e3aebfd39","author":{"email":"54234b27fef504da340909df6dcfdd8e7524fa74@gnu.org","name":"Miles Bader"},"url":"https://api.github.com/repos/snogglethorpe/snogray/commits/e651c128912439a79c1802fc7c58272e3aebfd39","message":"Makefile.am: fix the way we add $(CXX_EXTRA_REQ_FLAGS)\n\nAppend to AM_CFLAGS and AM_CXXFLAGS instead of CFLAGS and CXXFLAGS.\nThe latter are then purely left for the user to specify on the command\nline (they are always added after default flags)."},{"sha":"53ee4a54e49852308f678218cc12a22f585b6121","author":{"email":"54234b27fef504da340909df6dcfdd8e7524fa74@gnu.org","name":"Miles Bader"},"url":"https://api.github.com/repos/snogglethorpe/snogray/commits/53ee4a54e49852308f678218cc12a22f585b6121","message":"Correctly propagate Lua errors in luajit_exception_wrapper\n\nWhen Lua code calls into C++, the C++ code then recursively calls some\nLua code, and an unhandled error occurs in the inferior Lua code, then\nthe resulting C++ exception raised by the inferior Lua is an opaque\ntype, not a string or subclass of std::exception (which\nluajit_exception_wrapper already handled properly).\n\nHowever in this case the actual Lua error value is still at the top of\nthe Lua stack, so when luajit_exception_wrapper catches an unknown\nexception type, we just leave it in place and invoke lua_error (in the\nsuperior Lua).\n\nOf course if an unknown exception type wasn't actually raised by an\ninferior Lua, this makes the resulting Lua error nonsense, but the\nerror in that case would be pretty useless regardless.  In the\nusual case where it is from an inferior Lua, it's a huge win to\ncorrectly propagate Lua errors."},{"sha":"22403d17f0655d916edde0d168ae50f13971e931","author":{"email":"54234b27fef504da340909df6dcfdd8e7524fa74@gnu.org","name":"Miles Bader"},"url":"https://api.github.com/repos/snogglethorpe/snogray/commits/22403d17f0655d916edde0d168ae50f13971e931","message":"Fix memory leak in Octree::Builder"}],"head":"22403d17f0655d916edde0d168ae50f13971e931","size":4}