[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Port Subversion to Java

From: Scott Palmer <scott_at_digital-rapids.com>
Date: 2004-11-27 23:05:40 CET

On Nov 26, 2004, at 3:46 PM, Fewster, Robert wrote:

> C compiler support is more robust and stable on more platforms
> than JVM's are at this point in time. The promise of Java
> portability remains just that - a promise.

Having years of experience with C/C++ and Java I would have to say that
simply looking at the need to run ./configure shows that this statement
about C compiler "robustness" on multiple platforms is simply not true.

But that isn't the point of my post. I agree completely that it would
be a 100% waste of time to port Subversion to Java given that it is
already supported across the relevant platforms with the existing
project. Maybe if you were starting Subversion from scratch today Java
would be a reasonable choice. Java keeps getting better so today it
would be more attractive than it was when Subversion was started.
Perhaps if Subversion was started today it would use C++ instead of C.
I for one am surprised that anyone bother programming in straight C
anymore (I disagree with the arguments given for not doing Subversion
in C++). At the very least they could use C++ as a "better C".

All that doesn't matter NOW though. You have to look at what is
available now, and a C version of Subversion that is already ported is
available. There is no point in pretending that you are beginning all
over again.

On Nov 27, 2004, at 12:27 AM, Kevin Williams wrote:

> The Java developer's kit provides JNI as an accepted (stable?) means
> of accessing native code from within the VM. Native calls "un-managed
> in .NET" are looked upon as "the last resort". I'm reminded of the
> hiker who cut his arm off with a pocket knife to free himself from the
> boulder, only after spending days calling for help and trying to think
> of another way out. All Java developers I've talked to approach JNI
> the same way.

I disagree. In this case Subversion exists and so long at there are
JNI libraries for all the platforms on which the native Subversion code
runs then there is no issue for Java developers. The bindings are
there and you can use them as if they were any other Java library.
It's not like the JRE isn't full of native bindings so it can interact
with the host OS.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Nov 28 05:20:30 2004

This is an archived mail posted to the Subversion Users mailing list.