X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Wed, 6 Mar 2019 16:23:30 +0100 (CET)
From: Roland Lutz <rlutz AT hedmen DOT org>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] guile auto-compile failure
In-Reply-To: <20190306122848.55A4185E7F4C@turkos.aspodata.se>
Message-ID: <alpine.DEB.2.20.1903061614020.1851@nimbus>
References: <20190306122848 DOT 55A4185E7F4C AT turkos DOT aspodata DOT se>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On Wed, 6 Mar 2019, karl AT aspodata DOT se wrote:
> $ gsch2pcb small.sch
> /home/karl/git/openhw/boards_arm_aspo/stm32f105_can/Test_4/./simple.sym:2: error: failed to parse text object
> ERROR: Failed to load 'small.sch':
> Failed to run gnetlist

I just realized that this is the file you posted in your other mail.

The line which triggers the error is the first text object:
> T   400  3194   5 10  0 0   0 0 1

The problem are the extra spaces.  The old parsing routine just silently 
ignores them, but they are not allowed by the file format specification, 
so the new checks signal an error.

I believe it's pretty obvious that aligning fields to a certain column 
makes sense for human-written files, even though it may make processing 
the files with simple tools slightly more complicated; i.e. it's a bug in 
the specification.