World: r3wp

I used succesfully such arrays of floats as argument in my interface 
to AGG...this is no problem IMO

Cyphre do you have documentation on AGG anywhere?

cyphre how do you do it ?

it's curiosity not evilness ...

Paul: the docs aren't still for public..due to alpha state. When 
we reach beta the information in the docs will be 'stable' enough 
so all people could write code which syntax don't change.

Excellent at least there exist some docs :)

Shadwolf: let me show you some example...

oki

to-double-array: func [blk /no-header /local result][
	result: make binary! []
	if not no-header [

  insert tail result third make struct! [d [double]] reduce [length? 
  blk]
	]
	foreach dbl blk [
		insert tail result third make struct! [d [double]] reduce [dbl]
	]
	result
]


pass-doubles: make routine! [
	doubles [binary!]
	return: [int]
] some-lib "PassDoubles"

my-doubles: to-double-array [10.5 2.8 3.0 2.325]


pass-doubles my-doubles

---------------------------

on your C side:

extern "C"
MYDLL_API int GradientPen(unsigned char* doubles)
{
	<your code here>
	return 1;
}

this way you can pass a block of decimal!s to C side

note: the first value is the length of the array if you don't use 
the /no-header refinement

ups: the 'GradientPen' should be  'PassDoubles'

but I hope you got it

yes I understand i think

...then you can either work on the array directly using C code or 
copy it into new array etc.

but how to handle in rebol a C function of this kind void  my_func 
( int my_arg[25] ) { code... }

without adapting the C function argument type

let me check...

If I'm the conseptor of the external C lib i can do ma best for preprepare 
the data to be use to be teh easier to deal for rebol but I want 
to use a yet existant lib I will have to work pretty hard to be allowed 
to inteerface rebol code and this library

in PassDoule on C side you have a char * double argument that's not 
the same as handling a pre defined PassDoubles( unsigne double [4])

in PassDoule on C side you have a char * double argument that's not 
the same as handling a pre defined PassDoubles( unsigne double doubles 
[4])

I'm agree with you char * can feet every thing but this will need 
you on C side to make the spliting of the char content user << and 
&& maks to be able to retrieve your initial data passthue by rebol 
;)

it's impossible on C side  code to do without a spliting statement 
the direct exploitation of the data you pass to the lib

using rebol

here is teh example of your case:

test: make routine! [
	arg [binary!]
	return: [int]
] my-lib "SumIt"

probe test #{0100000002000000030000000400000005000000}

==15

the C side:

extern "C"
MYDLL_API int SumIt(int my_arg[5])
{
	int result = 0;
	for(int i = 0;i<5;i++){
		result+=my_arg[i];
	}
   return result;
}

you can build the binary! array using this function

int-to-bin-array: func [blk /local result][
	result: make binary! []
	foreach int blk [
		insert tail result third make struct! [d [int]] reduce [int]
	]
	result
]

>> int-to-bin-array [1 2 3 4 5]
== #{0100000002000000030000000400000005000000}
>>

hope this helps you

yes it helps me a lot

so you can see everything is possible to do (except the callbacks 
;))

to figure out in simle example this looks easy .... (hum not a lot 
in fact beacaus all the science is done by int-to-array reebol function 
witch is not pretty accessible to common or mortals )

maybe one improvemet would be great for us:

have some faster way how to construct those binary! data from Rebol

I hope this could solve the REBIN feature or else we need some another 
native functionality for that

you could makje it faster by reusing the same struct instead of creating 
a new one on each iteration

that would avoid a reduce too

and if y have twenty array sized and typed  different kind for my 
external lib I will need to wirte and handle as many function to 
play with binary content

Cyphre you comming to my main point ;) giving to carl a premaid function 
that allow us to deal easyly with array (int, float, char what ever 
type) but for struct based array that's a challenge too and an horrible 
task to do

example: struct my-struct { int a[10], char *name, other-struct ptr-ostruct[20];}

yes Gabriele this could help too....I wrote this function as a quick 
one so it can be optimized for sure

in the current way to handle you need to be very sharp to can interact 
with it from rebol and that why Cyphre you have all my admiration 
for your quick made AGG external exploitation script ...

shadwolf: I think you only need to write one global function which 
will convert you rebol block of chosen datatype into binary! form...this 
way you can pass any content to C side...

that's the REBOLTo C way but how about the C to rebol way (that I 
provide  using the MD2 file example)

As I said it is not so hard when yog get more experience...I spent 
hours when started to use DLLs from rebol. I had also bad luck I 
wanted to use very badly designed DLL in my first project so this 
was even bigger pain for me ;)

C to Rebol is very simmilar...have to leave now...bye for now