World: r3wp

Compiling /resources/Red/tests/empty.reds ...

*** Compiler Internal Error: Script Error : Cannot use path on none! 
value 
*** Where: build-debug-lines 
*** Near:  [records: job/debug-info/lines/records 
files: job/debug-info/lines/files 
rec-size:
]

Strange...I ran the whole tests suite, as usual, without any issue 
before committing.

Simple scripts are compiling OK for Linux too.

Testing from Linux, the tests are not passing.

hmm, nope. seems there's a bug in my debug fix

Fix pushed. Sorry for the mess.

No problem, thanks

Thanks Andreas.

Can't test the new struct detection due to a new bug

It will be very hard to fix if there's no way for me to reproduce 
the issue.

The code part where the compiler script breaks is not related to 
function return values, but only to function arguments code generation.

It's a Heisenbug, so I'll check in the broken code

I have posted debugging instructions in the ticket comments.

It might be caused by a uncaught wrong definition in your imports, 
that is messing up the imported function arguments parsing code.

It's in Fossil now

I didn't change the imports, only the type definition

Got closer, will change the bug description

If it's heisenberg, that means it still might work some of the time?

Yes, when you're not using it :-)

Wave function collapsed, cat saved, bug fixed.

Eh, the cat survived?

Added Hello World examples to the GTK repository

Here's the simplest:

Red/System [ ]

#include %GTK.reds

gtk-begin
gtk-view window label "Hello, Red/System GTK+ world!"

Here is how that is customarily written in other bindings in other 
languages:

Red/System [ ]

#include %GTK.reds

argc-reference: declare integer-reference!
argv-reference: declare handle-reference!
argc-reference/value: system/args-count
argv-reference/value: as-handle system/args-list

_gtk-begin argc-reference argv-reference

_window: gtk-new-window gtk-window-top-level
_label: as gtk-widget! 0

either as-logic _window [
	_label: gtk-new-label "Good riddens!"

	either as-logic _label [
		gtk-append-container  as gtk-container! _window  _label
	][
		print "Failed to create label.^/"
	]


 g-connect-signal  as-handle _window  "destroy"  as-integer :gtk-quit 
  none
	gtk-show-all _window
	gtk-do-events
][
	print "Failed to create window.^/"
]

I call it Goodbye Cruel World

Very nice!

Cat: I chosed the optimistic option.

:-)

I hope you'll make a nice web page for your GTK binding once finished. 
It also deserves some docs for the dialect API.

I'm not sure. People are not really supposed to use this binding, 
but the abstract cross-toolkit dialect you will make in Red

Could 'gtk-begin be called in %GTK.reds directly?

You mean without the callback wrapper?

Or you want to remove it from the dialect?

I mean, instead of having to call it from every user script, it could 
be called as last expression in %GTK.reds source file directly?

Probably. I'll feel more certain about it later on

Conversely, I'll probably move gtk-do-events out of gtk-view for 
flexibility

People are not really supposed to use this binding

 It's a very nice binding that could motivate some C coders from Rebol 
 community (or outside) to take a closer look at Red/System and start 
 hacking with it. It could be a good way to attract new users.

Actually, it's the most sophisticated binding we have so far in Red/System.

Yes, until the Red dialect is there, or when you really want all 
GTK features. But mostly, I need to be able to make GUIs as soon 
as possible myself

The new alias detection breaks the binding

You mean it makes it crash?

Need to go to sleep now, will look into that tomorrow morning.

just testing for a while... having:
	MagickGetImageWidth: "MagickGetImageWidth" [
		;{Returns the image width.}
		*wand     [wand!]
		return:  [integer!]
	]

When I do:
	width: MagickGetImageWidth *wand
	print ["image width: " width " " MagickGetImageWidth *wand]
I get:
	image width: 78 0000004E
I was expection:
	image width: 78 78
What do you think?

(but that's a detail... I'm still waiting for the decimal support)

Curious bug, I will look into it.

BTW, you can use PRINT-WIDE instead to insert white spaces automatically.

Oldes: I can't reproduce the issue, I tried with the following test 
code:

	#import [
		"msvcrt.dll" cdecl [
			abs: "abs" [
				n 	[integer!]
				return: [integer!]
			]
		]
	]

	width: abs -78
	print ["image width: " width " " abs -78]

I get:
    image width: 78 78

You are right, the main difference is, that I was using stdcall while 
you are using cdecl, which works as expected.