World: r3wp

I had the problem this week end... I had to install the latest kb 
update ... cause my computer was NOT switching the DST   :-(

cause the check mark in the time settings, only switches the "automatic" 
aspect of it... you can't manually set the dst to on or off.... which 
is darn stupid.

Ok, that works for me!

Thanks .. I'll tell all my users to move to Ontario

cool

hahahah

Oh, maybe the users have the wrong regional settings entered on their 
systems?

WindowsXP-KB942763-x86-ENU.exe  is the file that fixes tz on xp.

it superseeds older ones... (there are two previous kb I think... 
one in the 7 range and one in the 8 range IIRC)

I've passed on Max's instructions ... to reseed their clocks

I mean supercede their OS

if you search the net, you will quickly find the direct download 
link for that file from MS servers, without the need for WGA   :-)

got it my first search IIRC

So, Brian, the wiki is going to be ignored?

Brian, how do you do this: nforeach [a block1 b block2] [...]   without 
do/next or reduce?

it could as well be nforeach [a join block1 block2 b block3] [...]

I came across some code:

>> o: load {#[object! [a: 1]]}
>> source o
o: make object! [
    a: 1
]


Is this way of making objects documents somewhere? Does it work with 
other datatypes?

Gabriele, I don't think the wiki will be ignored. It's just that 
a wiki and an official manual are different things. Noone would sensibly 
expect a wiki that can be edited by anyone to be authoritative. But 
a wiki can fill in the blanks.

Wiki is becoming a "more organised mess", thanks to Kr. Bacon :-)

As for nforeach, you didn't catch that the first thing I would change 
would be to have the words and data in separate blocks, to make generation 
of the data and pipelining easier. The words are an artifact of the 
call to nforeach, not part of the data. You need DO/next to implement 
the old version, not a version that I was talking about. Any REDUCE 
would be outside the function.

Geomol, yes, but not all datatypes, and expect binding issues with 
object! and function types.

Pekr, Bacon has been doing good work, and the wiki is getting prettier 
:)  But there have been a few factual errors on those pages...

NFOREACH would take 3 arguments, not 2, just like FOREACH.

I'm not sure about the name though.

BrianH: I don't agree. While he is doing really a good work, he also 
completly ruined some stuff. He restructured Carl's docs so that 
they don't make much sense and he intermixed it with Gab's former 
VID docs, not understanding VID3 and VID 3.4 are different things. 
That fact alone is totally confusing ...

I can help him to point out few things, but dunno how to contact 
him ....

I'm not assuming it's a him until I see a full name. The factual 
errors can be cleaned up as the GUI design progresses, no worries. 
In the meanwhile we have a new doc structure and examples of formatting 
to copy, so I'm grateful. This does illustrate my point about the 
difference between a wiki and a manual though.

Factual fixes I can handle (with available time). Formatting fixes 
are much more difficult - don't know Wikimedia. Not the docs guy 
though.

Brian: i was not comparing wiki to docs. I was comparing wiki to 
chat. If i need to restate do in chat, why is the wiki there?

Brian: I don't like it that way as then you have to keep in your 
mind the relationship between words and blocks; furthermore, please 
name me one case where you wouldn't need reduce. A function that 
*always* needs reduce is badly designed. :P

Gab, sorry, I thought you were talking about DocBase (as others were) 
rather than the parse proposals. The reason I mentioned the chat 
is because you keep bringing up the DO operation as if you are trying 
to convince us of its importance, but we all agree with you so it 
doesn't help. I was trying to point you to a forum where trying to 
convince someone about a parse proposal would have some effect.

As for the Parse Proposals wiki, I'm afraid it will need some cleaning 
down. I kept trying to tell Peta the rules Carl set up, but Peta 
kept ignoring them and going into great detail about parse theory 
and such. Half of the contents of that page are going to have to 
be moved to other pages, and I'm probably going to have to summarize 
the best of the proposals to Carl if we want to convince him to implement 
them.

You have a good point about the nforeach reduce thing, but I am not 
convinced that giving up the ability to generate the data in other 
functions is worth it. I usually don't like to see DO/next in mezzanine 
code anyway: DO/next is usually a sign of a function that doesn't 
work in a REBOL-like way and has too much overhead to use. However, 
I still want Carl to fix DO/next in R3 - it doesn't work at all at 
the moment, and there are some proposed functions that can't be implemented 
without it.

to me do/next is just a sign of a dialect :-)

maybe too many dialects is bad, but i personally think it's worth 
trying.

I have a 'case like function that uses 'do/next

Like case, but inverted (performs the block if the result is false). 
 It'd be easier to implement using [block block] or [paren block] 
pairs, but would not be as readable - imagine the same with 'case 
?

Chris, that sounds like a good job for DO/next. It also sounds like 
a function that would be replaced by CASE [NOT ... when the code 
is being optimized. REBOL programmers can be pretty ruthless when 
it comes to hand-optimization, so one of the goals of R3 is to make 
the mezzanine functions powerful and efficient enough that they will 
actually get used rather than optimized away, and to make native 
the functions that need to be. The hope is that the users of REBOL 
can just use functions and trust that they will be efficient, rather 
than having to manually inline code all of the time.

Yey to that!

Is there a script around that decodes entities such as & etc 
?

rebol.org   web-to-plain.r  handles a lot of them.

http://box.lebeda.ws/~hmm/rebol/htmlentities_latest.r

(converts to utf8)

thanks.

Is this logical behaviour? (Has it been discussed before?)

>> #"a" = 97
== true
>> switch #"a" [97 [print "found!"]]
== none

Inconsistent, perhaps.  Perhaps the first case shouldn't be, but 
can be extra useful (as can #'a" + 5)

I'm not sure about you're example but this would definitely seem 
to be a bug:

>> #"a" == 97
== true

The R3 behaviour is: 

>> #"a" == 97
== false


>> #"a" = 97

== true

I get:

>>  #"a" == 97
== false

in R2...

The implicit type convesion in evaluating #"a" = 97 is consistent 
with the help text :

>> ?
 =
USAGE
:
    value1 = value2
 

DESCRIPTION:

     Returns TRUE if the values are equal
. 
    = is an op value
.

ARGUMENTS:

     value1 -- (Type: any)

     value2 -- (Type: any)