Re: Passing values between procedures(without actually passing them)
From: Shakespeare <whatsin_at_xs4all.nl>
Date: Fri, 29 Jan 2010 15:55:57 +0100
Message-ID: <4b62f6ed$0$22934$e4fe514c_at_news.xs4all.nl>
Op 29-1-2010 14:09, LPF schreef:
> It's possible to achieve something like this?
>
> Procedure1(param1,param2) IS
> ...
> begin
> Procedure2;
> end Procedure1;
>
> Procedure2 IS
> ....
> begin
> --Know the parameters values of Procedure1 at this point(with
> dbms_debug, dbms_trace, some V$, ....)
> end Procedure2;
>
> The point to this is that i have a lot of procedures(like Procedure1)
> calling a Procedure(Procedure2).
> So if this could be achieved, i only have to use a simple line like
> "Procedure2;" to all procedures(and with the advantage of not being
> dependent of the number of parameteres, so future changes wouldn't
> affect the Procedure2 call).
>
> Thx in advance.
Date: Fri, 29 Jan 2010 15:55:57 +0100
Message-ID: <4b62f6ed$0$22934$e4fe514c_at_news.xs4all.nl>
Op 29-1-2010 14:09, LPF schreef:
> It's possible to achieve something like this?
>
> Procedure1(param1,param2) IS
> ...
> begin
> Procedure2;
> end Procedure1;
>
> Procedure2 IS
> ....
> begin
> --Know the parameters values of Procedure1 at this point(with
> dbms_debug, dbms_trace, some V$, ....)
> end Procedure2;
>
> The point to this is that i have a lot of procedures(like Procedure1)
> calling a Procedure(Procedure2).
> So if this could be achieved, i only have to use a simple line like
> "Procedure2;" to all procedures(and with the advantage of not being
> dependent of the number of parameteres, so future changes wouldn't
> affect the Procedure2 call).
>
> Thx in advance.
With this approach, you're on the highway to hell.
Shakespeare Received on Fri Jan 29 2010 - 08:55:57 CST