#pentagram@irc.freenode.net logs for 16 Apr 2008 (GMT)

Archive Today Yesterday Tomorrow
Pentagram homepage


[00:03:32] --> Colourless has joined #Pentagram
[00:03:32] --- ChanServ gives channel operator status to Colourless
[00:34:59] --> Kirben has joined #pentagram
[00:34:59] --- ChanServ gives channel operator status to Kirben
[00:39:43] <-- watt has left IRC ()
[02:10:51] --> watt has joined #pentagram
[02:10:51] --- ChanServ gives channel operator status to watt
[02:59:13] <-- watt has left IRC ()
[04:47:12] --> watt has joined #pentagram
[04:47:12] --- ChanServ gives channel operator status to watt
[06:26:10] <-- Colourless has left IRC (Read error: 113 (No route to host))
[06:41:33] --> Colourless has joined #Pentagram
[06:41:33] --- ChanServ gives channel operator status to Colourless
[12:54:52] --> servus_ has joined #pentagram
[13:06:14] <-- Colourless has left IRC ("casts improved invisibility")
[13:09:20] <-- servus has left IRC (Read error: 110 (Connection timed out))
[13:12:44] <-- watt has left IRC ()
[13:39:16] --> watt has joined #pentagram
[13:39:16] --- ChanServ gives channel operator status to watt
[14:36:15] <watt> OT: anyone know of good command line code formatters?
[14:38:07] <watt> I've always encountered code formatters that a based in the editor, but its occurred to me that's less than ideal if your dealing in a development environment where everybody is using different editors
[14:47:20] <Mrrrrz0r> http://astyle.sourceforge.net/
[14:47:35] <watt> I've never played around with good old indent enough - might need to
[14:48:40] <Mrrrrz0r> I used astyle for a while... worked pretty well for what I needed, was the first thing that psearch suggested
[14:49:17] <watt> Hmmm... ok - I'll look into that
[14:49:20] <watt> thanks!
[14:52:07] <watt> Wikipedia has a good amount of links on this - http://en.wikipedia.org/wiki/Prettyprint
[15:15:28] <-- Kirben has left IRC (Read error: 110 (Connection timed out))
[18:14:23] --> Fingolfin has joined #pentagram
[18:14:23] --- ChanServ gives channel operator status to Fingolfin
[20:08:43] <watt> A co-worker and I were talking a bit more about code formatters and thought it might be cool to have a tool that used a CSS-like file structure to understand its formatting rules (sense everyone has there own insane set of ideas of how to format)
[20:09:57] <watt> Something like that might be able to be built using clang - could be a neat new hobby project for me :-)
[20:27:28] <-- Fingolfin has left IRC (No route to host)
[20:28:57] --> Fingolfin has joined #pentagram
[20:28:57] --- ChanServ gives channel operator status to Fingolfin
[20:32:52] <Mrrrrz0r> hah, watt - I was thinking the same thing when you asked earlier
[20:33:28] <Mrrrrz0r> I've seen the same functionality in some industry app... but I cant remember where I saw it, found a few of the perl formatters have a similar system tho
[20:46:49] <watt> Perhaps something crazy like this:
[20:46:51] <watt> for {brackets: attach}
[20:46:51] <watt> for .paren {padding: 1s 0s 0s 1s}
[20:46:51] <watt> for .paren .oper {padding: 1s 0s 0s 1s}
[20:46:51] <watt> for .paren .semicolon {padding: 0s 0s 0s 1s}
[20:46:52] <watt> for {brackets: attach}
[20:46:52] <watt> if {brackets: break}
[20:46:53] <watt> if .paren {padding: 1s 1s 1s 0}
[20:46:55] <watt> if .paren .oper {padding: 1s 0 0 1s}
[20:47:49] <watt> Changing rules per keyword and possibly per keyword inside other keywords.
[20:48:15] <watt> This might be a bit too crazy / unneeded :-)
[20:52:02] <watt> oh... I'd assume the example would to the following two lines
[20:52:35] <watt> for (i = 0; i < c; ++i) {
[20:53:10] <watt> if ( i == 1 )\n{
[21:01:36] <-- Fingolfin has left IRC ()
[22:03:10] <-- watt has left IRC ()
[22:10:11] --> watt has joined #pentagram
[22:10:12] --- ChanServ gives channel operator status to watt
[23:43:46] --> Colourless has joined #Pentagram
[23:43:52] --- ChanServ gives channel operator status to Colourless
[23:56:21] --> pupnik_ has joined #pentagram
[23:58:28] <-- pupnik has left IRC (Read error: 104 (Connection reset by peer))