:
> ilejn writes:
> > Arnaud,
>
> > these lists are not generated.
>
> > Actually these lists are a sort of interpreted programs and contain
> > some application logic.
>
> > Here is an example
> > [
> > [PUSH, [
_interface, '']],
[PULL, [out_mined_interface, req]],
]
If any interface name is unknown the list must not be invoked (in
other words, f function
call with this list must be somehow bypassed).
Thanks.
On Jan 20, 11:42 pm, Arnaud Delobelle wrote:
> ilejn writes:
is ;)
Thanks anyway.
On Jan 20, 10:58 pm, Arnaud Delobelle wrote:
> ilejn writes:
> > Hello!
>
> > I have a sequence of a function calls. Basically it looks like
>
> > f(arg1)
> > f(arg2)
> > ...
> > f(argN)
>
> > though real arguments are c
.
Thanks.
On Jan 20, 9:58 pm, Chris Rebert wrote:
> On Thu, Jan 20, 2011 at 9:32 AM, ilejn wrote:
> > Hello!
>
> > I have a sequence of a function calls. Basically it looks like
>
> > f(arg1)
> Why aren't they known? It's a very bad code smell to have p
Hello!
I have a sequence of a function calls. Basically it looks like
f(arg1)
f(arg2)
...
f(argN)
though real arguments are complex multilayer lists.
The problem is some arguments are not known and I get NameError
exceptions.
The solutions I know
1. wrap every f call in try/except block
2. mak
