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=gU79FW8fLwBN5RdoK9wxts06Ky/1nOyxehsWeAVpP+0=;
        b=FwrUr+MhUybY9b5HiR532NNNjrwT4kNZK8VkRLIxs1qx1fW8dUYAKb3U6AKIZDJy8J
         epdwih9/A5EQjIo2hLNwZ8VnqVc10PAKQuAm+hnAbUzZcGY65RVLBRgr6fxsBT+I29R+
         I8VDYY5b8hB3v+wj8GoC6W9JSdXv7sWHijg7FN4GP65vt742b/0LcVvQsMo32r8iFpvo
         FG9uFMarZUF3KgRC7EZckykXRYIekxAt8N5dBUFrxwWwzP26pUNOJG2vDB0VXo+FEP5c
         pXu0TJjbNtyYAb1xfd5sfp6z1iGbUW58+EI3ltgYjuk5vLe6beccdlTrOA/F8FSEU44L
         7MWQ==
MIME-Version: 1.0
X-Received: by 10.194.104.200 with SMTP id gg8mr8386169wjb.144.1445397505418;
 Tue, 20 Oct 2015 20:18:25 -0700 (PDT)
In-Reply-To: <CABuVarJAvo8TDR9-PRHghp6A=xMDPniVaZaGAqmN9uuQJ6NHWg@mail.gmail.com>
References: <CAC4O8c9rjGEsy6NP8kFz5jKRy51NOndbhU37gUa_Om70qbxVKg AT mail DOT gmail DOT com>
	<CABuVarJiWLMNh+cMcNF4vpv3aAm-eHKazu+i=F00WcBWF_=Oag AT mail DOT gmail DOT com>
	<CAC4O8c8n7RdxJ6Diq7UYkQAka16zwVQ_E+Wr0JGbiy3_VQw0jw AT mail DOT gmail DOT com>
	<20151019205802 DOT GA6798 AT recycle DOT lbl DOT gov>
	<20151020180706 DOT GC16826 AT localhost DOT localdomain>
	<201510201818 DOT t9KIIcFc016851 AT envy DOT delorie DOT com>
	<20151020184943 DOT GD16826 AT localhost DOT localdomain>
	<CABuVarJAvo8TDR9-PRHghp6A=xMDPniVaZaGAqmN9uuQJ6NHWg AT mail DOT gmail DOT com>
Date: Tue, 20 Oct 2015 19:18:25 -0800
Message-ID: <CAC4O8c8aobnZU5OqX4VNy4EDhSXY3Owk3f=1AsJ8Jvg4OEgOpA@mail.gmail.com>
Subject: Re: [geda-user] C99
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
Content-Type: multipart/alternative; boundary=089e010d8212deb20e052294d4c1
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

--089e010d8212deb20e052294d4c1
Content-Type: text/plain; charset=UTF-8

On Tue, Oct 20, 2015 at 1:08 PM, Sergey Stepanov (no DOT such DOT process AT gmail DOT com)
[via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:

> > Does it mean that functions related to C99 like 'hypot' cannot be used
> yet
>
> This one is supported for years (or even decades) as an extension to
> C89. There is one problem with it: if you use C89 and specific flags
> to compile 'pure c code', you should turn on some defines before
> `#include <math.h>`
>
> > though now I cannot find that branch in the repo.
>
> I just return it back after rebasing and testing.
>

Rebase of publicly pushed branches is often considered bad as it causes
confusion of this sort.  Even after branches get their final merge rebase
to master  its best to keep them around under their original name and from
original branch point, as that's likely the one most tested and free of
unanticipated adverse interactions with other new code.

Of course sometimes you want to rebase during devel but after the initial
publish.  I don't think we have a policy for this but I would suggest maybe
tag the old version as "rebased" or something and copy the branch to a new
name with _rebaseN appended.

The point is to not rewrite history (at least until rebase to master) so it
doesn't change under people.

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Tue, Oct 20, 2015 at 1:08 PM, Sergey Stepanov (<a href=3D"mailto:no.=
such DOT process AT gmail DOT com">no DOT such DOT process AT gmail DOT com</a>) [via <a href=3D"mail=
to:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>] <span dir=3D"ltr">&lt;=
<a href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">geda-user AT delori=
e.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=
=3D"">&gt; Does it mean that functions related to C99 like &#39;hypot&#39; =
cannot be used yet<br>
<br>
</span>This one is supported for years (or even decades) as an extension to=
<br>
C89. There is one problem with it: if you use C89 and specific flags<br>
to compile &#39;pure c code&#39;, you should turn on some defines before<br=
>
`#include &lt;math.h&gt;`<br>
<span class=3D""><br>
&gt; though now I cannot find that branch in the repo.<br>
<br>
</span>I just return it back after rebasing and testing.<br></blockquote><d=
iv><br></div><div style=3D"">Rebase of publicly pushed branches is often co=
nsidered bad as it causes confusion of this sort.=C2=A0 Even after branches=
 get their final merge rebase to master =C2=A0its best to keep them around =
under their original name and from original branch point, as that&#39;s lik=
ely the one most tested and free of unanticipated adverse interactions with=
 other new code.</div><div style=3D""><br></div><div style=3D"">Of course s=
ometimes you want to rebase during devel but after the initial publish.=C2=
=A0 I don&#39;t think we have a policy for this but I would suggest maybe t=
ag the old version as &quot;rebased&quot; or something and copy the branch =
to a new name with _rebaseN appended.</div><div style=3D""><br></div><div s=
tyle=3D"">The point is to not rewrite history (at least until rebase to mas=
ter) so it doesn&#39;t change under people.</div><div><br></div></div></div=
></div>

--089e010d8212deb20e052294d4c1--