Complete.Org: Mailing Lists: Archives: freeciv-dev: April 2000:
[Freeciv-Dev] Re: #define $#@$%! template

[Freeciv-Dev] Re: #define $#@$%! template

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: freeciv-dev@xxxxxxxxxxx
Subject: [Freeciv-Dev] Re: #define $#@$%! template
From: "Michael H. Price II" <price@xxxxxxxxxxx>
Date: Wed, 26 Apr 2000 21:05:10 -0500

On Thu, Apr 27, 2000 at 01:00:29AM +0200, Tomasz Wegrzanowski wrote:
> > I'm open to discussion.
> And cons are :
> - less people know c++ that c

If you continue that argument to its logical conclusion then no new
language would ever be developed. There is a learning curve associated
with any new product. Using it as an excuse not to learn is just silly.

> - c++ compiles much slower

If you limit yourself to one object (or group of very closely related
objects) per source file then you will be hard pressed to notice any
decrease in speed versus a C compiler.

> - c++ compiler makes worse code

People write worse code because they don't know the language as well
as they think they do. Write proper C++ code and you will get very
good code from any modern compiler. I challenge you to provide an
example supporting your claim.

> Is there any TODO item that would be much easier if switched c -> c++ ???

C++ isn't intended as a language to make things "easier". It is
intended as a language that more easily supports an OOA/OOD. While you
can used OOA and OOD techniques with any language, they are easier
with C++.

C++ is not a language for every purpose. Neither is C. They each have
their strengths and weaknesses. You can write crappy programs in
either language. You can write works of art in either as well.

I would only recommend switching languages if it becomes clear that
the languages strengths coincide with the design techniques used by
the project developers.

Just my $.02


[Prev in Thread] Current Thread [Next in Thread]