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:date:message-id:subject:from:to:content-type;
	bh=3cexylpaGqbqHY3ksSLB/opJ1mu2NVuh+Btidt33yQg=;
	b=vA4muCn0WcfPujGlar9+kEZCGigxZkrsEX9FZGNNVS0HtL8+Y6TUZRp1SwKvLnJWe0
	9dxzjA1WHvfyRK6MVsy7V7le+n3NVLKXK8XYntC7g5SZsX7T9zhppbKC7iQY5349oOTk
	/4ywuWFSDA9145pkwEqRq9cMDDjFw0xmrYoLmNULIgem897s+/Dk/JBoVcipaNfhthM8
	2wUyssr7v6LMkpSGkFaoPfiA7dG68DX6g4tunA/rwEN5RwTn+/axSn9dbt3H6XQ3dVO7
	P1oCoAoLpw8jtDl/zvIxq9y5EuYp0Pg1izqeZsrFaBXU6eT5AUaAkr8LogruF120fz5E
	L0Hw==
MIME-Version:	1.0
X-Received:	by 10.28.93.195 with SMTP id r186mr6584177wmb.37.1450208036951;
	Tue, 15 Dec 2015 11:33:56 -0800 (PST)
Date:	Tue, 15 Dec 2015 10:33:56 -0900
Message-ID:	<CAC4O8c_Jc98kmjDp_O2hKbY9BWWAjGk+nb0L5L=jqXfeTAYGGA@mail.gmail.com>
Subject:	[geda-user] merge please (or rebase if you must)
From:	"Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Reply-To:	geda-user AT delorie DOT com

--001a11469daee49dff0526f4de70
Content-Type: text/plain; charset=UTF-8

I never heard back on the merge commit privileges, so perhaps the answer is
no.
That's fine, I don't care as long as the merges happen.

There are four branches.  The first contains the other three:

home/bkerin/drc_fix_violation_locations

    This one contains the other three branches below, plus a lot of new code
    that causes DRC to give much better location information, and fixes to
    make arcs functional (they're pretty badly broken in release version).
    This is all pretty carefully tested for correctness with respect to
    connectivity and DRC.

    There is one objectionable part I'm aware of: unsupported arcs (of
    ellipses, degenerate, with square flag) are rejected at parse time,
with no
    arc inserted.  This is different than the current behavior of adding an
    arc that doesn't fit the description given in the file.  This is the
right
    thing to do in general I think, but unfortunately it breaks backwards
    compatability very slightly: someone might be using an arc of this sort
    somewhere.  So it could instead just warn and insert the same bad arc it
    does now.  I'm not really clear how the backwards compat mechanism for
the
    format is intended to work, perhaps someone can help here.  I guess what
    to do depends on how that works and whether we want to improve bad input
    rejection in this small way or maintain this small backwards
compatability.


home/bkerin/backtrace

    Stuff to print out a backtrace on request or assertion violation
    on linux only.


home/bkerin/geometry_module_2

    math-only (i.e. application neutral) geometry routines


home/bkerin/debugging_markers

    Add scale-independent background-contrasted dots at given coordinates.
    Useful for debugging geometry-related code


Please merge or let me know what needs to change.

Thanks,
Britton

--001a11469daee49dff0526f4de70
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><br></div><div style=3D""><div>I never heard back on =
the merge commit privileges, so perhaps the answer is no.</div><div>That&#3=
9;s fine, I don&#39;t care as long as the merges happen.</div><div><br></di=
v><div>There are four branches.=C2=A0 The first contains the other three:</=
div><div><br></div><div>home/bkerin/drc_fix_violation_locations</div><div><=
br></div><div>=C2=A0 =C2=A0 This one contains the other three branches belo=
w, plus a lot of new code</div><div>=C2=A0 =C2=A0 that causes DRC to give m=
uch better location information, and fixes to</div><div>=C2=A0 =C2=A0 make =
arcs functional (they&#39;re pretty badly broken in release version).</div>=
<div>=C2=A0 =C2=A0 This is all pretty carefully tested for correctness with=
 respect to</div><div>=C2=A0 =C2=A0 connectivity and DRC.</div><div><br></d=
iv><div>=C2=A0 =C2=A0 There is one objectionable part I&#39;m aware of: uns=
upported arcs (of</div><div>=C2=A0 =C2=A0 ellipses, degenerate, with square=
 flag) are rejected at parse time, with no</div><div>=C2=A0 =C2=A0 arc inse=
rted.=C2=A0 This is different than the current behavior of adding an</div><=
div>=C2=A0 =C2=A0 arc that doesn&#39;t fit the description given in the fil=
e.=C2=A0 This is the right</div><div>=C2=A0 =C2=A0 thing to do in general I=
 think, but unfortunately it breaks backwards</div><div>=C2=A0 =C2=A0 compa=
tability very slightly: someone might be using an arc of this sort</div><di=
v>=C2=A0 =C2=A0 somewhere.=C2=A0 So it could instead just warn and insert t=
he same bad arc it</div><div>=C2=A0 =C2=A0 does now.=C2=A0 I&#39;m not real=
ly clear how the backwards compat mechanism for the</div><div>=C2=A0 =C2=A0=
 format is intended to work, perhaps someone can help here.=C2=A0 I guess w=
hat</div><div>=C2=A0 =C2=A0 to do depends on how that works and whether we =
want to improve bad input</div><div>=C2=A0 =C2=A0 rejection in this small w=
ay or maintain this small backwards compatability.</div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0</div><div>=C2=A0=C2=
=A0</div><div>home/bkerin/backtrace</div><div><br></div><div>=C2=A0 =C2=A0 =
Stuff to print out a backtrace on request or assertion violation</div><div>=
=C2=A0 =C2=A0 on linux only.</div><div><br></div><div><br></div><div>home/b=
kerin/geometry_module_2</div><div><br></div><div>=C2=A0 =C2=A0 math-only (i=
.e. application neutral) geometry routines</div><div><br></div><div><br></d=
iv><div>home/bkerin/debugging_markers</div><div><br></div><div>=C2=A0 =C2=
=A0 Add scale-independent background-contrasted dots at given coordinates.<=
/div><div>=C2=A0 =C2=A0 Useful for debugging geometry-related code</div><di=
v><br></div><div><br></div><div>Please merge or let me know what needs to c=
hange.</div><div><br></div><div>Thanks,</div><div>Britton</div></div></div>

--001a11469daee49dff0526f4de70--

- Raw text -