Ignacio Morelle <[email protected]>:
> We are vulnerable anywhere where we don't coordinate our work or
> settle upon a common coding style, and a good *design style*. That's
> almost everywhere unfortunately, but I still can't find a good reason
> to blame C++.
You are mistaken if you think I am blaming C++ specifically in this
discussion. The defect attractors I am most worried about would be
just as severe in any attempt to do what Wesnoth does in *any*
language with pointers and fixed-extent types.
I can find plenty of things to curse C++ about, but that's
a different rant.
> And a language which does not offer data-type enforcement to me is
> just scaring, which is why it took me so long to learn Perl:
> unwillingness to surrender to type unsafety.
See my previous about "type safety" being a poor substitute
for explicit contracts and invariants.
> > The complex tangle of standard and local custom memory allocators we
> > presently use, and that are the source of so many of our bugs [...]
>
> Good example of non-coordination amongst developers. Um, why is C++,
> as a language, guilty?
Again, this is not a C++-specific problem. C, applied to a project
like Wesnoth, would probably produce a similarly nasty tangle.
Nor, in principle, would the solution need to be Python; in theory,
Ruby or Groovy or Guile would do just as well. Python is the tool
in thios class closest to hand.
> What are other *technical cons* on Python now? I have read a social
> one and an economical/hardware-resources one, but nothing else.
I'm hard put to think of any, really. Unless you think significant
whitespace is evil.
> I am
> also interested on what other free software projects using standard
> C++, rather than C or some non-standard dialect of any of the two, you
> work for. Or, if you practice writing C++ stand-alone applications to
> learn it, or you just stick to the first impression in Wesnoth.
I've done a little work on groff, which is written in C++.
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
_______________________________________________
Wesnoth-dev mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-dev
