[A discussion that has been going on the e-lang list has moved here to eros-port, where it probably should have been all along. Those who missed the earlier parts of the discussion can check out the online e-lang archive by following the link from http://www.eros-os.org/~majordomo. ]
> One of the trickier parts of installing EROS for me was getting Python
> installed. Not sure I agree about C++, though. You are bound to have
> strong toolchain dependencies anyway for building EROS (aren't you??),
> so adding C++ to that doesn't seem bad to me, especially since it is
> fairly universally available.
I think the comment about getting python running illustrates the point I've been trying to make. Particularly where a cross-build environment is involved, you really want to rely on the smallest tool set possible.
As to C++, it's overlap with C is large enough that they mostly involve the same run time so long as you avoid the standard C++ library. However, C++ isn't adding value, and removing it from the tool chain reduces the temptation to start depending on something unintentionally.