David White <[email protected]>:
> The fact is though that almost ALL programs -- closed or open source --
> that are anything like Wesnoth: that is, complex client-side game
> projects with sophisticated interfaces are written using languages with
> pointers and fixed-extent types.
Yes, which is a major reason so many of these programs are buggy and fragile.
> I personally tend to be of the view that for a project like Wesnoth,
> using dynamic typing extensively will be much more problematic. I am not
> sure of any programs that are large (i.e. teams of 5+ coders, developed
> over years) and have GUI's that are written in any dynamically typed
> languages, but I would enjoy hearing of them if anyone has any examples.
Here's an indisputably real-world example: AutoCAD. Most of it is written
in a customized LISP; the C part is the LISP interpreter core.
> I'd also like to point out that contrary to what was said in a previous
> email, we don't use a variety of memory allocators.
Oh, but you do. Every STL and Boost container class, for starters.
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
_______________________________________________
Wesnoth-dev mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-dev
