On Mon, Jan 10, 2011 at 13:57, John Anderson wrote:
> The asc2g code looks at the first line of the input file to
> determine if the file is the current ascii version (i.e., a tcl script)
> or the old ascii version. It is looking for a "title" or "put" command
> on the first line to identify t
The asc2g code looks at the first line of the input file to
determine if the file is the current ascii version (i.e., a tcl script)
or the old ascii version. It is looking for a "title" or "put" command
on the first line to identify tcl input. This could be easily changed to
do this check
On Jan 6, 2011, at 6:15 PM, Tom Browder wrote:
> Should I not expect comments to work?
Sounds like a bug to me. Given they are simple text/tcl files, being
able to add comments seems like a no-brainer.
Cheers!
Sean
---
As an experiment I added a tcl comment as the first line in my
hitherto working ascii file which makes a valid .g with
asc2g t.asc t.g
Now it bombs with:
ERROR: _bu_alloc size=0 (cnt=0, sz=8) botbld: vertices
ERROR: bu_malloc(0)
ERROR: bu_malloc(0)
Saving stack trace to (unknown)-14268-bomb
