From owner-freebsd-questions Tue Dec 22 19:15:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14625 for freebsd-questions-outgoing; Tue, 22 Dec 1998 19:15:12 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from guepardo.vicosa.com.br (guepardo.tdnet.com.br [200.236.148.6]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA14619 for ; Tue, 22 Dec 1998 19:15:07 -0800 (PST) (envelope-from grios@netshell.vicosa.com.br) Received: from netshell.vicosa.com.br [200.236.148.193] by guepardo.vicosa.com.br with ESMTP (SMTPD32-4.03) id A1E8AFC008E; Wed, 23 Dec 1998 00:22:16 +03d00 Message-ID: <36805FBF.6C31DF5E@netshell.vicosa.com.br> Date: Wed, 23 Dec 1998 01:13:03 -0200 From: Gustavo Vieira G C Rios X-Mailer: Mozilla 4.5 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: David Wolfskill CC: eddie@silk.net, freebsd-questions@FreeBSD.ORG Subject: Re: FreeBSD and C Programming References: <199812221932.LAA25417@pau-amma.whistle.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yeah, you are right, but this does not mean i am worng. Your suggestion is what i told "known as many as possible from the machine you are programming to" . No matter if it is virtual or "real machine". And more, i believe that using a virtual machine is not practice. That's all folks. David Wolfskill wrote: > > >Date: Tue, 22 Dec 1998 00:43:32 -0200 > >From: Gustavo Vieira G C Rios > > >if you wanna be a real programmer you should know the hardware you are > >programming to, right ? > > I respectfully disagree. > > Consider, for example, that Donald Knuth's "The Art of Computer > Programming" uses an reference machine that doesn't really exist (though > I'm sure folks have written emulators for it... after he wrote the > book(s)). > > Best suggestion I have is to find a problem that you need to solve, and > for which a (set of) program(s) written in C might reasonably be considered > a viable approach to solving it. Look at good code as a starting-point; > try /usr/src/*, for example. Often, I've found that starting by > figuring out how to make a least-intrusive change to an existing program > can be quite instructive. (Then again, sometimes what the program > really *needs* is to be gutted & re-constructed from the ground up. > Experience can help you distinguish the two cases.) > > Start small; build on that. Revise your building-blocks until they're > reliable. > > Caveat: I don't write code for a living (usually); I do sysadmin work. > I have written code for a living, though, and have been known to do so > somewhat recently. > > david > -- > David Wolfskill UNIX System Administrator > dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 -- +-------------------------------------------------------------------+ " ... Overall we've found FreeBSD to excel in performace, stability, technical support, and of course price. Two years after discovering FreeBSD, we have yet to find a reason why we switch to anything else" -David Filo, Yahoo! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message