This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Stack size
- From: Jonathan Olson <olson at mmsi dot com>
- To: tromey at redhat dot com
- Cc: "Steen Jansdal" <steen at jansdal dot dk>, <java at gcc dot gnu dot org>
- Date: Thu, 6 Dec 2001 08:26:22 -0700
- Subject: Re: Stack size
My personal experience with Java in an embedded environment is
that pure C++ code is much easier to debug and maintain than Java which
becomes a mix of Java, C++, and C. Debugging mixes of Java and
native code is difficult and having a mixed development environment
forces programmers to be fluent in multiple languages and environments.
If your goal is to reuse alot of existing Java code on an embedded
target
than the gains are often worth the pain. If you're writing most of the
code
from scratch, you're better off using C++.
On Thursday, December 6, 2001, at 08:24 AM, Tom Tromey wrote:
>>>>>> "Steen" == Steen Jansdal <steen@jansdal.dk> writes:
>
> Steen> The reason I'm asking this is that I'm trying to evaluate if
> Linux
> Steen> on a x86 is going to be the platform for our next embedded
> Steen> device. The memory on this device are limited to 16 or 32 Mb.
> Steen> The programs for this device are going to heavy multithreaded,
> Steen> and consist of a web-server, a soap-server and several user
> Steen> programs. It is my highest wish that we can use java as our
> Steen> language. C++ is too difficult to maintain.
>
> Steen> Any advices for my evaluation are much appreciated.
>
> With gcj you're always free to hack the library to do whatever you
> like. You could even add a Java API to control the stack size on a
> per-thread basis.
>
> Tom