C++, just C++, is a recipe for trouble. Most projects that use it define a subset to make development a less painfull talk. Usually operator overloading, templates and virtual inheritance are discarded.
Rodrigo On 5/17/05, Ben Laurie <[EMAIL PROTECTED]> wrote: > > Jónas Tryggvi Jóhannsson wrote: > > > >> Question to the floor: if it had to be one of C and C++, which would > >> you prefer? > > > > > > I can´t think of a single reason why C should be preferred over C++, > as > > C can simply be viewed as a subset of C++. > > That sounds like a reason to me. > > > As Java users, all of us > > appreciate object orientation and understand how it can be used to > > simplify software and make it more readable. Writing C code in an object > > oriented manner simply does not give the same level of abstraction C++ > > can provide. > > I agree. Many developers don't. > > > Im however very fond of the idea of writing the JVM in Java. Im > > beginning to look into the JikesRVM and I really like the idea, > > especially as it is the language that everyone on this list is familiar > > with. > > As I said before, don't assume we're all Java fans here. I'm far more > familiar with C++ than I am with Java. > > > It would also maximize the quality of the tools that we will > > provide, as we would be using them to develop our JVM. > > Like I said, a framework that allows you to do this is definitely what I > want to see. But it should also allow me to write the JVM in C. > > Is the Jikes licence one we can use? > > Cheers, > > Ben. > > -- > http://www.apache-ssl.org/ben.html http://www.thebunker.net/ > > "There is no limit to what a man can do or how far he can go if he > doesn't mind who gets the credit." - Robert Woodruff >
