Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.forth Subject: Re: esp8266 eForth and it's development software Date: Tue, 07 Mar 2017 20:39:38 -0800 Organization: A noiseless patient Spider Lines: 20 Message-ID: <87fuiocrg5.fsf@nightsong.com> References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="8d8921c284f2509425895148d84e66d3"; logging-data="6924"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18ytCwzgYOsp4cUgwcEuLcn" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:l4pGHWF6/ucDD3NpMLiexgE4gtg= sha1:gGLvP/2/T61dssYq6ck4E+t0z+8= Xref: csiph.com comp.lang.forth:55521 Cecil Bayona writes: > So tomorrow I will need to do some reading on C++ classes so I can > create the missing items, dummies at first so I can find the other > errors, then go back and flesh them out. Oh what fun. C++ is a lot different (better) now than it was 20 years ago. C++11 was a huge change. You might read a recent book that covers it. I like "Effective Modern C++" by Scott Mayer. This might also be of interest: https://isocpp.org/blog/2015/09/bjarne-stroustrup-announces-cpp-core-guidelines > Actually it would be easier to convert the code to plain C without > classes and it would be more portable at that. All of this is for the > sake of having a version of eForth on C++ or C so it can be migrated > somewhat easier. What a can of worms I have on my hands. Why is eForth in C so interesting or important? I thought the great thing about eForth was that it was written in Forth, and in a very simple way. But it's not all that useful a Forth. If you want a Forth in C, why not one of the many others that are out there?