Older blog entries for redi (starting at number 252)

RIP, dmr

I like using boost::function for callbacks, and boost::bind for partial application to allow those callbacks to do fancy things. And when I say I like it, I mean I love it so much I would change my name to std::function Wakely if it wasn't for the little problem of people mis-hearing it as StudFunction Wakely, which would just be silly. Anyway, when I wanted to use them for some cross-language callbacks in Python I was very pleased to find a section on boost.function objects in the Python wiki page about Boost.Python, where the file py_boost_function.hpp written by Alcides Viamontes Esquivel is attached. That little bit of magic sufficiently advanced technology lets me define callbacks which might call a partially-applied C++ function or a python function, or mixtures of both. Those callbacks can do pretty much anything. Power extreme. Thanks, Alcides. Thalcides.

ryuslash, you won't "fill up" the recentlog, you'll help create the conversation that recentlog is supposed to be. People who aren't interested don't have to read it, and if they're repeatedly not interested in what someone has to say they can rate their diary below the threshold they read at.

QOTD: Blog comments are for the weak. -- Zaitcev

He's right, only youtube comments are more unfuriating and inane than your average blog comment.

I never liked the change from calling these "diary entries" to "blogs" anyway.

robogato, wouldn't using libxml2's html-output (e.g. htmlDocDumpMemoryFormat) ensure it outputs <em></em> instead of <em/>?

I'm not sure how that would work with syndicated posts, do they get parsed into an xmlDoc first, then dumped out again?

nutella, no of course you're not the only one - apparently you're not reading Advogato closely enough :) or you'd have seen discussion of the new HTML parser that robogato released, and other cases of truncated/corrupted recentlog.

I usually email the owner of the problem diary entry or email robogato directly. If you read this, robogato, the HTML parser bails out on davidw's newest entry

recentlog seems to stop rendering after the <iframe> in bagder's post, I'm not sure why

badvogato, you say that confusedtrust may have fixed your problem (and I assume that's why you certified them.) If the problem you refer to is the diary entry from sness which broke recentlog, sness fixed that problem because I emailed him and pointed out the problem. confusedtrust is probably a spammer.

You've also certified r7379062259, whose "homepage" is a blog which plagiarises an essay on the history of C, which appears to originate at jakeo.com, He also plagiarises a tutorial on variables in C which possibly originates at cprogramming.com (although that could be plagiarised too). I haven't checked but I'd bet bread that every "blog" is stolen from someone else. That user is almost certainly a spammer, at the least a plagiarist. All spammers must die, be more vigilant!

Everyone else, if you think they're spammers please flag their accounts before badvogato's cerification validates them as real users.

Watch for Spammers, people. Be vigilant. The recentspam problem has been getting worse, I wonder if the spamming tool robogato discovered has been updated to use POST for new accounts.

All spammers must die.

Lots of recentspam today - you know what to do.

I need to learn to stop reading any comments on LWN that mention C++ or I'm going to get facepalm-related RSI.

robogato, unfortunately the diary edit page uses GET, so your changes mean I can't edit diary entries

Edit: editing works again now, like this. Thanks!

It also seems the new parser doesn't recognise <person> or <proj> tags

Edit2: I occasionally still use <proj> tags as a shortcut, but I stopped using <person> tags years ago as I find it more useful to link to a specific diary entry when responding to something in recentlog, so use <a> for a direct link to the diary entry. I think I wrote years ago that a <diary key=33>robogato<diary> would be nice :)