Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #55505
| From | Cecil Bayona <cbayona@cbayona.com> |
|---|---|
| Newsgroups | comp.lang.forth |
| Subject | Re: esp8266 eForth and it's development software |
| Date | 2017-03-07 10:39 -0600 |
| Organization | A noiseless patient Spider |
| Message-ID | <o9mnit$g1b$1@dont-email.me> (permalink) |
| References | (5 earlier) <o9gc5e$4e1$1@dont-email.me> <af081ca2-0068-43a1-8dd1-fff96b129670@googlegroups.com> <o9k9jm$ian$1@dont-email.me> <20170306175713.65d8a6a7@_> <893d7a04-cde5-4ca2-9d7d-5c3e95172e94@googlegroups.com> |
On 3/7/2017 3:23 AM, Mark Wills wrote: > On Monday, 6 March 2017 22:56:22 UTC, Rod Pemberton wrote: >> On Mon, 6 Mar 2017 12:28:46 -0600 >> Cecil Bayona <cbayona@cbayona.com> wrote: >> >>> On 3/6/2017 3:45 AM, Mark Wills wrote: >> >>> I just had a good laugh, I looked through my bookshelf to see what >>> books I have on C programming, one book, Kernighan and Ritchie's "The >>> C Programming Language". I have tons of books on various programming >>> subjects such as data structures, sorting, and other programming task >>> but they are not C books Other books on languages such as MatLab, >>> Delphi, Prolog, .Net Languages such as C#, VB.NET, PHP, and other >>> languages including Forth, but one book on C, "The Book" on C, the >>> language reference by the creators of C. >>> >>> It says something about C, how simple it is, that one book was all I >>> felt I ever needed. But the language is a bear when you have pointer >>> errors because anything is basically allowed, now you have lint to >>> find unassigned pointers and such. >> >> I beg to differ. "THE Book" on C is *NOT* Kernighan and Ritchie's "The >> C Programming Language." That's only an introduction to C. Far and >> away the absolute best book on C that exists is "C: A Reference Manual" >> by Samuel P. Harbison and Guy L. Steele, Jr. of Tartan Laboratories. >> It's truly the only book on C you'll ever need. Another good book is >> "The Standard C Library" by P.J. Plauger. These are the only two books >> in my library of C books that were worth the money. They are the only >> two that I've consistently used for a few decades now. If you ask on >> comp.lang.c, they'll tell you that you need "C Unleashed" since a bunch >> of the people who posted to the Usenet group circa year 2000 wrote it, >> such as Richard Heathfield, Lawrence Kirby, and something like 15 >> others. Personally, I wouldn't suggest anyone spend money on this book >> either. >> >> >> Rod Pemberton >> -- >> All it takes for humanity to conquer the world's toughest problems >> is to hope, to believe, to share, and to do, in cooperation. > > Yes. I found the K&R book too terse when I read it (very early 90s). I was just > learning C, there was no internet (that I or anyone I knew had access to) > and I was pretty much on my own. In those days you went to the library to > find stuff out. > > It kind of left me with a bad feeling when it comes to C. That and some > horrifically complicated C code that I once got involved with > that was written by a black-belt ninja C guru type bloke. We would pontificate > if he deliberately wrote obtuse C code when he wasn't in the room. It was > was really hard to follow, and he was an obnoxious bastard. Everyone was > afraid to ask him anything for fear of ridicule. It the was pointer syntax > that I always struggled with in C. Everything else seemed quite nice. > Simple pointers are okay, pointers to structs etc, yeah I was okay with that. It was when you started to get into double indirection (pointers to pointers) that it got tricky! > My first experience with C was to write my own version of a C compiler, a difficult thing when you don't have a working C compiler, the initial code was written in PL/M and once enough of it started working translate that to C and self compile from then on. Quite a convoluted project, but I was young and had lots of energy, I also had AMD floating point chip to do floating point eventually. I was a recursive decent compiler and was pretty complete a couple of years later including a peephole optimizer, I wish I had kept the source. Much later Borland came up with a decent C compiler and that pretty much stopped further development on it. I bought two more books to round out the library a hardbound copy of "C: A Reference Manual" and Plauger's Library book as an eBook. That is it for now, one hardbound book and eleven eBooks with about half no on C but on programming subjects, twelve books for around $70 shortly I will do the same for C++ but not on such a large scale maybe two to four books, I never have been a great fan of C++. At the time I looked at it it was hard to read compared to C and it generated not so fast code with it's emphasis on object oriented code. I started creating a project to convert the eForth Arduino based VM to C, lots of errors but I had to quit as major storms were moving in with heavy thunderstorms and a Tornado Watch in effect. -- Cecil - k5nwa
Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
esp8266 eForth and it's development software Cecil Bayona <cbayona@cbayona.com> - 2017-03-01 15:18 -0600
Re: esp8266 eForth and it's development software David Schultz <abuse@127.0.0.1> - 2017-03-01 15:29 -0600
Re: esp8266 eForth and it's development software Cecil Bayona <cbayona@cbayona.com> - 2017-03-01 17:16 -0600
Re: esp8266 eForth and it's development software David Schultz <abuse@127.0.0.1> - 2017-03-01 17:51 -0600
Re: esp8266 eForth and it's development software Cecil Bayona <cbayona@cbayona.com> - 2017-03-01 18:36 -0600
Re: esp8266 eForth and it's development software Paul Rubin <no.email@nospam.invalid> - 2017-03-01 16:53 -0800
Re: esp8266 eForth and it's development software Cecil Bayona <cbayona@cbayona.com> - 2017-03-01 19:28 -0600
Re: esp8266 eForth and it's development software Paul Rubin <no.email@nospam.invalid> - 2017-03-01 17:56 -0800
Re: esp8266 eForth and it's development software Cecil Bayona <cbayona@cbayona.com> - 2017-03-01 20:53 -0600
Re: esp8266 eForth and it's development software Paul Rubin <no.email@nospam.invalid> - 2017-03-01 18:57 -0800
Re: esp8266 eForth and it's development software Cecil Bayona <cbayona@cbayona.com> - 2017-03-01 21:17 -0600
Re: esp8266 eForth and it's development software David Schultz <abuse@127.0.0.1> - 2017-03-01 21:38 -0600
Re: esp8266 eForth and it's development software Cecil Bayona <cbayona@cbayona.com> - 2017-03-01 22:02 -0600
Re: esp8266 eForth and it's development software Paul Rubin <no.email@nospam.invalid> - 2017-03-01 19:40 -0800
Re: esp8266 eForth and it's development software Cecil Bayona <cbayona@cbayona.com> - 2017-03-01 22:44 -0600
Re: esp8266 eForth and it's development software Paul Rubin <no.email@nospam.invalid> - 2017-03-01 14:50 -0800
Re: esp8266 eForth and it's development software Cecil Bayona <cbayona@cbayona.com> - 2017-03-01 17:26 -0600
Re: esp8266 eForth and it's development software Paul Rubin <no.email@nospam.invalid> - 2017-03-01 15:41 -0800
Re: esp8266 eForth and it's development software Cecil Bayona <cbayona@cbayona.com> - 2017-03-01 18:10 -0600
Re: esp8266 eForth and it's development software Cecil Bayona <cbayona@cbayona.com> - 2017-03-04 20:50 -0600
Re: esp8266 eForth and it's development software Paul Rubin <no.email@nospam.invalid> - 2017-03-04 20:10 -0800
Re: esp8266 eForth and it's development software Cecil Bayona <cbayona@cbayona.com> - 2017-03-04 23:06 -0600
Re: esp8266 eForth and it's development software Paul Rubin <no.email@nospam.invalid> - 2017-03-04 21:25 -0800
Re: esp8266 eForth and it's development software Cecil Bayona <cbayona@cbayona.com> - 2017-03-05 00:47 -0600
Re: esp8266 eForth and it's development software Paul Rubin <no.email@nospam.invalid> - 2017-03-05 01:36 -0800
Re: esp8266 eForth and it's development software Cecil Bayona <cbayona@cbayona.com> - 2017-03-05 17:11 -0600
Re: esp8266 eForth and it's development software Cecil Bayona <cbayona@cbayona.com> - 2017-03-05 15:43 -0600
Re: esp8266 eForth and it's development software Mark Wills <markwills1970@gmail.com> - 2017-03-06 01:45 -0800
Re: esp8266 eForth and it's development software Cecil Bayona <cbayona@cbayona.com> - 2017-03-06 10:44 -0600
Re: esp8266 eForth and it's development software Cecil Bayona <cbayona@cbayona.com> - 2017-03-06 12:28 -0600
Re: esp8266 eForth and it's development software Cecil Bayona <cbayona@cbayona.com> - 2017-03-06 16:00 -0600
Re: esp8266 eForth and it's development software Rod Pemberton <NeedNotReplyHere@xrsevnneqk.cem> - 2017-03-06 17:57 -0500
Re: esp8266 eForth and it's development software Mark Wills <markwills1970@gmail.com> - 2017-03-07 01:23 -0800
Re: esp8266 eForth and it's development software albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-03-07 12:32 +0100
Re: esp8266 eForth and it's development software Cecil Bayona <cbayona@cbayona.com> - 2017-03-07 10:39 -0600
Re: esp8266 eForth and it's development software albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-03-06 13:35 +0100
Re: esp8266 eForth and it's development software Cecil Bayona <cbayona@cbayona.com> - 2017-03-06 10:51 -0600
Re: esp8266 eForth and it's development software Cecil Bayona <cbayona@cbayona.com> - 2017-03-07 22:33 -0600
Re: esp8266 eForth and it's development software Paul Rubin <no.email@nospam.invalid> - 2017-03-07 20:39 -0800
Re: esp8266 eForth and it's development software Cecil Bayona <cbayona@cbayona.com> - 2017-03-07 23:42 -0600
Re: esp8266 eForth and it's development software Paul Rubin <no.email@nospam.invalid> - 2017-03-07 23:44 -0800
Re: esp8266 eForth and it's development software Cecil Bayona <cbayona@cbayona.com> - 2017-03-08 11:03 -0600
Re: esp8266 eForth and it's development software albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-03-08 12:05 +0100
Re: esp8266 eForth and it's development software anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-03-06 17:09 +0000
Re: esp8266 eForth and it's development software albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-03-07 12:52 +0100
csiph-web