Is it time to plan a move to Go?

[Hal Murray]

> Pretty direct, I'd say.  I wouldn't even have introducing *methods* as an
> initial goal.  My experience is that trying to re-engineer while you
> translate is a dangerous rathole - you can easily end up at a place where
> you've lost track of the semantic mapping between the original code and the
> translation, and are just wandering around thrashing. 

But if you do a direct translation, you end up with code that still has all 
the crappy structure that you started with.  I think the main problem with 
the current code is global variables.

If I was working on this, I'd look into starting from scratch and trying to 
build things up by chunks.  The hard part would be the core of the 
timekeeping stuff, processing replies from a server.  Between the RFC, the 
book, and the code, we should be able to figure out how to do that.  Or 
maybe, look at chrony and try something new.

Is there a yacc/bison for Go?


-- 
These are my opinions.  I hate spam.