Re: OpenEuphoria on the raspberry pi
- Posted by mattlewis (admin) Feb 11, 2013
- 3075 views
rkdavis said...
will do, i know squat about mercurial as i use fossil so i'll read up on bisect.
the warnings about unused variables i'm not too bothered about but getting a few like the following that i'm a tad "worried" about
be_alloc.c: In function ‘new_dbl_block’: be_alloc.c:994:2: warning: passing argument 1 of ‘ERealloc’ from incompatible pointer type [enabled by default] be_alloc.h:164:14: note: expected ‘char *’ but argument is of type ‘struct free_block **’ be_alloc.c:994:16: warning: assignment from incompatible pointer type [enabled by default]
you get similar when building on x86?
I do get those. They aren't terribly important, though we should probably get rid of them, since they add unwanted noise. For the purpose of memory management a pointer is pretty much the same as any other pointer, but a function has to have a definite type for its parameters.
Matt
