[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Avoid global pointers in dae
From: |
Carlo De Falco |
Subject: |
Re: Avoid global pointers in dae |
Date: |
Mon, 15 Aug 2016 16:27:48 +0000 |
On 15 Aug 2016, at 12:42, Francesco Faccio <address@hidden> wrote:
> This is nice, but I can't write methods that compute residual inside my
> class. I need to call method do_multi_index_op or feval, which are defined in
> libinterp. That's why I dereference pointres to call function defined in [1]
> line 72.
I don't understand why not.
Can't you create a method that calls feval internally,
and pass a pointer to it with the standard technique shown
in the previous email?
Why?
c.
- Avoid global pointers in dae, Francesco Faccio, 2016/08/13
- Re: Avoid global pointers in dae, Carnë Draug, 2016/08/13
- Re: Avoid global pointers in dae, Carlo De Falco, 2016/08/13
- Re: Avoid global pointers in dae, Carlo De Falco, 2016/08/13
- Re: Avoid global pointers in dae, Francesco Faccio, 2016/08/15
- Re: Avoid global pointers in dae, Carlo De Falco, 2016/08/15
- Re: Avoid global pointers in dae, Francesco Faccio, 2016/08/15
- Re: Avoid global pointers in dae, Carnë Draug, 2016/08/15
- Re: Avoid global pointers in dae,
Carlo De Falco <=
- Re: Avoid global pointers in dae, Francesco Faccio, 2016/08/15
- Re: Avoid global pointers in dae, Carlo De Falco, 2016/08/15
- Re: Avoid global pointers in dae, Francesco Faccio, 2016/08/15
- Re: Avoid global pointers in dae, Carlo De Falco, 2016/08/15
- Re: Avoid global pointers in dae, Francesco Faccio, 2016/08/15
- Re: Avoid global pointers in dae, Francesco Faccio, 2016/08/16
- Re: Avoid global pointers in dae, Francesco Faccio, 2016/08/16