X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-TCPREMOTEIP: 108.49.234.33 X-Authenticated-UID: jpd AT noqsi DOT com From: John Doty Content-Type: multipart/alternative; boundary="Apple-Mail=_FD3CFF0E-BB3C-44D0-B56A-14A105A0C0AC" Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\)) Subject: Re: [geda-user] empty attributes Date: Sun, 26 Sep 2021 14:13:42 -0400 References: <20210925133011 DOT D0B918587B70 AT turkos DOT aspodata DOT se> <20210925194712 DOT 152EA8587FD0 AT turkos DOT aspodata DOT se> To: "Erich Heinzle (a1039181 AT gmail DOT com) [via geda-user AT delorie DOT com]" In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3608.120.23.2.7) 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 --Apple-Mail=_FD3CFF0E-BB3C-44D0-B56A-14A105A0C0AC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Sep 26, 2021, at 10:12 AM, Roland Lutz wrote: >=20 > Allowing component objects to have an empty refdes would be another, = different change. What would it mean for a component to have an empty = refdes? If the empty string was treated like any other value, all such = components would be merged into one package. Is this useful behavior? It=E2=80=99s consistent behavior. An empty string is a perfectly good = string. It is equal to any other empty string, not equal to other = strings. There is no reason to have any special rule for attribute = values that happen to be empty strings. Nor is there any reason to = exclude them. It=E2=80=99s not a change that needs any change in the = special treatment of refdes. John Doty Noqsi Aerospace, Ltd. jpd AT noqsi DOT com --Apple-Mail=_FD3CFF0E-BB3C-44D0-B56A-14A105A0C0AC Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

On Sep 26, 2021, at 10:12 AM, Roland Lutz <rlutz AT hedmen DOT org> = wrote:

Allowing component objects to = have an empty refdes would be another, different change. What = would it mean for a component to have an empty refdes? If the = empty string was treated like any other value, all such components would = be merged into one package. Is this useful behavior?

It=E2=80=99s = consistent behavior. An empty string is a perfectly good string. It is = equal to any other empty string, not equal to other strings. There is no = reason to have any special rule for attribute values that happen to be = empty strings. Nor is there any reason to exclude them. It=E2=80=99s not = a change that needs any change in the special treatment of = refdes.

John Doty = Noqsi = Aerospace, Ltd.

jpd AT noqsi DOT com

= --Apple-Mail=_FD3CFF0E-BB3C-44D0-B56A-14A105A0C0AC--