World: r3wp

it allows you to hook up alternate graphics drawing within AGG or 
directly on the window which view opens.  though you still have to 
map all that nasty OS specific windowing event stuff first.  keep 
in mind that you might be able to do stuff like a datatype viewer 
right into the view engine  :-)

so is there supposed to be one host-kit per platform in the future 
or ?

hopefully not.

it being the CGR path to host-kit... its still an infant, but I think 
its promissing already... just worked out a few issues with Andreas 
and its working fine on windows now.

arg... path= patch.

in the host-kit/src there is an os folder... that is where all the 
OS/platform-specific things are supposed to be.

once that is mapped all the rest is supposed to work multi-platform.

Andreas, sharing a common host-kit might be #ifdef hell though?

Yes, in a few places.

But that's how it is already anyway.

true.. it is fairly isolated so far

#ifdef where necessary, and separate files in the os/*/ trees where 
sensible.

when it gets to complex, its extracted and put into an isolated file, 
which is how its been evolving so far... quite straightforward.

We just really need to get Carl to the point where the hostkit is 
kept as a single source base.

Not one codebase for each platform which then slowly get out of sync.

where do commits go then?

rofl.

yeah we need to get to the point where Carl doesn't touch the host-kit 
anymore  ;-D

/dev/null

lol

localhost://svn/

I maintain a Git mirror of the hostkit sources at http://github.com/rebolsource/r3-hostkit

is there a standard for EOL?  amiga uses LF as most sane OSs :)

and I'll probably put my CGR package on github too in a short while.

nope, that's one of the main differences between the hostkits :)

the win32 hostkit has CRLF, the linux hostkit LF

eventually we should just decree one and run with it.

and given that carl seems to be 90% windows these days, it'll probably 
be windows line endings.

bah :-p

agreed :)

(note that my git mirror does not contain A109 because it wasn't 
really released officially, and I wanted to wait if Carl wants to 
hotfix the compile issue.)

Why is there a BOOL and a REBOOL ?

Amiga defines BOOL which is conflicting with R3's BOOL

are they using the same typedef?

no, Amiga typedefs to short while REBOL #defines to int

seems strange to have 2 bool types in REBOL ?

REBOOL is more compact for smaller structs.

strange that its trippping you though since its within an #ifndef

#ifndef BOOL
typedef int BOOL;       // (int is used for speed in modern CPUs)
#endif

the precompiler knows nothing of typedefs so when Amiga typedefs 
BOOL it skips the #ifndef check

I may have to keep the rebol and amiga stuff completely seperated

(different files)

I'd just rename the rebol BOOL to some other Identifier,and do a 
quick recursive file replace... I looked and its not used that much.

not good for common host-kit later though..

then give a note to carl so that it gets changed in the next host-kit. 
  cause I don't find it a good practice anyways.  strangely, I was 
wondering if BOOL would cause compiler hickups a few weeks ago.

guess I was right ;-)

maybe REBOL should just use the C99 _Bool type instead which is optimized 
for each platform

instead of assuming int is best

MSVC doesn't support C99.  :-(     though maybe _Bool is defined 
anyways.

lol... silly microsoft..  for windows we can just typedef _Bool until 
they catch up?

thing is I see that BOOL is used in the host-kit as return values, 
so expecting the same dll to be compatible with different compilers 
might be dangerous.