orks fine in
> 3.6) - hence the difference.
>
> Andy
>
> On 28 January 2011 06:53, Emond Papegaaij
wrote:
> > Hi all,
> >
> > Starting with Eclipse 3.6, the Eclipse compiler no longer suppresses raw
> > type warnings with @SuppressWarnings("unchecked&
Hi all,
Starting with Eclipse 3.6, the Eclipse compiler no longer suppresses raw type
warnings with @SuppressWarnings("unchecked"). You need to use
@SuppressWarnings("rawtypes") for that. Is it possible to change this in the
AspectJ compiler as well?
At our company, we have several libraries s
Hi Andy,
Did you make any additional improvements lately? Last time, you were a bit
supprised that type demotion did not reduce the memory usage by as much as you
expected it to do. I haven't tried AJDT since then, because with the memory
usage at that time, Eclipse is not very usable on my lap
if they were, I
should have seen a compile error). Is there any way I can see why these types
are kept in the tMap?
Best regards,
Emond Papegaaij
___
aspectj-users mailing list
aspectj-users@eclipse.org
https://dev.eclipse.org/mailman/listinfo/aspectj-users
On Friday 06 August 2010 18:20:01 Andy Clement wrote:
> Thanks for the feedback!
>
> On 6 August 2010 00:29, Emond Papegaaij wrote:
> > Memory usage is down a bit (I'd say about 20%, compared to just
> > minimalModel=true). The largest AjState object went down from 2
j.weaver.ReferenceType.isAssignableFrom(ReferenceType.java:399)
etc.
Unfortunately, I can't dive into this deeper now and won't have time to test
this the next couple of weeks, but I'll check back on this in september.
Good luck with this, it seems you're on the right path. Wit
On Tuesday 20 July 2010 17:04:36 Andy Clement wrote:
> On 19 July 2010 23:48, Emond Papegaaij wrote:
> > I wonder, what does the AspectJ compiler need all that information for?
> > Currently, it seems it stores a complete representation of the classes in
> > the t
On Monday 19 July 2010 17:44:54 Andy Clement wrote:
> On 19 July 2010 02:10, Emond Papegaaij wrote:
> > Hi,
> >
> > I've upgraded to the latests snapshot, and enabled the option. Memory
> > usage went down quite a bit, I'd say about 300M. The AjState object I
e feedback I may make it the default.
>
> The world typemap will only shrink when type demotion is implemented
> for compile time weaving. This is a harder problem but I think I know
> a viable solution - it is just finding the time to implement it.
>
> cheers,
> Andy
>
>
build takes several
minutes.
> > I hope this helps. If you need more information, please let me know.
>
> It does, thanks. I'll let you know when a dev build of AJDT includes
> something to try out.
Great, I'll give it a try when you say so.
Best regards,
Emond Pape
ments. The memory usage stayed about the same.
I hope this helps. If you need more information, please let me know.
Best regards,
Emond Papegaaij
On Tuesday 13 July 2010 19:14:37 Andy Clement wrote:
> Hi,
>
> I've been exploring some memory shrinking options under
> ht
h the latest AJDT development build
(2.1.1.e35x-20100712-1300) with AspectJ 1.6.10.2010071213.
Is there any way we can reduce this memory usage? I tried disabling
incremental building and disabling the weaving service, but that didn't help.
Best regards,
Emond
12 matches
Mail list logo
