[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gEDA-dev: Stack corruption PCB bug in hid_parse_actions????
On Thu, 2006-09-07 at 09:58 -0400, Stuart Brorson wrote:
> On Thu, 7 Sep 2006, Peter Clifton wrote:
>
> [ . . . snip . . . .]
> > I think this risks producing code which is more difficult to understand
> > and debug. As this function doesn't seem to be a bottle-neck point, I'll
> > leave it as is.
> [snip] Simple (but adequate) code is therefore preferred over
> tricker code which offers an unnoticible performance improvement since
> the simple code can be understood and hacked by more developers.
>
> Just MHO,
>
> Stuart
Oh dear.. you won't like the project manager backend I'm writing for
scripting gsch2pcb updates to a running copy of PCB. Its in Python and
(mis)uses generator functions to implement a less than obvious program
flow. It writes out to PCB, then the generator function yields, until an
IO callback causes it to re-enter where it left off.
Its quite an elegant way to do it in some respects, and saves a complete
state-machine implementation for every action I request PCB to do (which
needs a response). Will require a little documentation.
Peter C.
_______________________________________________
geda-dev mailing list
geda-dev@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev