World: r3wp

Pekr definately a bug it looks like as any-type! doesn't work either:

>> parse [/ /R3/Blah/] [any-type! path!]
== false

Please submit it Pekr to curecode.

That doesn't work in 2.7.6 either.

You can submit it yourself. It was matched as a word!, so I can see 
no problem with that :-)

matched as a word?

>> parse [/r3/blah][any-type!]
== false

How are you seeing it as a match for word?

We will need to know that cause any-type! doesn't match.

I'm thinking we need an any-path function.

or type rather.

Paul, it returns false, because they are two separate refinements.

>> parse [/b/a] [2 any-type!]
== true

Ahhhh.  I went the path route.

So with parse we should always think in terms of refinements instead 
of path.

only if the leading char is not a /.

Gotcha.

whoops, only if the leading char IS a /.

right, I understand.

I'm curious how Pekr, got word! do match though.

Paul - as easy as parse [ / ] [word!] ? :-)

line continuation doesn't work in the r3 console?

there are some limitations compared to the r2 console.

an open [ doesn't continue to next line? - just checking

yes, correct. you can't paste code in the console.

thx

i just tried to download the new r3alpha.

my NOD32-antivirus guard identified it as a variant of Win32/Adware.Antivirus2008

:-)

that' s curious.
I can download with firefox without problems.
but with seamonkey it's no longer available.

I know of no language that has this!  

evoke 'crash

nice...

why settle for unintentional crashing

>> ? evoke
USAGE:
        EVOKE chant

DESCRIPTION:
        Special guru meditations. (Not for beginners.)
        EVOKE is a native value.

ARGUMENTS:

        chant -- Single or block of words ('? to list) (word! block! integer!)

perhaps a single guaranteed way to provoke crashes to see how they 
are handled on different platforms.

Pekr, i thought you were parsing the /R3/GUI as word!.  Ok, I misunderstood. 
 Thanks Pekr.

I like that. This could eb a cult hit. Somebody quits your app, evoke 
crash. Wish for evoke 'reboot-os!!!

The RebDev Web Client seems to be broken :


*** RebDev Error: client is out of date ** Script Error: cause-error-here 
has no value ** Where: error ** Near: cause-error-here


I guess this is to do with the changes being made to the server to 
fix the "unicode" problem.

is rebol.com going Cheyenne ?

Nice trick that works in R2 and R3: If you put
    rebol []

before the code you would otherwise paste in the console and include 
that header in the copy, you can
    do clipboard://
to do the code :)

It doesn't mess up your console history either, as pasting in the 
console does.

I'm using this one-liner function for it:
>> ?? drc
drc: func [][do read clipboard://]

That doesn't need a rebol [] header, and is probably a good candidate 
for your %user.r.

Here's my %user.r function:

explore: func [

    "Open directory in the file manager (shell shortcut function)."

    'path [file! word! path! string! unset!] "Accepts %file, :variables, 
    and just words (as dirs)"
] [
    path: case [
        unset? :path [to-local-file what-dir]
        file? path [to-local-file path]
        string? path [path]
        true [to-local-file to-file path]
    ]

    call ajoin [{"} get-env "SystemRoot" {\explorer.exe" } mold path]
]

CALL is less capable (and less buggy) in R3, but CASE is more capable 
:)

CALL doesn't support block arguments or any options yet in R3, though 
you can workaround some of its limitations for now.

One question to R3 chat. Was there any change, that enter now does 
not list new messages one each time?

If such functionality was removed, how do I simulate it? L does list 
of msg heading, lm lists msgs even with body. But all of them at 
once, not one in each press ?

hi,  i am very to play with R3 but  i don't find a way to do a round 
of a amount or decimal with a scale example i would like to 1/3 in 
a interest amount with 8 decimal . how a can do this with R3  ?  
the simplest way or the better way ?  thank of you all

i find this way => round/to (1 / 3/)   0.00000001

round/to 1 / 3   0.00000001

It's a known bug

sorry, I misread. (I read too fast these days) There is indeed a 
bug which causes certain roundings to be incorrect with the ROUND 
function, but it should not occur with the above example.