Hello all, While I'm all for using appropriate language features to make implementations more readable and efficient, the use of the "yield" keyword in the tokenizer makes me pause a little. Why should we not use yield?
* It complicates porting the Python implementation to other languages. In my opinion, the html5lib implementations are a first step on the way to a uber-fast C implementation and other userspace implementations in other programming languages. Coroutines are mildly difficult to understand; using a more general implementation helps porters! (like me) * It's not necessary. We can remove the yield statement in two ways: replacing the parser's iteration as a callback function, or queuing extra tokens on a round of self.state(). Both are simple changes due to the minimal amounts of state that need to be preserved; heck, there's already a tokenQueue data-structure to push the stream errors to. Of course, you can treat these as the complaints of a fogey on PHP who doesn't get access to such a nice, shiny language feature. I'd be interested in what you all have to say, though. Cheers, Edward --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "html5lib-discuss" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
