X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=rTcxje4AJHjGhklnEARvjst0++9jxuPI1XsP9jhPB9I=;
        b=Pm/yLYBHcYNbsR7Y0iB7y+OpVH3GDxHQA7vnJYcZ8bV1/kcFRUeSzS1yh13MyMsL9B
         bamIUFYP16XT7UppnqFE0Ph5MUcIlWcRmmqCBY98MmI0xo7BLVlCtt1FpXkGPptK/O+q
         M0wK/DISwJp8Wd22LXclfH6MYxveAfwatD44OjZKPUw/cTOLgZiHxE4DC/jx4l0PY4gy
         JeN9Ii2LSvMT8WZeYThyujyanMizAQondonsm0Z56+RXCyMBXAHEmva+fTxYT8VsvOZ6
         3uSOp5pz8Mp6ghnBS9hbclO6Ol2c9Xy6fABUldc8IZTdoHnVlGuxvAIwC7WNvuxewyTT
         knVg==
MIME-Version: 1.0
X-Received: by 10.112.180.230 with SMTP id dr6mr8569959lbc.72.1445524890184;
 Thu, 22 Oct 2015 07:41:30 -0700 (PDT)
In-Reply-To: <20151022113635.GA16105@visitor2.iram.es>
References: <CAM2RGhSvpVvboJ-gdyrojAzggFEBnAr30CKNQBefjci-PA1n6g AT mail DOT gmail DOT com>
	<201510220112 DOT t9M1Ccfq013731 AT envy DOT delorie DOT com>
	<CAM2RGhQhNkShqtN8uyCSd7R+V4FgLXDZTvTC2RTdmKF7C_8ndA AT mail DOT gmail DOT com>
	<201510220136 DOT t9M1a5Uw015222 AT envy DOT delorie DOT com>
	<CAM2RGhQOpnBXbZXngNq=RcQTZN=UrU+PGzTZ9AC=xKNfu_zQkQ AT mail DOT gmail DOT com>
	<201510220149 DOT t9M1nrIe016145 AT envy DOT delorie DOT com>
	<CAM2RGhQ26+gpcAeTdgJpBEh0egOGLYcpizQ+B6kfTQLowEk5xQ AT mail DOT gmail DOT com>
	<20151022023002 DOT GA25952 AT recycle DOT lbl DOT gov>
	<20151022090751 DOT ecb5bc25c7d968646dea2e85 AT gmail DOT com>
	<n0ad7l$79l$1 AT ger DOT gmane DOT org>
	<20151022113635 DOT GA16105 AT visitor2 DOT iram DOT es>
Date: Thu, 22 Oct 2015 10:41:30 -0400
Message-ID: <CAM2RGhSzM-7vb3Oz3wbxy33i1ZeiWQVE3i=St6SJdqccnsVg3Q@mail.gmail.com>
Subject: Re: [geda-user] A lesson from gnet-makefile
From: "Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: gEDA users mailing list <geda-user AT delorie DOT com>
Content-Type: text/plain; charset=UTF-8
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 Thu, Oct 22, 2015 at 7:36 AM, Gabriel Paubert (paubert AT iram DOT es)
[via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
> On Thu, Oct 22, 2015 at 12:19:32PM +0200, Kai-Martin Knaak wrote:
>> Nicklas Karlsson  wrote:
>>
>> > Yes, only problem with star ground symbol in gschem is how many pins
>> > it should have. In pcb for many cases it would make sense with one
>> > common connection point.
>> >
>> Last time this topic surfaced on the mailing list the most practical
>> suggestion was to exploit a pecularity of text in copper:
>> The connection check of geda-pcb completely ignores letters. Insert a
>> large "-" and make regular tracks overlap with the character but not
>> connect to each other.
>>
>> This is of course an abuse of a missing feature (connection check of
>> strings in copper) which might break if/when somebody takes the time
>> to fix it. But at least it works now.
>>
>> And it gives a hint for a second best solution: Add a tag "ignore-for-
>> connection-check" which can be attached to a track segment. This would
>> of course also not check for unwanted connections to the tagged
>> segment. But since it is an explicit localized exception, the risk is
>> manageable. After all, we live with not connection checked text all
>> the time...
>
> Indeed, having "non-conductive copper" is probably the best solution, it
> also allows to build some RF structures like directional couplers.

I support "ignore-connection-check" as an attribute for nets but not
"non-conductive copper" because it is poor taste linguistically.

There are two ways to look at this.
1. A complete lack of understanding in PCB of what the structure you
are making is and apply the "ignore-connection-check" attribute
2. A functional understanding in PCB of what the structures are with
hierachical nets that have properties describing what you are doing.

As much as I like #2 the reality is that we will always be playing
catchup to what people are working with so it makes sense to do both.

>     Gabriel



-- 
Home
http://evanfoss.googlepages.com/
Work
http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/