World: r4wp

ok, thanks

Oh right, the pointer is returned from the function, not the value

There's no problem in allocating memory to return from a function, 
but you have to use ALLOCATE and later FREE it

Ok, so this version does what I expected :)

f: func [
	val	[integer!]
	return:	[struct! [value [integer!]]]
	/local s
][
	s: declare struct! [value [integer!]]
	t: allocate size? s
	s/value: val
	t: copy-memory t as byte-ptr! s size? s
	as struct! [value [integer!]] t
]

s1: f 1
print ["s1/value:" s1/value lf]	; == 1
s2: f 10
print ["s1/value:" s1/value lf]	; == 1

You don't have to declare an intermediate struct and copy it

t: as struct! [value [integer!]] allocate size? s

t/value: val

t

You should check the allocation for being a null pointer, though

how that can happen?

If you don't get the memory from the operating system

The form-* functions in the C library binding do pretty much that:

http://red.esperconsultancy.nl/Red-C-library/artifact/a1a55e070454c421657185b1d9d09f480d6c5587

Another question :) Is there any easy way to convert integer! to 
float! ? I wrote something for float! to integer!, but with integer! 
to float! I'm bit lost.

Another question :) Is there any easy way to convert integer! to 
float! ? I wrote something for float! to integer!, but with integer! 
to float! I'm bit lost.
 - see http://www.fm.tul.cz/~ladislav/rebol/library-utils.r

The approach is as follows:
1) convert integer to double (=decimal!)
2) convert double to float

aha, sorry, this is a Red group...

yes, I'm looking for Red/System solution.

Why does this code throw *** Runtime Error 11: float stack check 
?

i: 0
f: 0.0
p: declare pointer! [float!]
arr: allocate 100

while [i < 10][
	p: as pointer! [float!] arr + (i * 8)
	p/value: f
	f: f + 0.1
	i: i + 1
]

Sounds like a bug, although the program is overly complex

i: 0
f: 0.0
arr: as pointer! [float!] allocate 10 * size? float!

while [i < 10][
	p/i/value: f
	f: f + 0.1
	i: i + 1
]

That should work, and be more secure

arr/i/value: f

Oh, with path notation, you need to adjust the loop to start counting 
the index from 1

I'm still discovering how Red/System works :)

If your original program keeps erroring out, please enter it in the 
bug tracker

Kaj, your code throws compilation error invalid struct member i in: 
arr/i/value

Ah, it's actually even simpler :-)

i: 1
f: 0.0
arr: as pointer! [float!] allocate 10 * size? float!

while [i <= 10] [
	arr/i: f
	f: f + 0.1
	i: i + 1
]

In Linux, on your original code, I get:

*** Runtime Error 9: float invalid operation
*** at: 08048397h

With your latest version I get *** Runtime Error 11: float stack 
check (on windows).

Better enter both in the bug tracker, then

Rebolek: yes, add them to the bugtracker, I will fix them this weekend.

That's great, thanks!

Just an update, I just tried latest Kaj's code on Ubuntu under VirtualBox 
and I get *** Runtime Error 9: float invalid operation

It looks like we haven't tested floats pointer arithmetic enough.

Is that 64 bit Ubuntu?

32bit Lubuntu

Rebolek: I've pushed a fix for your issue (Intel CPU). I'm looking 
on the other issue you had with ARMv5TE.

Great! But I've got another one... putting it to bugtracker.

For the ARM isse, I'm testing with an emulated ARMv5TEJL, and both 
Fibonacci and Mandelbrot perform correctly. I've added some questions 
to the ticket on the bugtracker.

I will provide the info tomorrow when I have access to the machine.

I've answered to your ticket #220.

Thanks, it's getting late, I better should left testing for tommorrow 
:)

I've located the cause of bug #220, you should have a fix when you'll 
wake up. ;-)

Fix for issue #220 pushed.

Wow, that' was fast! :)

I've added information about my machine to #219 (no gcc info, as 
it doesn't have gcc installed).

Doc, another float! problem found (#221).