Eventually, do you maybe still have the code by curiosity to have a look at the code?

--
Pub.Msg @dugan: look the book that I just found

Several versions and ports here.

http://www.ifarchive.org/indexes/if-...esXsource.html

Your link is really amazing. There are lot of things on it.

Rule #11:

Don't flood programmer's forum threads with off-topics..

Sometimes, programming make no sense maybe? Only on Monday we should programme.


Here it is a good example that programmes that do not offer a good compatibility, portability and which can be built without too much changes will remain.

xfmail is a good example. "Mark broken: does not build"
https://www.freshports.org/mail/xfmail
If maintainers cannot compile the application/software without too much changes, it'll stay otherwise a good programme can disappear forever. Because libraries are changing faster than the development of software, it is likely that a programme will not find always maintenance. Is it good? Mature programmers will say that of course possible maintenance/compilation has some importance.

Yes, but it is also an example of a program that followed all your rules.

What does that say about your rules?

Not that working always.

It depends on the goals, project, funding, and operating system.
We can still compile very old programmes on old operating systems. On Unix, it is more difficult.

You must love the SystemD team.

GnuCOBOL also converts into C.

Hmm...

One rule that I have not seen in the discussion:

Aggregation is better than Inheritance.

I first learned it from one of my bosses. There are design-patterns which make use of the rule; the best implementation that I have seen was a complex state machine, organized as a tree structure with branches, leafs AND states implementing the same Interface, each being a composite of an arbitrary number of ... branches, leafs and states.

A filter/pipeline pattern was introduced by a second interface.

You provide a 1-liner C-macro to define your template-classes at compile-time and let the code explode. Impossible with Inheritance.

Nowadays with Ruby, there is anyway not much to win by deriving classes.