#pentagram@irc.freenode.net logs for 25 Feb 2009 (GMT)

Archive Today Yesterday Tomorrow
Pentagram homepage


[00:23:32] --> watt has joined #pentagram
[00:23:32] --- ChanServ gives channel operator status to watt
[00:30:38] --> watt__ has joined #pentagram
[00:44:37] <-- ShadwChsr has left IRC ()
[00:47:44] <-- watt has left IRC (Read error: 110 (Connection timed out))
[02:10:53] --> watt has joined #pentagram
[02:10:53] --- ChanServ gives channel operator status to watt
[02:14:18] --> Fingolfin has joined #pentagram
[02:14:18] --- ChanServ gives channel operator status to Fingolfin
[02:18:42] --> ShadwChsr has joined #pentagram
[02:28:44] <-- watt__ has left IRC (Read error: 110 (Connection timed out))
[02:44:31] <ShadwChsr> Why does Pentagram define it's own dynamic casting mechanism?
[02:44:59] <ShadwChsr> As opposed to the normal stl stuff ;)
[02:49:28] <watt> Correct me if I'm wrong, but stl doesn't supply any way to actually check it an object is of a type.
[02:53:38] <ShadwChsr> Just being braindead, my head is in C# land from work ;)
[02:53:53] <ShadwChsr> but C++ still has dynamic_cast, why the Pentagram version as well?
[02:57:06] <ShadwChsr> This is probably woefully buggy, but something like:
[02:58:30] <ShadwChsr> if (dynamic_cast<Target*>(source))
[03:00:22] <ShadwChsr> Maybe it was to bypass C++ RTTI?
[03:01:25] <watt> hmmm, it occurs to me I've never looked hard enough into types of C++ casts - never enforced much in schooling and haven't worked much in C++ since.... looking at the documentation, I'd might point out the dynamic_cast does seem to require proper RTTI generation by the compiler.
[03:01:45] <watt> Ah... I type slow I see :-)
[03:02:36] <ShadwChsr> Colourless' documentation says "If we use it... we use it.. if we don't, it doesn't matter"
[03:02:37] <ShadwChsr> hehe
[04:56:57] <-- Fingolfin has left IRC ()
[05:58:57] <Colourless> implemented it for some platforms that didn't have RTTI, or where RTTI causes performance penalties
[06:00:56] * ShadwChsr nods
[06:05:45] <ShadwChsr> I can't imagine a C++ compiler without RTTI these days - so I imagine it's just for things like handheld devices?
[06:37:05] <Colourless> exactly
[06:37:15] <Colourless> though even those have RTTI nowdays too
[06:37:30] * ShadwChsr nods
[06:37:57] <ShadwChsr> p_dynamic_cast adds a lot of semantic fluff to Pentagram, which is why I was curious :)
[07:04:40] <-- ShadwChsr has left IRC ()
[07:52:30] --> pupnik_ has joined #pentagram
[08:08:44] <-- pupnik has left IRC (Read error: 110 (Connection timed out))
[11:29:27] <-- Colourless has left IRC ("casts improved invisibility")
[13:36:26] <-- Kirben has left IRC (Read error: 110 (Connection timed out))
[14:02:34] <-- watt has left IRC ()
[14:27:49] --> watt has joined #pentagram
[14:27:49] --- ChanServ gives channel operator status to watt
[16:55:18] <-- Lord_Nightmare has left IRC (Read error: 110 (Connection timed out))
[16:56:07] --> Lord_Nightmare has joined #pentagram
[17:39:55] --> ShadwChsr has joined #pentagram
[21:36:05] --> Colourless has joined #Pentagram
[22:24:10] --> Kirben has joined #pentagram
[22:24:10] --- ChanServ gives channel operator status to Kirben
[22:30:29] <-- ShadwChsr has left IRC ()