X-Authentication-Warning: delorie.com: mail set sender to geda-help-bounces using -f X-Recipient: geda-help AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=+ukXrCOk7cZavuP9bRwCYHM4BcF6vVJRbniNNjwl5ic=; b=muYPHA3sW+7kXHUWKYqnwFCw06h1jmsR//DOtIgCxGOImHAhR/Wf69jTMCx42IYaCt i0vw1LSsIPqliToDy9iJTlZZ/m3zEmnLLO4FZm05Zglxr5/bVE7lQggRcQechZ7IcuGI bHmP+JRzWzOQR48wWkE/zoeeASGaUtFYRK2i42KzCSoQ76mTsdNdFky2dJhmCP6bKVJ+ B651Bj/arq85XUxtZ2FIWQ7v2/s/A2nHB2vhWH1pgMhdsOlf8JeG2C3MZ7mMMmAnchhg Tf2z8zhQ82djsd94K7WA+lOHYRh4qFzs1NKbWBpphtW0OoKzmm7MxV2jjpS8RofjDtfc e5AQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mail-followup-to :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=+ukXrCOk7cZavuP9bRwCYHM4BcF6vVJRbniNNjwl5ic=; b=Ox7v67azZrRsgYsJP1L21EjJwi3ujLsgiukCYMy26T9NTE9dEO99l3ensxQ9CLeITE rkBkB+fwIUgTxeMPIJHwIteObLqbarKW4ECUd6poNihC4EpT4vlAKw+cybUvEJ8kPrES uZvH2VUqH/IYBmZdxUo98ANaqrItEjTOBf0wzv6wlX0W8MYRN2hAGtZBFahM/5bByk+Y ee/ihSdcRNm5Ng82yI1qAdeFT/o0nCm0uOSOAo6qwzG5HHaGeumQodSfiW0+nUqJE9p0 vfvRPqDDuwxvepdLJ5O8/jNW+YnQO2haf43DLdaBodQaRw93FcnTlZ7t/u/Yj8BO4VLw sOtQ== X-Gm-Message-State: AMke39kVwVIDBxGf43DecLMGgA0H5VpazGH9J0LXVontuncUhuFvi5Wl94IBVTS3HsyHaw== X-Received: by 10.25.161.208 with SMTP id k199mr3607800lfe.165.1487444176745; Sat, 18 Feb 2017 10:56:16 -0800 (PST) Date: Sat, 18 Feb 2017 21:56:14 +0300 From: "Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via geda-help AT delorie DOT com]" To: geda-help AT delorie DOT com Subject: Re: [geda-help] Please help with multiple-pages schematics Message-ID: <20170218185614.GA25608@localhost.localdomain> Mail-Followup-To: geda-help AT delorie DOT com References: <11BDEC14-5D1D-4157-B552-582C1E75D00E AT noqsi DOT com> <20170218180232 DOT GB23464 AT localhost DOT localdomain> <4FA4C5C8-4B56-493A-94AC-1D4920C201F3 AT noqsi DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4FA4C5C8-4B56-493A-94AC-1D4920C201F3@noqsi.com> User-Agent: Mutt/1.5.23 (2014-03-12) Reply-To: geda-help AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-help AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Sat, Feb 18, 2017 at 11:29:39AM -0700, John Doty wrote: > > On Feb 18, 2017, at 11:02 AM, Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via geda-help AT delorie DOT com] wrote: > > > On Sat, Feb 18, 2017 at 10:39:06AM -0700, John Doty wrote: > >> > >> On Feb 18, 2017, at 3:41 AM, Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-help AT delorie DOT com] wrote: > >> > >>> > >>> On 18 February 2017 at 08:27, Vasily Olekhov (olekhov AT gmail DOT com) [via geda-help AT delorie DOT com] wrote: > >>> Thank you John, I've got your point. > >>> Can you hint how should I reference CONN1 on the second page? > >>> It should be the same component CONN1 from the first page. > >>> > >>> This is a slightly unusual way of doing things. I _thought_ it should work, but having checked, it is actually generating a bad netlist. > >>> > >>> My Windows dual-boot has gEDA 1.6.1..... so this could be some bug which is fixed since then. What version do you use? > >>> > >> > >> This is a very old bug. I suppose it’s rarely encountered: most of us don’t try to do things that way. It’s still present in lepton pulled from git yesterday. > > > > Yes, this is > > 1) a misguiding abuse of components in schematics > > On the other hand, we *do* allow the case of a “package” derived from multiple symbol instances. Here, Vasily is trying to use that freedom in a way that appears to make sense in his application. Not for such cases, anyway. See (2). Such using can get confusing even for the author after a while, especially when schematics are large enough. > > > 2) a bug in gnetlist consisting in having no check of package > > consistency wrt the number of its pins and conflicting pinnumbers > > (and pinseqs IIUC). > > If we decide this is not allowed, the user should receive an error message rather than a bad netlist. Certainly, the back end should never encounter a pin connected to two different nets. Yes. Bug reports are welcome. -- Vladimir