| I confess: When I was writing C, K&R was the standard! Good to see that now there are better versions of C with more detailed documentation. The last time I had to write some C, I just refreshed my C 'skills' with K&R and reading some of my old code. For your "You seems to have found some that works well for your needs so everything is good." I agree: I looked at Java early on and didn't like it. From some of the comments and links here at HN, I see that Java has made progress since then. Indeed, some of what I like in Visual Basic .NET (I say ".NET" because there is an
earlier version of Visual Basic that is quite different and
less 'advanced') seems to have come from Java. So, now I'm glad to have the progress of Java and/or Visual Basic .NET and will return to C only when necessary. Actually, the last time I worked with C, I wrote only a few lines of it! Instead, I took some Fortran code, washed it through the famous Bell Labs program f2c (apparently abbreviates 'Fortran to C') to translate to C,
slightly tweaked the C, compiled it into a DLL, and now call it from Visual Basic .NET. Maybe what will be waiting
for me in the lower reaches is C programming on an
early version of Unix without virtual memory and without
a good text editor on a slow time sharing computer
using a B/W character terminal, 24 x 80! |