From: C R Onjob Date: Sat, 20 Sep 2014 17:00:01 +0000 (+0800) Subject: Automatic commit of irc logs X-Git-Url: https://git.ucc.asn.au/?a=commitdiff_plain;h=22889d11998f2d71c836a78942546882265f4afb;p=ipdf%2Fdocuments.git Automatic commit of irc logs Don't get stuck in a closet -- wear yourself out. --- diff --git a/irc/#ipdf.log b/irc/#ipdf.log index 6ee4bdd..96b59b7 100644 --- a/irc/#ipdf.log +++ b/irc/#ipdf.log @@ -5036,3 +5036,21 @@ 19:23 <@matches> Sanity-Check-this - out 19:24 <@matches> I think I need more sleep 19:53 < Pommers> goto bed matches +--- Day changed Sat Sep 20 2014 +21:22 <@matches> Overloading operator new and delete is kind of terrifying... +21:25 <@matches> Things run blindingly fast +21:25 <@matches> Until they segfault +21:26 <@matches> I suspect std::vector does not take kindly to being destructed multiple times +21:33 <@matches> Hmm +21:33 <@matches> I need to make std::vector pointers instead? +21:33 <@matches> That's getting a little convoluted... +21:35 <@matches> Or what I really need is a delete operator that doesn't actually call the destructor automagically +21:35 <@matches> (Even when you overload delete it still calls the destructor?) +21:36 <@matches> I'm noticing a bit of a trend here +21:36 <@matches> You can overload C++ operators but if you do it totally breaks everything +21:36 <@matches> eg: You could implement a double() operator for casting to double but you're better off just writing Double() and using it everywhere because otherwise the compiler goes insane trying to use your operator in places +21:37 <@matches> You can implement your own delete operator but that won't stop the compiler from doing everything it does with the standard delete... +21:38 <@matches> The only operators you can overload (mostly) are the arithmetic ones +21:39 <@matches> Also the compiler seems to occasionally just use the standard delete anyway which just makes everything TOTALLY INSANE +21:39 <@matches> WHY +21:39 * matches grumbles and prepares to write "Delete" and "New"