Re: [cowiki-dev] The new coWiki parser
Paul Hanchett <[email protected]> Thu, 22 Sep 2005 19:28:47 -0700
| Newsgroups | gmane.comp.php.cowiki.devel |
|---|---|
| Message-ID | <[email protected]> |
--------------010104040408040502040306 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit John (yt) Hogenmiller wrote: >On 9/22/05, Paul Hanchett <[email protected]> wrote: > > >> Archie and Team-- >> >> I've been meaning to ask a question... If we back out the parser for now, >>what features and bug fixes do we loose? The "Black Magic" that seems to be >>contained in the parser frankly makes me very nervous and tells me that it >>is serious trouble. Perhaps a strategic retreat and some planning sessions >>are what's required instead... >> >> > >A good description of what issues are affected by rolling back the >parser is available here: http://www.cowiki.org/11.html#A6 along with >a version of cowiki with the parser rolled back. > >Also, as a point of note, we're not dealing with "black magic" but >"bad magic"... we should be nothing, if not consistent when referring >to ill defined areas of doubt and uncertainty. In my opinion, the bad >magic bug has been fixed in CVS HEAD since late July of this year. > John-- I really did mean Black Magic in the sense that no one (Daniel included) seems to know how the parser works, or how to modify it (reliably). I wasn't referrring to the data-loss bug. I think /that/ was fixed when Daniel disabled Kai's auto-recover code. Paul --------------010104040408040502040306 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> John (yt) Hogenmiller wrote: <blockquote cite="[email protected]" type="cite"> <pre wrap="">On 9/22/05, Paul Hanchett <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a> wrote: </pre> <blockquote type="cite"> <pre wrap=""> Archie and Team-- I've been meaning to ask a question... If we back out the parser for now, what features and bug fixes do we loose? The "Black Magic" that seems to be contained in the parser frankly makes me very nervous and tells me that it is serious trouble. Perhaps a strategic retreat and some planning sessions are what's required instead... </pre> </blockquote> <pre wrap=""><!----> A good description of what issues are affected by rolling back the parser is available here: <a class="moz-txt-link-freetext" href="http://www.cowiki.org/11.html#A6">http://www.cowiki.org/11.html#A6</a> along with a version of cowiki with the parser rolled back. Also, as a point of note, we're not dealing with "black magic" but "bad magic"... we should be nothing, if not consistent when referring to ill defined areas of doubt and uncertainty. In my opinion, the bad magic bug has been fixed in CVS HEAD since late July of this year. </pre> </blockquote> John--<br> <br> I really did mean Black Magic in the sense that no one (Daniel included) seems to know how the parser works, or how to modify it (reliably). I wasn't referrring to the data-loss bug. I think /that/ was fixed when Daniel disabled Kai's auto-recover code.<br> <br> Paul<br> </body> </html> --------------010104040408040502040306--