Re: gEDA-user: gerbv - not reading format

[Stuart Brorson <sdb@xxxxxxxxxx>]

Frank, Julian,

Thanks for the bug report.  It's interesting that sloppy code makes
gerbv choke.   Moving forward I'd like gerbv to silently flag and
identify sloppy code, but keep processing.  Later,
the user can request a "gerber check" window which presents him
statistics about codes and errors found while processing his files.
That way gerbv can become as much a diagnostic tool as a simple
viewer.  It's on my todo list to implement this type of functionality.

One question, however:  Does anybody know how common a line with no *
is in the universe of gerber files generated by EDA programs?  i.e. is
this a common (bad) convention?  (DJ -- hint hint?)  Any thoughts
about how to handle it which differ from my proposal?

Stuart


On Mon, 3 Dec 2007, Julian wrote:

> Frank,
>    It looks like the RS274x manual has sloppy code in it.  The G04 code
> in line 1 is supposed to end with a "*" at the end of the line to signal
> it is finished (see section on G-codes in the manual). gerbv keeps
> reading until it finds a *, which made it advance past the FS statement
> in the next line. If you add a final "*" to line 1, it should work.
>    Maybe we'll look into adding a fix for this problem and let a
> carriage return also work to finish out a G code, just to make sure we
> handle this type of malformed code.  Thanks for pointing this problem
> out.
>
> Cheers,
> Julian
>
>
>
> _______________________________________________
> geda-user mailing list
> geda-user@xxxxxxxxxxxxxx
> http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
>


_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user