00:59:06  * rgrinbergjoined
02:41:50  <SinisterRectus>daurnimator: remember when you helped me with my class constructor? i came up with a new trick to store properties sequentially: http://pastebin.com/Gx8JdQVW
03:29:28  <SinisterRectus>ignore that class.properties = properties. that was for debugging.
03:40:50  * rgrinbergquit (Ping timeout: 260 seconds)
07:48:11  <daurnimator>SinisterRectus: sure. I still don't think creating a class system solves anything :P
07:49:17  <daurnimator>SinisterRectus: in 99% of circumstances you can get away with just: local methods = {}; local mt = {__index=methods}; local function new(...) --[[code here]] return setmetatable({}, mt) end; function methods:foo() end; return { new = new };
07:51:53  * rendarjoined
14:53:45  * rgrinbergjoined
18:50:10  * daurnimatorquit (*.net *.split)
18:57:22  * daurnimatorjoined
19:12:12  * DarkGodjoined
19:41:11  * rendarquit (Ping timeout: 244 seconds)
20:11:29  * rendarjoined
20:49:10  <SinisterRectus>it's nice to have a constructor when you have a lot of class definitions
20:49:26  <SinisterRectus>you can make the same argument about any function
20:49:38  <SinisterRectus>why write a function when you can just copy and paste the code everywhere
22:26:50  * rendarquit (Quit: std::lower_bound + std::less_equal *works* with a vector without duplicates!)