World: r3wp

Ah, good question, now I think Christian meant the binary format 
of rebol's date! values, not any database's date format, which should 
be available as a string at least.

I suspect the passing of rebol date values may not have been implemented 
in R3 extensions yet (not that I've tried anything there yet).

I've looked in DevBase, but haven't asked questions there yet. I've 
scanned all the extensions documentation on DocBase and the header 
files in the host-lib/extension packages. 


I didn't even manage to read a date value in a simple command like 
   TEST-DATE: COMMAND [DATE [DATE!]]      About every member n the 
REBOL value c-union type seemed to only contain zero values.

I have no idea on how date values are stored in C, all that the docs 
say is that date values are 32 bit encoded date and time zone values, 
so I mainly tried with value.int32a but tried other members too. 
I have no idea about how the encoding is done and - as Anton said 
- I really don't want to reverse engineer it.

Hmm.. that doesn't look very promising.

Anton, yes, I can get date values from databases if I ask for string 
values, but I'd rather like DATE! results.

Yes, it should be faster performance.

But I suppose if you need it badly enough and can't find how to move 
dates then you parse and transform between the string formats.

On the rebol side, should just need a MOLD and a LOAD / TO-DATE...

Surely *someone* will illuminate the situation soon...

ChristianE - either post on R3 Chat, or post to Robert - he might 
be the most direct channel to Carl, so I think you might get your 
answer faster that way ....

Hmm, I think I've to check this again. At least, a simple 

    RXIEXT int RX_Call(int cmd, RXIFRM *frm, void *data) {
        return RXR_VALUE
    }
    
returns a proper date value for

    test-date: command [date [date!]]
    
I'll see if I can find some time to work on this evening.

Using external extensions with a104, I get an error when using these 
series macros :

RL_SERIES_INFO(ser, RXI_SER_TAIL) ,  RL_GET_CHAR(ser, idx) , and 
RL_MAKE_STRING. Did someone noticed this ?

ChristianE, can we see your extension .. even if it is a WIP?

There are things that have to be cleaned up a bit first, Graham, 
but I hope I can publish it very soon (counting days, not weeks).

It really should only depend on the time I can piut aside to work 
on the driver.

Hmm, I somehow don't manage to compile my odbc extension with a109, 
on import I get the following error

>> import %../lib/odbc.dll
** Script error: make-scheme has no value
** Where: do -apply- make catch case case -apply- apply import
** Near: do body obj


I do understand that it's related to MAKE-SCHEME moving into SYS 
context,. Do I have to import SYS into my extension module's context 
first and, if so, how? NEEDS: [SYS] doesn't work, my extension is 
already declared with TYPE: MODULE OPTIONS: [EXTENSION DELAY], trying 
to access MAKE-SCHEME directly thru SYS/MAKE-SCHEME makes the intepreter 
crash.

Maybe your extension is loaded faster than mezz-code?

That's why I'm trying to DELAY. Delaying doesn't seem to work for 
embedded extensions according to curecode, but here it's a simple 
dll import ...

Yes, I saw the ticket ... maybe it gets fixed in a110, but not sure 
it is a cause. BrianH discussed it a bit today ...

See REBOL3 channel ... or wait for BrianH ....

is make-scheme in the lib context?  cause that worked out for me 
using other mezzanines...

It never occured to me to try with LIB instead of SYS, it's in LIB, 
too, of course! But calling LIB/MAKE-SCHEME crashes, too, so I guess 
the problem is somewhere else.

Both bugs 1723 and 1729 have been fixed, for alpha 110. The next 
release should fix your problems, Christian.

We have been discussing adding a header option to tell the system 
to put off loading an embedded extension until after the mezzanines 
have loaded (or have that be the default, and have an option to load 
before the mezzanines). I haven't looked over the startup code yet 
to see how to do this, but it shouldn't be too hard. I'm waiting 
for Carl to decide on the option (he seems to be the namer of that 
kind of thing right now, I'm just an implementor).

Thanks, Brian, for the status update, that's good news in more than 
one way. I con stop trying and just expect it to work next time. 
.'J

Where to start when I would like to learn how to write own extension? 
This page is out -of-date:/
http://www.rebol.com/r3/docs/concepts/extensions-examples.html

Here's a minimal example of an extension:
https://gist.github.com/0677266b8511d83ce76a

Also christian did an ODBC extension

fine... I can compile the minimal example, have problems with the 
samples above. The ODBC source is where?

don't think the odbc sources are published at the moment

see the announce group

the primary change compared to the docs is that many things have 
been renamed

some things

I don't see the ODBC source, only link to dll and docs.

Hmm... I thought I once saw the source

maybe that was the first attempt....

AFAIK his is the only working extension released

I did some early extensions .. but I doubt that they work now

With the sample2.c example I have problem with undefined RXI_SERIES_INFO 
and RXI_GET_CHAR

(I'm using #include "reb-host.h" from A110)

I think RXI_SERIES_INFO is now RL_SERIES

works

with RL_GET_CHAR

i think you could also replace RXI_GET_CHAR by first obtaining a 
pointer using RL_SERIES(ser, RXI_SER_DATA) and then just indexing 
into this directly

well, RL_GET_CHAR is probably better

all RL_* functions are safe to call from extensions

(macros, safe to use)

I did several extensions for windows, and you can find the source 
code and the dlls here: http://www.colineau.fr/rebol/R3_extensions.html
. This code may not be up to date, but recently I have compiled new 
versions. If necessary, I can upload them.

Oops, I forgot about your stuff jocko .. does it all still work?

I would appreciate a very simple example how to make extension using 
external DLL. So I could write for example ImageMagick extension.