Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [aspectj-users] Extend type patterns by qualifiers like public, interface etc.

I know you will hate me for saying this :) Take a look in the read me for 1.6.9: https://eclipse.org/aspectj/doc/released/README-169.html

"Type category type patterns"

execution(* (!is(InnerType)).m(..)) {}
!within(* && is(InnerType)) {}

Options for use in is() are: ClassType, AspectType, InterfaceType, InnerType, AnonymousType, EnumType.

I just had a look and there don't seem to be a mountain of test cases for it so you might have to try it in your code and see what happens, I'll certainly take a bug if it is misbehaving.

cheers,
Andy 


On 27 August 2014 07:04, Alexander Kriegisch <alexander@xxxxxxxxxxxxxx> wrote:
Hi there (especially Andy Clement).

Before creating a Bugzilla ticket I wanted to get some developer feedback or hints to features I might have overlooked.

In type patterns (used as part of method signatures, in pertypewithing clauses or in declare parent statements) I generally miss the option to limit the pattern like this:

!interface com.foo..*
public enum foo.bar.Zot

For instance, I guess often it makes sense to exclude interfaces from ITD type patterns when declaring something like "implements Baz".

Is anything like this possible (I don't think so)? Planned? Generally a good idea with a chance of implementation? If so, should I create a ticket for it? I do not want to bloat the ticket list by something without a realistic chance of implementation.

Regards
--
Alexander Kriegisch
http://scrum-master.de

_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/aspectj-users


Back to the top