- About Scala
- Documentation
- Code Examples
- Software
- Scala Developers
Re: Eclipse plugin health?
Wed, 2008-12-17, 20:27
On Wed, Dec 17, 2008 at 7:16 PM, Chris Twiner wrote:
> just to clarify, as an Xmas present the plugin should get another leap
> in functionality? Please drop an email on scala-tools and let us know
> when its out. I for one would love to help testing that out.
Thanks for the offer and the encouragement :-)
Probably the only thing you'll notice immediately is that the
occasional duplication of Scala files with Java file in the package
explorer when you move or rename things will have gone away. But this
is an enabling feature which will mean thing will be able to move
forward much more rapidly ...
Cheers,
Miles
Wed, 2008-12-17, 21:07
#2
Re: Eclipse plugin health?
On Wed, Dec 17, 2008 at 7:37 PM, Naftoli Gugenheim wrote:
> Other bugs are: The outline doesn't jump you to the right place in some
> cases (I have to double check exactly when - if it's in project source files
> or library looked up source code).
You should find most of those fixed in 2.7.3. Trac tickets for the
ones which aren't would be much appreciated :-)
Cheers,
Miles
Other bugs are: The outline doesn't jump you to the right place in some cases (I have to double check exactly when - if it's in project source files or library looked up source code).
Also I think Autocomplete should show local variables before classes. Also if there's a class with the same name as local variable but with different case I think selecting the variable (which is later in the list) inserts the class name.
Also is the discussion about memory leaks in actors relevant to the plugin? Because I'm pretty sure there is memory leak. When I first open Eclipse with my project open, it uses ~45Mb of RAM, and if I leave Eclipse open for too long (a day?) without restarting it will climb all the way to my current maximum of 256Mb -- gradually. I can't guarantee that the memory jumps only resulting from a compile, but that's definitely the most obvious time. Also, I noticed that even after memory usage peaked, if I closed the Scala perspective (the only one that was open) most of the memory was freed, so that when it was reopened it was only a small amount more than it had started with. So it seems like there must be a lot of stuff that's being held back from being garbage collected by references in the perspective data structures (actually I can't remember if the project was open during closing/reopening the perspective; it probably wasn't; but closing and reopening the project didn't achieve that effect).
(I work on a computer that's not connected to the internet so I have plenty of time to forget the details of bugs. If these bugs are not known issues I can try to reenact them to get more details if need be.)
Thanks!