X-Authentication-Warning: delorie.com: mail set sender to geda-help-bounces using -f
X-Recipient: geda-help AT delorie DOT com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=uS3Ws81FqGQ/VSDaP8LX/8ZLQH4+tOPg4Y3hk3+8Gb0=;
        b=xAW3365uNPfpdFANyH6fYDH+3gRaNEGCacykTXqkTPlZ1VwONaaoGtnPI/UObke00D
         kyL7e2UzRCYC7yzmbSvYeNXD32zTEOQUc9NYePSGQxQAmW0CeXZDLPX/vQvyFwq51U1W
         prpvvSXCXbbe9E0HQmc8BB62ZIL/CAGAEViKY=
MIME-Version: 1.0
In-Reply-To: <4F1C643E.7080503@gmail.com>
References: <4F1A1196 DOT 20100 AT gmail DOT com>
	<201201210150 DOT q0L1o04r012622 AT envy DOT delorie DOT com>
	<4F1C643E DOT 7080503 AT gmail DOT com>
Date: Sun, 22 Jan 2012 16:22:00 -0500
Message-ID: <CAPFCoithVSn-AOggs4nZscwYN+5ejH7Cb38VEHDHFzrVLY7Wxg@mail.gmail.com>
Subject: Re: [geda-help] Help, how can I help?
From: John Hudak <jjhudak AT gmail DOT com>
To: geda-help AT delorie DOT com
Content-Type: multipart/alternative; boundary=f46d0418266227276704b7248108
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

--f46d0418266227276704b7248108
Content-Type: text/plain; charset=ISO-8859-1

Hi Darryl:

- 'a getter'.....yep, I thought the same thing- back in the day of
designing tubes.....
- a caution about learning C - (and this is my opinion after teaching and
observing lots of students) - you can 'hang' yourself lots of ways in C.
IMHO, just as important as learning the language syntax and semantics is
learning the pitfalls.  Here is a ref to something I reference in class:
http://www.csd.uwo.ca/~moreno/cs2211_moreno/ctraps-AKoenig.pdf
If you google C pitfalls, you will find lots of docs.

If you are interested in a good book for learning C, this is one of my
favorites:
Engineering Problem Solving with C, Delores Etter

Purists will point to the Kerhanan & Ritchey book, which is a great
reference but is a little tough to plow through to learn the language.

In some programming languages, particularly for C,  the knowledge of  some
C coding standards is very helpful. I would like to think that the ppl in
this group use some standard.  Hopefully it is documented.  If not, if you
look around the web you will find C coding standards and styles that are
commonly used. - Delores Etters book contains a lot practices that good C
coders follow.
Good luck
-John



On Sun, Jan 22, 2012 at 2:32 PM, Darryl Gibson <n2diy2 AT gmail DOT com> wrote:

> On 01/20/2012 08:50 PM, DJ Delorie wrote:
> > This is getter for geda-user - you're not asking for help, you're
> > asking how to get involved.  But I'll answer here anyway :-)
>
> A getter? Haven't heard that term since I was studying vacuum tubes! :)
>
> > The gEDA project uses a couple of languages, but primarily we use C
> > and guile (a scheme/lisp variant).  There are some ancillary
> > languages, like Makefiles, shell scripts, M4, etc.
>
> Ok, I think I should get acquainted with make, I've noticed folks
> experiment with that fairly often.
>
> And I'll tackle C, I've been shying away from it for years because it
> looks like it has a steep learning curve.
>
> >
> > As for git, you should at least learn how to clone and update a source
> > tree so you can stay up to date, and generate a diff to pass
> > "upstream".
>
> Ok. I just did a clone Saturday night, do I need to update too?
>
> And I'll hit the books to learn the terminology and concepts of git.
>
> > To learn the *sources* however, your best bet is to dig into the bug
> > list, pick something that you think might be easy to fix, and see if
> > you can fix it.
>
> Roger that.
> --
> Darryl Gibson N2DIY
> Linux, free software, for the people, by the people.
>
>
>
>
>

--f46d0418266227276704b7248108
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Darryl:<br><br>- &#39;a getter&#39;.....yep, I thought the same thing- b=
ack in the day of designing tubes.....<br>- a caution about learning C - (a=
nd this is my opinion after teaching and observing lots of students) - you =
can &#39;hang&#39; yourself lots of ways in C.=A0 IMHO, just as important a=
s learning the language syntax and semantics is learning the pitfalls.=A0 H=
ere is a ref to something I reference in class:<br>
<a href=3D"http://www.csd.uwo.ca/~moreno/cs2211_moreno/ctraps-AKoenig.pdf">=
http://www.csd.uwo.ca/~moreno/cs2211_moreno/ctraps-AKoenig.pdf</a><br>If yo=
u google C pitfalls, you will find lots of docs.<br><br>If you are interest=
ed in a good book for learning C, this is one of my favorites:<br>
<span class=3D"booktitle">Engineering Problem Solving with C, Delores Etter=
<br><br>Purists will point to the Kerhanan &amp; Ritchey book, which is a g=
reat reference but is a little tough to plow through to learn the language.=
<br>
<br>In some programming languages, particularly for C,=A0 the knowledge of=
=A0 some C coding standards is very helpful. I would like to think that the=
 ppl in this group use some standard.=A0 Hopefully it is documented.=A0 If =
not, if you look around the web you will find C coding standards and styles=
 that are commonly used. - Delores Etters book contains a lot practices tha=
t good C coders follow.<br>
Good luck<br>-John<br><br><br></span><br><div class=3D"gmail_quote">On Sun,=
 Jan 22, 2012 at 2:32 PM, Darryl Gibson <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:n2diy2 AT gmail DOT com">n2diy2 AT gmail DOT com</a>&gt;</span> wrote:<br><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex">
On 01/20/2012 08:50 PM, DJ Delorie wrote:<br>
&gt; This is getter for geda-user - you&#39;re not asking for help, you&#39=
;re<br>
&gt; asking how to get involved. =A0But I&#39;ll answer here anyway :-)<br>
<br>
A getter? Haven&#39;t heard that term since I was studying vacuum tubes! :)=
<br>
<br>
&gt; The gEDA project uses a couple of languages, but primarily we use C<br=
>
&gt; and guile (a scheme/lisp variant). =A0There are some ancillary<br>
&gt; languages, like Makefiles, shell scripts, M4, etc.<br>
<br>
Ok, I think I should get acquainted with make, I&#39;ve noticed folks<br>
experiment with that fairly often.<br>
<br>
And I&#39;ll tackle C, I&#39;ve been shying away from it for years because =
it<br>
looks like it has a steep learning curve.<br>
<br>
&gt;<br>
&gt; As for git, you should at least learn how to clone and update a source=
<br>
&gt; tree so you can stay up to date, and generate a diff to pass<br>
&gt; &quot;upstream&quot;.<br>
<br>
Ok. I just did a clone Saturday night, do I need to update too?<br>
<br>
And I&#39;ll hit the books to learn the terminology and concepts of git.<br=
>
<br>
&gt; To learn the *sources* however, your best bet is to dig into the bug<b=
r>
&gt; list, pick something that you think might be easy to fix, and see if<b=
r>
&gt; you can fix it.<br>
<br>
Roger that.<br>
<span class=3D"HOEnZb"><font color=3D"#888888">--<br>
Darryl Gibson N2DIY<br>
Linux, free software, for the people, by the people.<br>
<br>
<br>
<br>
<br>
</font></span></blockquote></div><br>

--f46d0418266227276704b7248108--