X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Tue, 20 Nov 2012 01:46:26 +0100 From: Kai-Martin Knaak To: geda-user AT delorie DOT com Subject: Re: [geda-user] Re: Objects of objects Message-ID: <20121120014626.651cb18c@akka> In-Reply-To: <20121102122705.7FAEF8130ED5@turkos.aspodata.se> References: <54CAA7EE-7638-4B89-8197-111D0493F859 AT noqsi DOT com> <508CE947 DOT 4050408 AT xs4all DOT nl> <665E18E2-E9F9-40E4-9DE1-CC8FDBBDCB00 AT noqsi DOT com> <508EE43F DOT 5050505 AT neurotica DOT com> <9B14233C-F3A7-489C-BDC7-F6EAAAFCAB51 AT noqsi DOT com> <8835FFD4-C2F8-4EBF-BA06-2EFD38B47865 AT noqsi DOT com> <20121101124136 DOT 247F28117B6F AT turkos DOT aspodata DOT se> <20121101143159 DOT 3AF688130EC0 AT turkos DOT aspodata DOT se> <2012110 1213405 DOT 35D3A8130ECB AT turkos DOT aspodata DOT se> <7A0F89F3-507E-43E2-B534-595B0B1013F2 AT noqsi DOT com> <20121102122705 DOT 7FAEF8130ED5 AT turkos DOT aspodata DOT se> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/0RXv9v=lWflmG5l0ogD2RzF"; protocol="application/pgp-signature" X-Provags-ID: V02:K0:tJeLV1dsVw3MIMbM/40CvfbCRwwPv59IdOenFmjkWJB MYiM0MCKNeP/DZ7GoklA5QLVwgWaUXgOPPcY9ay2cAcIFKKRxX dFkeH9l83hrMio/zyonk2puW+jdvr+ons0uj0gQ7K6Q7Lwu+O5 5b8qNXs8jd+wJX+eN0g6J7I0koaPS3toVVhxMK/shJbp5Dd4Wp 5q1L68c+hbtXBX20uL8epPjASeNTAuhp7yhgbOSC/XxAJw6shr gQaHgCwi42Xtu14p+wS0B6WPUXLZrOwSS9FyvrsxfP1YFXzxHI UP13eczGGmOFNWbsNXVpstLXA9HtyjRdszSsT/DEJrBrmW1/g= = 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 --Sig_/0RXv9v=lWflmG5l0ogD2RzF Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable karl AT aspodata DOT se (Karl Hammar) schrieb am 2. November 2012: > > Stating the obvious, but since circuits represent=C2=A0 physical > > constructs, recursion must inherently be limited. =20 >=20 > Well, gschem file format does say nothing about any physical > realisation of a schematic. Isn't that which makes it so > flexible? Any application that is supposed to resolve the recursion will suffer from infinite regress unless there is a termination condition. IMHO, there are two more general concepts that are missing in gschem format: 1) parameters that can be passed to sub sheets 2) a way to manipulate the parameters during interpretation of the schematics by gnetlist. When implemented, these two would make gschem much more powerful. Imagine a subsheet whose purpose is to amplify a voltage by an amount given by the parent sheet. This would be rather versatile, much like a sub procedure in programming. ---<)kaimartin(>--- --=20 Kai-Martin Knaak --Sig_/0RXv9v=lWflmG5l0ogD2RzF Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlCq0uIACgkQt9RkiGwLn1PO2gCeKfAn4W/6uUQFLNxfqe7kmIdp +voAmgPEb/zjySFajUTKTuv+dv3MIat/ =ENT/ -----END PGP SIGNATURE----- --Sig_/0RXv9v=lWflmG5l0ogD2RzF--