[REBOL] Re: REBOL/Core 2.5.3 Released
From: brian:hawley at: 9-Aug-2002 16:29
At 09:08 PM 8/2/02 -0700, you wrote:
>A new REBOL/Core has been released for testing purposes.
...
>Some of the changes include:
>
> MAKE-DIR Rewritten
> New Bitset Functions: CLEAR, LENGTH?, EMPTY?
> Changes to SKIP Function
> ARRAYs Initialized with Block Values
> Added PARSE BREAK Word
> Fix to OPEN on Network Ports
> Fixed Crash on Modified Functions
> Unset Object Variables (on Exit)
> Added BUILD-MARKUP Function
> Revised BUILD-TAG Function
> Revised DECODE-CGI Function
> and more...
Yay to all, but let me add one I noticed (belatedly):
TO-REBOL-FILE and TO-LOCAL-FILE are finally there
as 2.5.0 said they would be, and they work too!
Well, for the most part. TO-LOCAL-FILE still needs to be
passed a full file specification, but since you can use
CLEAN-PATH to get that I don't have a problem here. That
should be documented in the function spec, though.
TO-REBOL-FILE even doesn't choke on NTFS file streams
except in one case, when the file stream is specified
off of a fully relative file name, like this:
>> to-rebol-file "blah:hiddenstream"
== %/blah/Lang/REBOL/Core/hiddenstream
when it should be
>> to-rebol-file "blah:hiddenstream"
== %blah:hiddenstream
I suspect that the existing behavior might be a carry-
over from the Amiga version of TO-REBOL-FILE, but I
would be the last person to ask that :)
Really, REBOL is going about file stream support wrong.
I would like to see NTFS file streams (or forks) use the
GET-MODES 'forks interface, just like it is on Mac. I
love the forks, type and creator support on Mac - it
would be cool to be able to do similarly arcane stuff
on Windows as well. On the other hand, perhaps streams
are too arcane for REBOL to support directly...
I'll look it up on MSDN and see what I can hack up to
improve stream support for REBOL, then tell Feedback.
And you all, of course.
Brian Hawley