AltME: R3 Building and Porting


LiH: to me it looks you are right, you can do "pull request" with the fix.

As I'm updating my old scripts on, I'm trying to understand the problems with compress/gzip & decompress/gzip ,
and found at least one issue in u-zlib.c .
When compressing, as the checksum method is assumed to be adler32 for most of the code, stream->adler (the current checksum) is wrongly initialized to 1 in two places, giving an off-by-one checksum in the output and making it unusable for decompress/gzip.
Still no clue for what yields the
     ** Script error: value out of range: none
error and why calling
     compress ""
seems to fix this problem sometimes.It seems that something isn't correctly resetted between calls.

Now digit the following commands in MinGW console: => Now type ??

Can rebol be built to include .r scripts for a portable rebol?
not sure I understand your question  ':-/
to distribute applications?
Bundle scripts along with the rebol executable, for distribution, as a single file.
if you compile the host kit you have full control over this.  Otherwise, Saphirion seem to have built an encap tool for R3.
Saphiron's encap tool was built before the sources were available
If you do what Florin wants, how would you get your code to execute instead of landing on the console?
the console is just a loop in the main which gets a string and executes it.  what you'd do is execute a string of utf8 text directly.
I had the r3 hostkit running as a dll with full host support... in fact, I was able to execute R3 scripts from within R2   :-)
obviously there was no sharing of info, only exchange of string data
so I'd use load/mold on the string from/to R3  ...
Are you answering the question?
I'm just saying that with the hostkit, you can execute or setup evaluating whatever you want however you want.
florin: yes, it's possible to include embedded modules or embedded extensions with R3. but it's not documented how to do so, at the moment, so you'll have to dig through the sources yourself.
for embedded modules, it could be as simple as dropping your module in src/mezz/, including its filename in src/mezz/boot-files.r and doing a full rebuild (including `prep`) after that. didn't try yet, though.
Florin, I wrote this about adding your own scheme
GrahamC: Wonderful, thanks.

Last message posted 91 weeks ago.