World: r3wp

sure

i'll compile this thang for windows somewhen early next week

should work as-is

so, where do i claim part of the bounty :) ?

ehehe... the dyncall is the easy part hehe...  ;-)

if you can send me the code you have so far, I'll be working on it 
this very week-end, on windows and that means starting to build the 
/library API itself, including struct support and stub function mapping 
and all.

my email address here is the best way to send me stuff, if you are 
so inclined .

I've put up my current code for the dyncall extension at: http://github.com/earl/rebol3/blob/master/extensions/dyncall.c

cool thanks, will give it a look.

Maxim asked me to take a look here...  it would be good to throw 
the main parts of this into www.rebol.net/wiki -- because it's hard 
to dive into the details in an evolving discussion, do you agree?

yep... but I'm mainly interested in a quick critique of the code 
snippet I post above  (the long post)

once I have parts of this working, I'll do a wiki post and release 
alphas so people can test.

Should the spec block of a lib func be similar to the spec of a normal 
func ?

If so, then all the help features might work ok.

I should note that there's a pending change to func specs.  Namely, 
the use of set-words for special options.

For example, there's no way to describe the return value of a function, 
or trace options, or catch/throw handling.

I was planning to use set-words to do those. For example:

sum: func [a [integer!] b [integer!] return: [integer!]]

This is also important to give us localized returns, because the 
word return here can hold the binding to the function's defined context, 
the necessary link to make it work.

But, I've yet to post all this up for discussion... however, you 
may need to think about that.  I would be good to have spec blocks 
work over all functional values.

Just a note.

thanks for your feedback.

I'm sure I'll have more to say... multitasking right now.  Finally 
got R3 chat moved.

hi maxim, do you have some news about the status of /library ?

got dyncall compiled on windows and working on integrating it with 
the extension... not done though as I'm concentrating all my dev 
time on finishing a contract.

should resume work on this next week.

great, thx for the info.

was /library ever finished?  Or did it turn out to be hard?

as this is driven by client requirements... it was temporarilly bumped 
by more pressing stuff... but its still on the top of the list.


it will resume when this temporary new development is working (which 
is also REBOL-related).

ironically, this new development is something I put on hold for years... 
so its a good turn of events in any case  :-)