Re: Solution for 5.0 language features in Eclipse(Re: And enum types (Re: API with generics))

2006-03-17 Thread Ashish Ranjan

 I'm looking forward to see this voting happeningif this compiler
 option is added into build system, it will introduce big convenience to
 current development and help to avoid mass repeating upgrade work to
 comply with Java 5 later (there are much in already).


+1 from me too.
I don't forsee any negative vote for this, atleast.

bye :-)
Ashish Ranjan
Scientist,CSIR,India
[EMAIL PROTECTED]
[EMAIL PROTECTED]


Re: Building choices (was: Re: Code contribution to harmony)

2005-11-23 Thread Ashish Ranjan
that is the most convincing argument till now.   :-)
bye :-)
Ashish Ranjan
India
[EMAIL PROTECTED]

On 11/23/05, Graeme Johnson [EMAIL PROTECTED] wrote:

 Tim Ellison [EMAIL PROTECTED] wrote on 11/21/2005 07:17:16 AM:

  Andrey Chernyshev wrote:
   On 11/15/05, Tim Ellison [EMAIL PROTECTED] wrote:
  
  In the end we decided to go with a 'conventional' native code tool set
  for the native source, and 'conventional' Java code tools for the Java
  source.  People just felt more comfortable with that.
  
  Do you think we are missing out on something ;-) ?
  
  
   Well, I can see a few potential issues with such mixed approach:
   - In order to contribute, people would have to learn both building
   technologies - Ant and make, someone may give up.
 
  I don't see a great advantage to asking people to learn 'cpptask' rather
  than 'make'.  I would suggest that many more C programmers are familiar
  with 'make' already, so we are not asking them to learn something new.
 
  [snip]

 'make' also simplifies the bootstrapping issue.  When you are doing the
 initial port of the VM to a new platform, and you don't have java
 running yet, having your build instructions encoded in Ant is problematic.

 Relying on the availability of a previous java port to get the Harmony
 VM building seems like a questionable porting story.  'make' of one flavor

 or another is pretty much universally available, and seems like the
 pragmatic choice for building C code.

 Graeme Johnson
 J9 VM Team, IBM Canada.



Re: compiling JCHEVM with MSVC

2005-11-20 Thread Ashish Ranjan
if you want to build native executables with gcc on ms-windows platform, i
will suggest to use MINGW (which is a gcc port to windows) and MSYS (which
is a gnuish environment for your build, so that your makefiles and automake
etc. will run). Hence goto www.mingw.org http://www.mingw.org and
download- mingw, msys, msys-DTK
and install it on MS-Windows and then give it a try. It will be easier to
try with/work with/port with/maintain with.
Just note that it is different from cygwin, which is an emulation layer.
bye :-)
Ashish Ranjan
India
[EMAIL PROTECTED]


On 11/20/05, Archie Cobbs [EMAIL PROTECTED] wrote:

 Enrico Migliore wrote:
  I'm compiling JCHEVM with MSVC.

 Hi Enrico,

 Unfortunately JCHEVM requires the GCC compiler right now.
 It would take some nontrivial work to port it to MSVC.
 Can you get access to a Linux or FreeBSD machine?

 In any case, this error:

 D:\projects\harmony-jcvm\jcvm\libjc\jc_invoke.c(81) : error C2059: syntax
 error : '['

 I believe is not a GCC-specific issue... that syntax is a C99
 extension to standard C (I believe).. for example:

 http://docs.sun.com/source/819-0494/c99.app.html#pgfId-1004206

 Cheers,
 -Archie

 __
 Archie Cobbs * CTO, Awarix * http://www.awarix.com