OpenEuphoria

2. Re: Wrapping Functions When Matrix is Involved

• Posted by ghaberek (admin) May 26, 2019
• 1721 views

You just need to allocate the space for the floats, poke them into that space, and then pass the pointer to the function.

Not sure why we don't have peek/poke float functions in the standard library. But this is how you'd do it:

procedure poke_float32( atom ptr, object value ) 
 
    if atom( value ) then 
        value = {value} 
    end if 
 
    for i = 1 to length( value ) do 
        poke( ptr, atom_to_float32(value[i]) ) 
        ptr += sizeof(C_FLOAT) 
    end for 
 
end procedure 
 
public constant xNewtonCreateBox = define_c_func( nd,"NewtonCreateBox", {C_POINTER,C_FLOAT,C_FLOAT,C_FLOAT,C_INT,C_POINTER}, C_POINTER ) 
 
public function NewtonCreateBox( atom world, atom x, atom y, atom z, atom id, sequence matrix ) 
 
    -- we assume matrix is of non-zero length 
    atom p_matrix = allocate_data( sizeof(C_FLOAT) * length(matrix), TRUE ) -- cleanup = TRUE 
 
    poke_float32( p_matrix, matrix ) 
 
    return c_func( xNewtonCreateBox, {world,x,y,z,id,p_matrix} ) 
end function 

-Greg

4. Re: Wrapping Functions When Matrix is Involved

• Posted by irv May 27, 2019
• 1677 views

include std/dll.e 
 
? sizeof(C_FLOAT) 

4

Euphoria 4.1 beta 2

8.41.2.5

sizeof

<built-in> function sizeof( atom data_type )

Parameters:

data_type A C data type constant

Returns the size, in bytes of the specified data type.

6. Re: Wrapping Functions When Matrix is Involved

• Posted by irv May 27, 2019
• 1607 views

The more people who use 4.1, the sooner any bugs will be found, and the sooner they can be fixed.

I think that EuGTK is complex enough to be a fair test of Eu 4.1, and so far, only one "sort of" bug has shown up. It could also simply be documented as an "illegal operation", without inconveniencing anyone significantly. Don't let that stop you from using 4.1 b 2.

8. Re: Wrapping Functions When Matrix is Involved

• Posted by ghaberek (admin) May 27, 2019
• 1607 views

There several options available in The Archive. I wrap all my structs by hand without much difficulty. See this comment.

I'd like to get Matt's memstruct* changes merged it after we get a proper 4.1 release out. It seems ripe for being a "version 4.2" feature.

(*Although I'm strongly considering changing "memstruct" to just "struct" -- but I suppose we'll burn that bridge when we get to it.)

So how is that 4.1 release going, anyway? I'm still struggling with the spaghetti soup that is the monolithic Makefile.

It's slow-going and I've been putting more effort into Euphoria MVC because I think more work is need to refresh the website.

If anything, rebuilding the website will act as a good proof-of-concept that 4.1 is viable for full release.

-Greg