World: r3wp

Cool... I'm able to obtain image size from red using iMagick

Nice, let us know if you hit any issue.

the main issue is that I had to find out, how to print integers:) 
Kaj's C-library is not working on windows.

*** Compilation Error: multiple type casting not allowed
*** in file: %runtime/../library/C-library.reds
*** in function: temporary-name
*** at:  [as c-string! null]

here is a fix:

-- 	_temporary-name as-c-string none
++	_temporary-name none

for a real work with iMagick, the decimal numbers are required.

Kaj has not yet updated the C library binding to the latest Red/System 
version.

Float support will either be added at Red level or at Red/System 
level, depending on how the Red compiler will be built.

A bit hard to update my binding to a Red version that is released 
while I sleep, but I will have a look

By the way, my C binding was developed for Windows so far, and the 
only thing I've really used it for is printing integers :-)

I've just tested it for the the first time on Linux last night, and 
printing worked there, as well

The new pointers sound good, Doc

Glad you like it.

Kaj: sorry if my sentence sounded bad, I was just trying to be informative. 
That is a typical case of impedance mismatch between a thought and 
how it ends up being written. :-)

Btw, about function! extended support: after making a few tests in 
the compiler to extend it, I can't support it for argument passing 
and as return value for native functions without making function! 
type fully first class. The changes required for that are too deep 
and too numerous to be made now.

No problem, I know all about it :-)

I've left the alternative function! uses commented out in my code, 
so they'll be there awaiting a future version

Updated the C and 0MQ bindings to the latest changes

Jocko, input-line works on Linux. I'll test it on WINE later tonight

When I compile this:

either as-logic 0 [
	no
][
	yes
]

I get

Compiling /users/administrator/Red/test.reds ...
*** Compiler Internal Error: Script Error : Invalid path value: 1
*** Where: comp-either 

*** Near:  [emitter/branch/over/adjust/on c-true negate offset expr/1]

Weird error...

Yeah

Oh I see what's wrong, let me fix that

Fix pushed.

Thanks! Good turnaround again :-)

Took me some time, had to run all the tests suite several times, 
refactor the code and find a meaningful commit log message. ;-)

:-)

Jocko, input-line works both on WINE and on Linux, so I have no reason 
to believe it wouldn't work on Windows. What is your code that doesn't 
work?

Oldes, same for print-integer and print-1. What is your code that 
doesn't work?

Next:

dummy: func [return: [integer!]] [0]
either as-logic dummy [
	no
][
	no
]

*** Compiler Internal Error: Script Error : first expected series 
argument of type: series pair event money date object port time tuple 
any-function library struct event
*** Where: opposite? 
*** Near:  [first select/skip opp-conditions cond 2]

Having a quick look at this error.

Seems related to my previous fix.

Yeah, was to be expected

Added two tests to reflect the two cases above to cast-test.reds. 
It now fails with a compliation error.

Fix pushed.

Thanks, both

Peter, the compilation error in the new type casting tests was not 
the right one. Variable initialization cannot happen in EITHER blocks 
now since today's following commit: https://github.com/dockimbel/Red/commit/31b87b9565004574174ba3bf02b4dfaa2db665f2

That change was required to fix issue #84.

Kaj: you're welcome. But no more fixes until tomorrow, bed time here.

OK then, I'll release you from your duties for the duration of eight 
(8) hours ;-)

Thanks for the pointing out the initaliasation changes and fixing 
the tests.

Great to see continued activity and progress on Red.

Kaj, I tested this morning, input-line works under Windows
My mistake was that I did not allocate the input buffer by

in: allocate 255 but by in: "" , which is not really an allocation

on an other hand, I cannot simply include the C-library in my script 
by :

#include %C-library.reds


instead, I must extract the used functions. (here _input-line and 
input-line)


The error message at the compilation is not visible in the console, 
because a large amount of text is printed. Maybe a double declaration. 
Any idea ?