Crossfire Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: From c to c++
- To: ,
- Subject: Re: From c to c++
- From: Michael Walker <>
- Date: Wed, 06 Dec 1995 12:43:37 -0800
- Cc: crossfire (at) ifi.uio.no
- In-Reply-To: Your message of "Wed, 06 Dec 1995 21:56:21 +0200." <>
Just a thought on my part for someone who's just a lurker on this
alias. But if y'all are considering a complete re-write have you
thought about coding it in Java.
Some of the advantages of Java would be:
o binaries are machine independent. You will instantly be able
to run the client's all the machines that have the java
virtual machine on it. Which currently includes many unix's
Win95/NT and soon Mac too.
o Object oriented languages very simular to C++
o Might win *big* prizes...
I think that if crossfire were ported to JAVA it would ba a great
candidate for the Java contest that Sun is currently running. For
more info on Java and the contest start take a look
at http://javacontest.sun.com.
I'm only bummed because I'm a Sun employee I'm not uneligible for
the contest.
It's a thought and it might be a lot of fun.
_Mike_
=> On Wed, 6 Dec 1995, W.E.B wrote:
=>
=> > I'm working with a group of students here at the University of
=> > Nevada Reno who'd like to port crossfire to c++. I realize it's under the
=> > GNU license but would like to hear from some of the people working on it.
=> >
=> > If this becomes a reality it would be an upper divisional class in
=> > porting using crossfire as an example. With any luck, the class would
=> > first abstract the code into some general classes and then address the
=> > issues of static versus dynamic code. There are plenty of topics which
=> > crossfire implements and is an excellent model to be divided up. Hopefully
=> > the system would be easier to expand and maintain if we were to do a job
=> > well done.
=> >
=> > If you have some ideas/suggestions we'd be very pleased to hear them.
=>
=> * first task is to get a base on c++, meaning the code can
=> be compiled with c++-complier. It's quite straightforward
=> work thanks to ansi-c. And then get development package out.
=>
=> * the set of c++ features should be decided, most complilers
=> provides templates, but exception handling is still uncomplete
=> in many compilers eg. g++-2.7.2 and what libraries to use;
=> STL is nice and available with libg++, but how other development
=> environments.
=>
=> * instead of full rewriting (unless you feel you have unlimited amount
=> of energy :) I suggest increamental modification, for example
=> considering the object/monster structure and using still same
=> user interface.
=>
=> <A HREF="http://www.lut.fi/~hevi/"></A>
=>
--
Mike Walker