I'm pretty competent at basic c - at least my uni record shows good marks. The biggest issues I've found is that coding in the real world is different to my text books and assignments I had to do in content and the windows layer on top of everything wine does. For fixes I've done on other applications it seemed very straight forward to me though with wine you have to make sure your changes match the inputs and outputs expected by a list in msdn - it is more like filling in the blanks with a blind fold on (for a new coder) than another project where you just change any of the code you want to fix the issue. Jingo I'd say you really don't want to get much help with all of this. There is a very easy trap you can fall in to when learning c/cpp in that the simple tasks you are doing are easier for others to fix than for them to teach you why it is broken. This leads to you not really learning what is wrong or how to fix it. Believe it or not the five hours that you sit looking at some stupid simple issue will teach you more than the same amount of reading some book while you try and work through to find the solution. James what country are you in, I might be up for grabbing your copy of k & r, if you are close to australia email me with how much you want. Edward On Fri, Mar 14, 2008 at 6:01 PM, Alan McKinnon <alan.mckinnon@xxxxxxxxx> wrote: > On Friday 14 March 2008, James McKenzie wrote: > > > Alan McKinnon wrote: > > > On Thursday 13 March 2008, Edward Savage wrote: > > >> Thanks Dan for expanding K and Rs full names! I now know which > > >> book to look for. > > > > > > I shall now confuse you a little further. When you have finished > > > with the basics of K & R, you need to read the works of T. > > > > > > :-) > > > > Alan: > > > > Not fair! > > > > And there are FIVE books that T wrote, if it is the T I'm thinking > > about. > > Ken T? > > > > > -- > Alan McKinnon > alan dot mckinnon at gmail dot com > > >
