Quote:Original post by jollyjeffersQuote:Despite the fact that I frequently curse it (Daily at work in fact)There's something very familiar sounding about that [wink]. My current project is related to writing some new language editors as eclipse-3 plugins...
Eclipse, at least for Java, has a lot of very powerful features given that it's free/open-source. You've got decent debugging (comparable to VStudio imo), decent build management (Using ANT) and code-refactoring support built in.Quote:edit the desktop icon to Eclipse and allocate the JVM some more memory if you want tolerable speedsGot any more info on this? sounds interesting... my work machine has 1gb RAM - would happily allocate more to eclipse if it'll make it happier!
Cheers,
Jack
Sure. I assume you're using Windows.
Go to your desktop icon for Eclipse, right click and select "properties" then select the shortcut tab and where it says target write something like:
C:\Java\eclipse\eclipse.exe -vm C:\Java\j2sdk1.4.2\bin\javaw.exe -vmargs -Xmx512M
The first path is the path to the eclipse executable, which should already be there, the second is the explicit path to your JVM and the two arguments allocate 512 MB of RAM to the JVM when running Eclipse. I wouldnt go above that, merely because with lots of RAM - instead of dead object refs getting garbage collected- they will get swapped out on to disk and stored instead, which means garbage collection will take even longer when it does run, as it has to fetch a load of pages with dead object refs from disk.
Jon
