Changes between Version 3 and Version 4 of ParrotQuotes

Timestamp:

02/18/09 17:59:53 (13 years ago)

Author:

Infinoid

Comment:

Reformat things to look (hopefully) a little nicer.

ParrotQuotes

@@ -99 +99 @@
 }}}
 {{{
-japhb> OK, popping that discussion off the stack ... we clearly support gcc 3.4.  How much older than that do we still support?
-rurban> 3.3 ?
-particle> no
+japhb>       OK, popping that discussion off the stack ...
+             we clearly support gcc 3.4.  How much older than that do we still support?
+rurban>      3.3 ?
+particle>    no
 davidfetter> stack? i thought we used registers here ;)
-particle> and don't even ask about 2.7
-rurban> 2.95 is still quite popular in academia
-chromatic> Academia should freakin' go outside once in a while.
-japhb> chromatic++
-chromatic> HELLO FROM THE 21ST CENTURY PLEASE JOIN US THE WATER IS FINE
+particle>    and don't even ask about 2.7
+rurban>      2.95 is still quite popular in academia
+chromatic>   Academia should freakin' go outside once in a while.
+japhb>       chromatic++
+chromatic>   HELLO FROM THE 21ST CENTURY PLEASE JOIN US THE WATER IS FINE
 }}}
 {{{
-NotFound> "put exit at bottom or die" is valid perl6?
-moritz> it's just a string literal ;)
-NotFound> moritz: don't take it too literay
-NotFound> literaly
-Infinoid> metaphors are very literary.
-particle> i never met a phor i didn't like (or is)
+NotFound>  "put exit at bottom or die" is valid perl6?
+moritz>    it's just a string literal ;)
+NotFound>  moritz: don't take it too literay
+NotFound>  literaly
+Infinoid>  metaphors are very literary.
+particle>  i never met a phor i didn't like (or is)
 chromatic> I never metamodel not obsessed with reflection.
 }}}
 {{{
-alvar> allison: would it be a good idea to build something which relies on threads on the current implementation?
-allison> alvar: you will likely run into some rough spots in the current threading implementation, but a real use for the threads implementation is a great way to shake out the bugs
-allison> alvar: so, I guess it depends on whether you're more of a "mountain bike" or "racing bike" kind of programmer
+alvar>       allison: would it be a good idea to build something which
+             relies on threads on the current implementation?
+allison>     alvar: you will likely run into some rough spots in the
+             current threading implementation, but a real use for the
+             threads implementation is a great way to shake out the bugs
+allison>     alvar: so, I guess it depends on whether you're more of a
+             "mountain bike" or "racing bike" kind of programmer
 Whiteknight> what's the difference?
 Whiteknight> ...besides the number of crashes
-Infinoid> big gnarly wheels and a penchant for running over small woodland creatures
-allison> alvar: "mountain bike" would be enjoying exploring rugged terrain, not minding a few bumps
-particle> the racing bike programmer wears a funny hat, too
-chromatic> If a mountain biker sees a goat, that's wonderful.  If a racing biker sees a goat, something's wrong.
+Infinoid>    big gnarly wheels and a penchant for running over small
+             woodland creatures
+allison>     alvar: "mountain bike" would be enjoying exploring rugged
+             terrain, not minding a few bumps
+particle>    the racing bike programmer wears a funny hat, too
+chromatic>   If a mountain biker sees a goat, that's wonderful.
+             If a racing biker sees a goat, something's wrong.
 }}}