harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Geir Magnusson Jr <g...@pobox.com>
Subject Re: awt and swing integration issues
Date Mon, 19 Jun 2006 11:48:25 GMT
My USD0.02...

1) If I were to write a GUI toolkit, I can't imagine why I wouldn't use
C++ given relationships like "DialogBox is a Window"

2) Isn't it a reasonably safe bet that any platform that has a GUI is
'advanced' enough to have a reasonable C++ compiler for it?

I understand the need to stick to the simplicity of C, but I'm not
surprised w/ the C++

Mark, are you suggesting we convert it back to C?


Alexey Petrenko wrote:
> 2006/6/18, Mark Hindess <mark.hindess@googlemail.com>:
>> On 18 June 2006 at 22:16, "Alexey Petrenko"
>> <alexey.a.petrenko@gmail.com> wrote:
>> > 2006/6/18, Mark Hindess <mark.hindess@googlemail.com>:
>> > > c) I'm also wondering about the motivation for using C++ when I can't
>> > > see any pressing reason to require this.
>> > You mean that most of the native code is C++ but not C?
>> Yes.  It seems to be a mixture of C and C++ and although I only looked
>> at a couple of files I didn't see anything that really needed C++
>> features.
>> For portability I'd stick to C if C++ isn't really required.
> But C++ gives at least 2 benefits for developer:
> 1. Strict type checking
> 2. It is allow to write env->FindClass("java/lang/Object") instead of
> (*env)->FindClass(env, "java/lang/Object") :)
> Windows version also uses GDI+ which is class library.
> So I vote for C++...

Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org

View raw message