It's funny, that's more or less the solution my compatriot and I
discussed, and we might just go with that.
Thanks for all the help.
On 31-Oct-07, at 5:17 PM, Ron Bodkin wrote:
To modify the arguments, you could use a case study: write a version
for 1,
2, ..., n arguments along with using a declare error statement to flag
methods that had too many arguments for the finite number that you
enumerated.
It's not elegant but in 20 lines of code you can probably handle any
practical case.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris Rose
Sent: Wednesday, October 31, 2007 3:36 PM
To: [email protected]
Subject: Re: [aspectj-users] Modifying the parameters of methodswith
arbitrarysignatures
Okay, that's more or less what I thought.
Just as an aside, how safe is it to permit the modification of parts
of
the arguments that are not mutable? Suppose I want to change the
properties of some parameter in getArgs(), is that okay?
Eric Bodden wrote:
On 31/10/2007, Chris Rose <[EMAIL PROTECTED]> wrote:
That works for the purposes of getting them, but I need to feed them
back into the proceed call, don't I?
Hi Chris. AFAIK there is no way to do this in AspectJ. (it would be
very hard to get this working within the compiler)
Eric
--
Chris Rose
Developer Planet Consulting Group
(780) 577-8433
[EMAIL PROTECTED]
_______________________________________________
aspectj-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/aspectj-users
_______________________________________________
aspectj-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/aspectj-users
_______________________________________________
aspectj-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/aspectj-users
