#pentagram@irc.freenode.net logs for 11 Aug 2007 (GMT)

Archive Today Yesterday Tomorrow
Pentagram homepage


[00:38:08] --> watt has joined #pentagram
[00:38:08] --- ChanServ gives channel operator status to watt
[00:38:08] <-- watt_ has left IRC (Read error: 104 (Connection reset by peer))
[02:45:47] <watt> Kirben: sorry about that :-(
[02:49:25] <SB-X> ?
[02:54:53] --> Colourless has joined #Pentagram
[02:54:53] --- ChanServ gives channel operator status to Colourless
[02:55:16] <watt> I caused a compile error on windows.
[02:55:51] <watt> Didn't add new scope before declaring variable in middle of function
[02:56:09] <Colourless> that should be ok
[02:57:01] <Colourless> only a problem on 'old' version of msvc. latest ones its a compile flag, and it's only relevant to the scope of for statement
[05:00:11] <-- SB-X has left IRC ("BRB")
[05:06:07] --> sb-x has joined #pentagram
[05:38:10] <-- watt has left IRC ()
[06:19:40] <-- sb-x has left IRC ("*casts gate travel*")
[07:26:58] <-- Kazin has left IRC ("fwaffwafwfaa")
[07:29:12] --> Kazin has joined #pentagram
[09:13:55] <wjp> watt: that's not the problem; the issue is declaring variables in a case statement
[09:17:00] <Colourless> oh
[09:17:10] <Colourless> yeah doing that is bad
[09:17:39] <Colourless> not sure if it's even legal to do it. it doesn't make much sense to do it, and obviously it doesn't work doing it in windows
[09:18:37] <Colourless> if you 'need' to do something dubious with variables in case statments then declare the variable before the switch
[09:18:42] <wjp> hi Ryan
[09:19:00] <Colourless> hi
[11:04:09] <-- Colourless has left IRC ("casts improved invisibility")
[15:03:57] --> watt has joined #pentagram
[15:03:57] --- ChanServ gives channel operator status to watt
[15:05:49] <watt> ah... ok... doesn't a newer version of gcc even warn when you do that? Thought I saw that in gcc 4.1
[15:06:40] <watt> using gcc-4.0.1 here
[15:10:07] --> watt_ has joined #pentagram
[15:10:57] <wjp> yes, it should warn you
[15:13:42] <-- Kirben has left IRC (Read error: 110 (Connection timed out))
[15:26:27] <-- watt has left IRC (Read error: 110 (Connection timed out))
[15:26:29] --> watt has joined #pentagram
[15:26:29] --- ChanServ gives channel operator status to watt
[15:35:30] <-- watt_ has left IRC (Read error: 110 (Connection timed out))
[17:11:53] --> Monochrome has joined #pentagram
[17:12:06] <Monochrome> sup guys
[17:17:10] <Monochrome> anyone available?
[17:22:59] <watt> I am briefly
[17:23:37] <Monochrome> wanted to ask sum questions regarding pentagram
[17:24:50] <Monochrome> will the engine be mainly focused in making U8 engine games work once again, or will there be any developer support?
[17:25:54] <watt> main focus is U8, secondary would be the crusader games.
[17:26:54] <Monochrome> yes but that doesnt rly answer my question in totality
[17:27:02] <watt> Additional community games and additions could be considered for support, but I don't think we have any real plans for that yet
[17:27:11] <Monochrome> i was interested in developing a game using pentagram
[17:30:15] <watt> You'd be welcome to try of course
[17:31:16] <watt> However, you may want to consider exult - it does already have some support for new content..
[17:32:53] <Monochrome> nah i was looking foward to make advantage of U8's climbing system
[17:33:16] <watt> Ah.. ok.
[17:37:35] <watt> Well, I've gotta go now... good luck on your endeavors.
[17:37:45] <-- watt has left IRC ()
[21:27:05] --> watt has joined #pentagram
[21:27:05] --- ChanServ gives channel operator status to watt
[21:31:10] --> watt_ has joined #pentagram
[21:31:10] <-- watt has left IRC (Read error: 104 (Connection reset by peer))
[21:36:43] <-- watt_ has left IRC (Read error: 104 (Connection reset by peer))
[21:36:44] --> watt has joined #pentagram
[21:36:44] --- ChanServ gives channel operator status to watt
[22:00:38] <-- watt has left IRC (Read error: 110 (Connection timed out))
[23:27:58] --> Colourless has joined #Pentagram
[23:27:58] --- ChanServ gives channel operator status to Colourless