[aspectc-user] =?iso-8859-2?Q?Re:=A0[aspectc-user]=A0Re:=A0[aspectc-user]=A0intercepting?= =?iso-8859-2?Q?=A0flow=A0of=A0executio=3D=3Fiso-8859-2=3FQ=3FRe:=A0[aspec?= =?iso-8859-2?Q?Re:�[aspectc-user]�Re:�[aspectc-user]�intercepting�flow �of�executio=?iso-8859-2?Q?Re:�[aspectc-user]?= =?iso-8859-2?Q?=A0intercepting=A0flow=A0of=A0execution=3DA0of=3F=3D=A0the?= =?iso-8859-2?Q?=A0method=A0declaredinside=A0aspect?=

Bartosz Blimke masb at chorwacja.com
Thu May 27 13:24:17 CEST 2004

> Our test cases show that cflow does not always fail under Windows.
> Therefore, I'm optimitic that the following workaround will help you:
> Move the implementation of your run() function from the aspect header
> into a *.cpp file which includes the aspect header explititly.
> aspect header:
> aspect Aspect {
>    void run(AC::Action &action);
>    ...
> };
> Aspect.cpp:
> void Aspect::run (AC::Action &action) {
>    action.trigger();
> }
> The local class will now be generated only in Aspect.cpp and the linker
> can't complain that it is defined twice.
> I hope that helps,
> Olaf

Ok, it works, but I had to declare run() as a global function
not the member of Aspect class.
If run() is a method of Aspect class ac++ weaver complains
that there is unknown token "Aspect" in run() definition in *.cpp file
void Aspect::run (AC::Action &action) {

Thanks for help, now I'm able to continue my solution,
and I'm waiting for fixing this bug with cflow :)


More information about the aspectc-user mailing list