Re: unsigned-int

[Catonano <catonano@gmail.com>]

2017-06-22 21:13 GMT+02:00 Catonano <catonano@gmail.com>:
>
>
> I apologize if my questions are naive.
> I wrote my last scrap of C code in about 2004 and it never was my thing
> Also the manual is a great reference but not a great tutorial and I'm not
a great reader, probably.

Something that is concerning me is that in the example  a "rows" variable
and a "columns" variable get declared as

unsigned int rows;
unsigned short columns;

and then they get passed as arguments to freexl_worksheet_dimensions as

&rows, &columns

like this

ret = freexl_worksheet_dimensions (handle, &rows, &columns);

In scheme I am NOT declaring anything because I don't now how to
I am just passing void pointers to freexl_worksheet_dimensions

But when you declare a variable of some type, some memory gets reserved for
the value to be contained in that variable, right ?

But I am passing void pointers here, so is any memory region being reserved
? I'm afraid not

That might be the reason why I get garbage rows numbers. Because I am
making it read some random memory region that has been already reserved for
something else, that's already populated with God knows what and I am
making it interpreting that stuff as numbers.

I don't know, I'm speaking freely, here, this is a wild hypothesis

I can't make so much sense of this code

Please bear with me :-/

Thanks in advance