Tim Fletcher wrote: > Two more (both "mistranslations" from Python to Ruby): > > http://code.google.com/p/html5lib/issues/detail?id=38 > http://code.google.com/p/html5lib/issues/detail?id=39
Tim, mind if I add you as a member (committer) to this project? You certainly have earned it! Note: while there is some obvious benefits to keeping the high level design of the two implementations in sync, I have no interest in drawing attention to language differences. If there are obvious Ruby idioms that can make a given section of code smaller or clearer, then by all means, such idioms should be used. What I am trying to say is that while the bulk of this code *looks* like it was originally written in Python and then hastily ported to Ruby, that situation should be treated as a quirk of history that over time should be corrected, and not as a desirable end in itself. - Sam Ruby P.S. Issue #38 seems like an obvious bug in the Python implementation. The test case appears to be designed to test to make sure that only the first newline is "eaten", but it turns out that the test code (as opposed to the parser itself) eats the other other line, and the test data was "adjusted" to match the net behavior of the Python test, missing the point of the original test in the process. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "html5lib-discuss" group. To post to this group, send email to html5lib-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/html5lib-discuss?hl=en-GB -~----------~----~----~----~------~----~------~--~---
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4