Re: some notes about mex support in Octave

[David Bateman]

John W. Eaton wrote:

>On 26-Jul-2006, David Bateman wrote:
>
>| John W. Eaton wrote:
>| 
>| >On 26-Jul-2006, David Bateman wrote:
>| >
>| >| Ok, then what about the attached patch.
>| >
>| >Thanks, I checked it in.
>| >
>| >| The test code should probably be
>| >| cleaned up. Also I note that valgrind is not clean against the mex
>| >| types, though that is independent of the sparse type..
>| >
>| >Can you send an example of some code that shows the problem?
>| >  
>| >
>| Well in fact I had problems with all of the mex example code in
>| valgrind. For example launching octave with "valgrind --tool-memcheck
>| octave" and then running the mystruct mex example gave me the errors
>| 
>| octave:1> a.b=1; a.c=2; mystruct(a)
>
>OK, I think the following changes fix this problem.
>
>Thanks,
>
>jwe
>
>
>  
>
Ok, that worked perfectly..

D.

-- 
David Bateman                                address@hidden
Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph) 
Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob) 
91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax) 

The information contained in this communication has been classified as: 

[x] General Business Information 
[ ] Motorola Internal Use Only 
[ ] Motorola Confidential Proprietary