Comments on: ANTLR (?) http://third-bit.com/blog/archives/1356.html Data is ones and zeroes | Software is ones and zeroes and hard work. Fri, 03 Feb 2012 17:07:30 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: The Third Bit » Blog Archive » Reviewing Markdown http://third-bit.com/blog/archives/1356.html#comment-1465 The Third Bit » Blog Archive » Reviewing Markdown Tue, 12 Feb 2008 23:57:34 +0000 http://pyre.third-bit.com/blog/archives/1356.html#comment-1465 [...] software engineering class about code reviews last week, while simultaneously thinking about how to replace the wiki parser in DrProject.  Two birds one stone, I decided to review a wiki parser written in Python and keep [...] [...] software engineering class about code reviews last week, while simultaneously thinking about how to replace the wiki parser in DrProject.  Two birds one stone, I decided to review a wiki parser written in Python and keep [...]

]]> By: Greg Wilson http://third-bit.com/blog/archives/1356.html#comment-1464 Greg Wilson Sat, 02 Feb 2008 22:41:16 +0000 http://pyre.third-bit.com/blog/archives/1356.html#comment-1464 Following up on Andrey's suggestion, I'm now looking at http://www.freewisdom.org/projects/python-markdown/ and http://code.google.com/p/python-markdown2/. The first is easier to read (since it's not a direct translation from Perl); the second is faster and a little shorter (but does text-to-text, rather than text-to-DOM-to-text, which I'd prefer). Adopting either would require us to rewrite all our wiki pages, but on the other hand, it'd save us having to document our wiki syntax ourselves... Following up on Andrey’s suggestion, I’m now looking at http://www.freewisdom.org/projects/python-markdown/ and http://code.google.com/p/python-markdown2/. The first is easier to read (since it’s not a direct translation from Perl); the second is faster and a little shorter (but does text-to-text, rather than text-to-DOM-to-text, which I’d prefer). Adopting either would require us to rewrite all our wiki pages, but on the other hand, it’d save us having to document our wiki syntax ourselves…

]]> By: Blake Winton http://third-bit.com/blog/archives/1356.html#comment-1463 Blake Winton Thu, 31 Jan 2008 16:21:14 +0000 http://pyre.third-bit.com/blog/archives/1356.html#comment-1463 Well, I'm not an ANTLR whiz, but I'ld love to learn it. Perhaps a set of blog posts on the topic as you convert the code to Python would be a neat idea. (And if you had any questions, I'ld be happy to find the answers for you. It's only fair, since rewriting the parser will save me time and frustration in the long run. ;) Also, is this a new template for the blog? It seems more... sterile, or something. Well, I’m not an ANTLR whiz, but I’ld love to learn it. Perhaps a set of blog posts on the topic as you convert the code to Python would be a neat idea. (And if you had any questions, I’ld be happy to find the answers for you. It’s only fair, since rewriting the parser will save me time and frustration in the long run. ;)

Also, is this a new template for the blog? It seems more… sterile, or something.

]]> By: Andrey http://third-bit.com/blog/archives/1356.html#comment-1462 Andrey Thu, 31 Jan 2008 14:59:30 +0000 http://pyre.third-bit.com/blog/archives/1356.html#comment-1462 Oooooor parse the page as soon as it's submitted and cache the result? I believe that's how most modern wiki's work. Although it wouldn't hurt Dr. Project to adopt a more modern wiki syntax like markdown or something hip like that. Oooooor parse the page as soon as it’s submitted and cache the result? I believe that’s how most modern wiki’s work.

Although it wouldn’t hurt Dr. Project to adopt a more modern wiki syntax like markdown or something hip like that.

]]>