#zinc

stil lhavent figured out how to allocate that space for C library objects .. still 0 :/

c0170, what are you trying to do?

bgamari: http://stackoverflow.com/questions/28154683/rus...

^^ https://github.com/rust-lang/rust/issues/28157336

I asked on stackoverflow to get ideas

need to allocate runtime sized object which then retype to C type object.

c0170, it's really runtime sized?

you don't know the size at compile time?

c0170, I'm not sure I follow your issue here

c0170, init() in this case will produce a zero-initialized array of four u8s

it seems to me that is exactly what you are seeing

I am seeing that gpio is a pointer to 0

rather, init() will produce a zero-initialized reference to an array of four u8s

have to run ,be back

c0170, that is what you should be seeing

I shared disassembly there of the function new

c0170, yes, I see that

c0170, it is correct

c0170, You are misunderstanding what init does

probably yes

I had to initialized that array so I found init()

what other options are there? have to look for

it's not producing an array

it's producing a reference to an array

c0170, you need to provide room for the C data structure within your Rust type

unless you want to use dynamic allocation

which is best to avoid in this case

c0170, as you almost certainly know the size of the C data structure at compile timme

c0170, you likely want something like this, https://github.com/jdm/rust-socket/blob/master/...

farcaller, fixed shiny for you

it was broken?

:(

thanks

bgamari: no dynamic allocation, and yes its compile time but for each target different... so gpio_type for freescale might be 4 bytes, for silabs 20bytes

c0170, ugh

c0170, what library are you using?

there can be a function call, get_gpio_size() which returns sizeof(gpio_type) for the target

mbed :-)

c0170, I believe you need to know the size at compile to do static allocation

:(

c0170, CPP magic could work around this

what do you mean CPP magic?

#ifdef PLATFORM_FREESCALE

#define GPIO_SIZE 4

#else ...

yes, that could be.. dont want to do that at first

as library is changing

and maintain all those defines might be a nightmare

but for now can do that

going to get some sleep, thanks bgamari ;) talk to u later

one more question, for preprocessor magic usage, how that work in the rust world?

you'd need to send your rust sources through CPP

c0170, alternatively you could

write a macro

"send your rust sources through CPP"

"left IRC"

:-D