World: r3wp

Checking the CC would be a good start.

How do you mean?

he hasn't gone over the CC tickets in long time.

perhaps he wants a change ... ?

work on something different

but Carl usually optimises into different phases of work.

design
build
fix


we sort of know why Carl has been a bit silent lately (he's been 
working on 2.7.8) now I think he is in a design phase in his mind.

Was there that much done on 2.7.8 ??

Brian Posted a list in the R2 Releases group.


I also hope he included 2 fixes which I got Cyphre to address in 
view which crash or mock-up the quality in AGG.

RAMBO shows about ten fixes

Don't remember AGG related fixes

Carl is not the only one to go over the tickets, the rest of us go 
over them too. But yes, there's new stuff there that needs his attention.

Elan Goldma registered to R3 Chat ... isn't it Elan, who wrote the 
first book on REBOL years and years ago? :-)

Goldman

it's amazing to see that in 2011 it can take so much energy out of 
someone just to tweet a "I'm away for 6 month please don't let a 
message after the bip"

yes, Carl does not handle communication well. We should not start 
advocacy here though, but in advocacy channel ...

there is some indication from some guys here, that Carl might be 
back to R3 now, just looking into the situation, and deciding upon 
what's next ...

Pekr I heard that too ... But that's like the rebol GC we don't know 
in fact :)

but hey maybe carl will come with another super grate stuff ... But 
my point is rebol is already super great stuff that just need to 
be  upto dated one every 6 month ...

sorry I got the last sentence wrong ... But my point is rebol is 
already full of super great stuffs (desktop, console, web plugins, 
 etc...) that just need to be upto dated once every 6 month. Some 
of them maybe needs a redefinition.

for example I would prefere a webplugin rebol/view  for only firefox 
but available on all OS... Maybe basing rebol VM on non hardware 
related  langagues would allow to speed up things ...

R3 can't read and write back source file, to correct platform terminators? 
I used such aproach in R3 - just read, and write back to the same 
file. In R3 I even tried read/string, but it does not help when I 
wrote file back ....

terminators ? you mean the robots from the futur that are tracking 
down sarah conor and john conor ?

Pekr, just tried
write %foo.r read/string %foo.r
on Linux. Converted DOS (CRLF) line endings to LF-only for me.

sorry ...

I tried RMA's source under Windows, and no luck ...

R2 turned out being handy, though :-)

Ah yes, WRITE does not do any conversion, but READ does. So you'll 
always end up with LF-only.

Well, shouldn't R3 under Windows turn line terminators (Johns and 
Sarahs :-) into Windows compatible ones?

Use ENLINE for that.

The full sequence for line terminator recoding is:
write %foo.r to-binary enline deline to-string read %foo.r

- READ/string is a shortcut for "deline to-string read"

- WRITE auto-converts string! to binary, so is a shortcut for "write 
to-binary" in this case.

So it can be just:
write %foo.r enline read/string %foo.r

Thanks - that is a gem - should be docced :-)

Is there a home for R3 one-liners and idioms?


reline: func [file] [write file to-binary enline deline to-string 
read file]

reline: func [file] [write file to-binary enline read/string file]

reline: func [file] [write file enline read/string file]

(whoops, missed one)

New bug: http://issue.cc/r3/1830

Sorry, that one's intentional.

It's all part of the plan to make SELECT treat blocks, objects and 
maps more alike.

I've always felt that doing so was dumbing down select.  now I can't 
use select with/within parse, cause the different types will not 
be identified.   

has switch suffered the same fate?

Nope.

Now that I have internet again (it's been out for possibly a week) 
I'll check with Carl about this, but I remember code from 2007-2008 
that depended on this change, even from before SELECT was extended 
to objects and maps. It's used to make blocks that look like spec 
blocks for objects or maps act like objects or maps. SELECT does 
EQUAL? comparison, and SELECT/case does STRICT-EQUAL? comparison. 
So you can make it work by using SELECT/case. Note: Words now support 
case-sensitivity in blocks too, letting them be searched with FIND/case 
and SELECT/case.

>> select [a 1 :a 2] quote :a
== 1
>> select/case [a 1 :a 2] quote :a
== 2

fine!

I'll add this info to the ticket in a comment and dismiss it. It's 
actually more powerful than R2 :)

but not perfect as the case-sensitivity may cause problems...but 
I can live with it.

but not perfect as the case-sensitivity may cause problems...but 
I can live with it.

Not when you realize that this is consistent throughout R3, and just 
don't mix case when you don't need to.

The trick is that objects and maps are case-preserving rather than 
case-sensitive, so their fields get the same case as the first instance 
of the word. Plus, case-insensitivity is a little broken for a lot 
of languages right now (Unicode case is a complex problem).

Characters are case-sensitive

 is a pretty misleading description of the difference you've pointed 
 out between SELECT and SELECT/CASE, Brian. 


I would appriciate SELECT/STRICT over /CASE, /STRICT would even be 
usefull to imply case sensitivity, at least it seems better suited 
to express the semantic difference between the refined und the unrefined 
function call .

Same for 

>> find/case [a :a] quote :a
== [:a]
>> replace/case [a :a] quote :a quote a:
== [a a:]
>> alter/case [a] [:a]
== true


DIFFERENCE, UNIQUE and other "set-functions" obviously haven't been 
subject to change when the treatment of blocks, objects and maps 
converged:

>> difference/case [:a] [a:] 
== []
>> unique/case [a: a :a] 
== [a:]
>> union/case [a] [:a] 
== [a]
>> intersect/case [a] [:a] 
== [a]
>> exclude/case [a] [:a]
== []


In all cases, /STRICT would read at least as well as /CASE, if not 
better.