World: r3wp

>> d
** Script Error: d has no value
** Where: halt-view
** Near: d
>> e
** Script Error: e has no value
** Where: halt-view
** Near: e

>> test: funct [ ][ parse [ "abcd" ] [ set d string! end ] e: "abcd"]
>> test
== "abcd"
>> d
== "abcd"
>> e
** Script Error: e has no value
** Where: halt-view
** Near: e

only set-word are used as markers to declare a var as local

Right. So you need to use it in a set-word expression somewhere, 
or put it in the locals list manually.

like this

test: funct [ ][d: none  parse [ "abcd" ] [set d string! end ] e: 
"abcd"]

I guess it saves writing /local

Or like this:

test: funct [/local d ][parse [ "abcd" ] [set d string! end ] e: 
"abcd"]

yes, but you can inspect the source of funct if you want :-)

R2 builds with the new changes! Yay! Time to go out and party!

Installs on Windows 7 but need to be admin to install.

REBOL/View 2.7.7 released:
http://www.rebol.com/downloads/v277/rebview.exe

(Core 2.7.7 is rebcore.exe)

Many thanks to Brian Hawley for his R2/Forward contributions in this 
release!

Where's the docs?

I have a 2.7.7 summary page to be posted shortly - but, we're going 
to need someone to summarize the R2/Forward addition.

the HTTPS scheme is missing in Core. Why?

Core ?

There is only a View release isn't there?

http://www.rebol.com/downloads/v277/rebcore.exe

Anyone seen Brian's R2/Forward docs?

Why are the names changing?

Thank you for 2.7.7 - Happy New Year!

We should decide on a consistent scheme ... 
used to be rebol.exe for core  ...

Maybe rebcore is for web servers that don't need SSL ??

Oldes, where did you get that link from?

From Carl's message of course, just read it again:)

btw.. I can confirm, that SSL is working fine in the rebview. Thanks 
for it.

Ah .. I wondered what that message meant at the bottom ..

wow, cool !! thanks to Brian and Carl for this !

I ohpe there is a base with ssl and all the stripped out view stuff.

Many thanks to BrianH and Carl !! 8-)

has an osx version been build already?

build -> built ?

Windows only ...

I guess people need to test the new builds and report any issues 
before other ones are built

Now that I'm back home I can document the changes. Sorry for the 
delay.

R2/Forward is documented in extensive code comments in the source, 
which is available in R3 chat #837. I need to integrate the fixes 
I did during the migration to the mezzanine source.

Brian in R2 is says one of the components is Windows Registry access. 
 What would some of those functions be?

I see 'run is still not available in this version.

The R2/Forward code is licensed (MIT), not donated. From now on, 
the aim of the R2/Forward project has changed. Now its main goal 
is to provide forward compatibility to old R2 versions. I'll be reorganizing 
the code accordingly, and trying to push support as far back as 2.5.0, 
the last version that is supported on the deprecated platforms.

You don't need 'run ....

call works ...

not sure what run was.

The registry functions are unset before runtime in /Core and /View, 
for security reasons. They are available to SDK apps if necessary.

They are documented in the SDK docs.

call "demo.pdf" is the same as run "demo.pdf"

in my case, windows loads acrobat and loads demo.pdf

Are we going to get a free SDK for this version?

Afaict, RUN is basically CALL "start.exe ..."

You wish ...

Got ya.  That is what I thought it was.

I do wish.  :-)