World: r3wp

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.

since we aren't compiling the core ourself.  it might be using some 
different typedef.

this is why ISO standarized things over 10 years ago.. ;-)

hehe

standards?  programmers?  are you kidding?  ;-)

I can work around it for now but I would recommend the ISO approach 
myself (for types)

except the RE* types of course which are special

I agree, if it can be guaranteed that it won't break between MSVC 
and GCC.

we can supply a stdbool.h and stdint.h for the MSVC users if need 
be.. until MS catches up

anyway, just a thought

Is there a version of the host-kit that works with AGG without Windows?

in theory you can use to-image! on a gob!   but I'm not sure its 
been fixed in latest hostkits and not sure that really answers your 
question either ;-)

by windows do you mean on another platform than MS Windows?

yes

the windows code is filled with truetype font stuff for example

I would need to use freetype

nope.  you are the brave soul we where all waiting for  ;-)

so bet it :)

be even

ssolie: the only file that needs to be reformatted so it supports 
other platforms than windows is agg_truetype_text.cpp + .h

Otherwise there is already available FreeType wrapper so the rest 
of code can work  even on OS4

But the current hostkit code needs some more work to extract the 
font/text rendering parts so they can be controlled by defs.

If you don't want to waste time on this I can have a look at it over 
the weekend and make the changes so you should be able compile without 
the text code for now. Just let me know.

Cyphre, that would be great if you could make the necessary changes. 
I have simply commented out text support for the time being so I 
can continue to work on other areas.

FYI - I filed some bug reports for the host-kit for the more annoying 
problems I've hit. Feel free to add comments to the reports.

saw them all good ideas

scanning: reading back a few pages...

looks like Steve got his questions answered

we can probably find some way to handle BOOL via the reb-config.h

If C code line terminators are effecting your tools, I suggest you 
get better tools.

btw, I released a new host-kit which has custom gob rendering enabled 
(very early prototype) but its got an OpenGL rendering engine running 
within view.


you can see the download link in the announce group, if you want 
to try it out.

Andreas: the code base is a mix of both single source and multi-source 
tree.


I will not allow source files to become unreadable with every other 
line being #ifdef for a different OS. Those are not maintainable.

no need to compile anything, there are example scripts and compiled 
versions  in the cgr-apps of that zip file.

this being said I would like to have a private chat with you about 
some issues I encountered so far.

A: The OS/dirs are for code that is really quite different.  Merging 
into a single source does not help keep it in sync, because most 
coders only modify the platform of their choice. They can just as 
easily diff.

(Let's just say I've been doing source control for a long long time. 
;)

Maxim: on OpenGL, that's good news.

Checking Steve's bug postings.

Carl, the codebase is already out of sync. Viz. the hostlib vector.

And from inspecting the differences between the Linux and Win32 hostkit, 
there are not really any.

Except for the hostlib vector and 3 or 4 minor lines.

But maybe you misunderstood the suggestion.,

I'm not saying to change much compared to what is done currently, 
as the codebase is 99.95% the same in the past Win32 and Linux hostkit 
releases.

Just to get rid of this artificial distinction alltogether, and keep 
the hostkit a single distribution, from which all platform targets 
can be built.

Makes it _much_ easier to build and test for multiple platforms.