On Fri, Jun 22, 2012 at 02:33:13PM +0200, Marc Espie wrote:
> On Fri, Jun 22, 2012 at 01:57:10PM +0200, Gilles Chehade wrote:
> > On Fri, Jun 22, 2012 at 01:20:09PM +0200, Marc Espie wrote:
> > > >
> > > > Actually, before a webserver, I'd recommend learning how to write a
> > > > shell
> > > > as it will have you deal with lots of concepts you would not see
> > > > otherwise ... then network programming :-p
> > >
> > > Just because you suffered thru a fucked-up education that's
> > > ass-backwards doesn't mean you should wish it on other people.
> > > ('may you live in interesting times', the old chinese curse).
> > >
> >
> > Your opinion is pointless, you actually *like* perl ;-)
> >
> >
> > > A shell is one of the most complicated pieces of C code to get right,
> > > between the fucked-up parser, the lazy evaluation, the arcane shit you
> > > have to do to various file descriptors, and the signal handling.
> > >
> > > Among other things.
> > >
> >
> > That's because you think the goal is to write a perfect shell.
> > The goal is to use fork, exec, signals, process groups, etc...
>
> yeah, right... and do it without any proper courses either.
>
> So that, afterwards, when I quizz students, they don't even understand
> how wait() works or anything about signal semantics.
>
> Yet they validated that specific project...
>
That's an implementation detail :-p
Someone who really wants to understand things will look at the man
pages and try to understand, someone who doesn't give a damn about
getting things done right will produce crap with or without proper
courses ...
--
Gilles Chehade
https://www.poolp.org @poolpOrg
