"G.W. Haywood" wrote:
>
> Hi there,
>
> On Mon, 30 Oct 2000, Greg Cope wrote:
>
> > In theory there is no reason why this should not be translateable to C,
> > it is quite small (in perl).
> > However:
> > a) I cannot do C (and translating this is beyond me as a learning
> > exercise at the mo).
> > b) Also waiting is a good idea till all the bugs are sorted. (I am sure
> > there are more).
>
> I think it's right to turn things like this into C. I'll help you
> with it if you like, but I think you're right about waiting until the
> design is stable before doing it.
>
> If you can write Perl you can write C, there are onlya couple of dozen
> keywords. It's just that you're not so mollycoddled in C, you're much
> closer to the machine, and you have to plan further ahead (instead of
> waiting for the bang:). I prefer it.
Thank you Ged.
I have been meaning to learn C (along with lots of other things).
Any good books to recommend - I've got practicle C from O'Reilly - I
need something that is not too dry and manpage ish, but also not an
idiots guide as I can do perl (well I think I can).
I've been toying with the idea of C as this would push it out of the
mod_perl areana. The logic of it is quite simple. But for a beginer it
look all to complex. Plus there is the minor issue of time !
Thanks again for the offer of help, I may take you up on that.
Greg
> 73,
> Ged.
