> > And finally Aaron 28748 lines of code? What a slacker > > *Moe Howard slaps Antny on back of head*: "Hey. Wake up and go to sleep again."
To be fair, most of that is from src/lib/netlist/generated/static_solvers.cpp, which is a machine-generated file to allow the solvers for the circuit equations to be compiled in advance rather than generated at runtime; that makes the solver run quite a bit faster. On the other hand, if I'm reading this pull request report right, Antny's total seems to have missed some major chunks of human-written code, so it looks like Aaron really did write nearly 10,000 lines for this. Wow. Just, wow.
> > Does anyone know of a list of schematics that are "on hand" and ones that are needed? > > Is there a net-list dev wish list for schematics? > > Unfortunately it is more than schematics by themselves because of possible misprints > in some of the drawings. Access to actual hardware needed as well to verify/test such > as what Colin had to do with Midway 280zzzap analog audio.
But having schematics is a hell of a lot better than working without them. They should be verified and may have to be corrected, sure, but trying to do this strictly from photographing and tracing boards? Yikes!
> > I wonder where we are with the whole NL picture. Is the "framework" pretty much done? > > Unsure about the 'foundation/framework' core code, but the device components list > has to still be lengthy by itself.
Basic framework is clearly done enough to use, but couriersud still has plenty of ideas for improvements and expansion.