@cmuratori @Jonathan_Blow You don't need tooling assisting you in doing this; you want tools that assist you in not doing this accidentally!
-
-
Replying to @rygorous
@rygorous@Jonathan_Blow Metaprogramming is good! Just because C++ templates suck doesn't mean you don't want codegen.5 replies 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@Jonathan_Blow All I've said, about 5 times now, is that making backtracking parsers easier to write is actually a net negative.1 reply 0 retweets 0 likes -
Replying to @rygorous
@rygorous@Jonathan_Blow But backtracking for _error recovery_? That does not imply anything about your grammar.2 replies 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@Jonathan_Blow Though I dislike that variant too - makes it easy to introduce bugs where the parser can't make progress.1 reply 0 retweets 0 likes -
Replying to @rygorous
@rygorous@Jonathan_Blow Validation is a separate thing though, right? You can always do LALR validation if you wanted to do that.2 replies 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@Jonathan_Blow Stop saying LALR. In a top-down parser you want LL(k), usually k=1. :)1 reply 0 retweets 0 likes -
Replying to @rygorous
@rygorous@Jonathan_Blow I'm only saying that because Sean said it :) But LL(1) is pretty weak sauce dude...2 replies 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@rygorous@Jonathan_Blow Why settle for that constraint?2 replies 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@Jonathan_Blow 64-bit virtual memory is pretty weak sauce dude! Why settle for that constraint? Let's use bigint addressing!1 reply 0 retweets 0 likes
@rygorous @Jonathan_Blow It's true. We need 256 bits, really :)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.