After all, the guy has made it clear he intends to use a mid-sized 805x and not an ARM or some other larger architecture. Let's leave C++ out of the discussion, then, shall we?

After all, we're trying, though I'm not necessarily on board with this, generally speaking, to dissuade the O/P from doing work that's TBD with BASCOM, a dialect of BASIC in favor of using 'C' or PASCAL, ... his choice, not ours ... because we believe it will, over the long run, serve his needs much better to do so.

He does say he has the documentation for BASCOM, so, presumably, he can make the choice. I'd prefer not to "muddy the waters" with additional options that really don't apply to what he wants to do. The BASCOM with which I once was familiar ran under CP/M, taking genuine Microsoft Basic source as its input and generating suitable loadable/linkable executables as its output. I've really got no idea what the BASCOM for 805x can do, so my recommendations certainly are dated. I assure you, though, that 'C' is still taught in universities here, and is still widely recommended for PC and MCU applications. Moreover, since nearly every drunk on skid-row can program in 'C', thanks to its popularity, it's not hard to maintain software generated with it.

The lack of C++ garbage collection is not something with which PC programmers concern themselves. That probably accounts for the very large programs generated under C++.

BTW, how large is HELLO.C's executable these days?

RE