World: r3wp

So most countries did.

but would it be good/bad for rebol to support it? what if you are 
calculating astronomical data or similar

It seems, REBOL handle leap years correctly. The rule is, that every 
4. year is a leap year. Every 100 year isn't a leap year though, 
unless it's divided by 400. So 2000 was a leap year, 1900 wasn't, 
but 1600 was. And so on.

Henrik, good question!

Also, REBOL does not support negative years at all

>> 1-1--1
== 1-Jan-1999

well, that's pretty bad if you want to calculate astronomy stuff... 
maybe support for the julian calendar would be more appropriate for 
calculating extreme time periods?

I've always thought that consideration for science in REBOL was a 
little low

REBOL broadly follows the ISO-8601 date format (though not with the 
strict yyyymmdd format): years are 4 digit, positive numbers only. 
ISO 8601 is not designed for acheology or astronomy.

True astronomocal julian dates of course change day at midday not 
midnight -- so be really sure you want to use them.

Can anyone help me understand what is wrong below?  I am essentially 
trying to get Rebol to execute a ping or traceroute and record the 
result in a text file....

>> print read dns://www.google.ca
72.14.207.104
>> fp: open/new/lines %google.txt
>> call/console/output "tracert 72.14.207.104" fp
== 0
>> close fp
>> data: read/lines %google.txt

== ["close fp" "close fp" "close fp" "close fp" "close fp" "close 
fp" "close fp" "close fp" "close fp" "close fp" "
close fp" "close...

I have also tried using /wait...
	call/console/wait/output "tracert 72.14.207.104" fp
with the essentially the same result.

use this 
call/console/output "tracert 72.14.207.104" fp: ""

probe fp

or this

call/console/output "tracert 72.14.207.104" f %google.txt

sorry, it's wrong above.
Should be;
call/console/output "tracert 72.14.207.104"  %google.txt

don't use /console! /console means redirecting i/o to the rebol console, 
which conflicts with the other redirection you are asking for.

just call/output "tracert www.google.ca" out: ""

so close... thanks guys.

why this does not work?

  ff: func [a] [str: "a + 1" do str]
>> ff 2
** Script Error: a has no value
** Where: ff
** Near: a + 1

while following does?

>> ff: func [a] [b: a  str: "b + 1" do str]
>> ff 1
== 2

string is bound global. 'b too.

'b is global, as is not.

Yes, Volker is right, (and I made a spelling mistake.)

ok, before I read your replies I found it out too :-) can we somehow 
influence how 'do or 'load behave in that regard?

simply to bind 'do to the context of the function?

ff: func [a] [str: "a + 1" blk: bind load str 'a do blk]

bind the argument, not the 'do

just   do bind load str 'a

I thought bind is involved somehow :-)

I have one other question to bindology :-)

following works:

 >> kontext: context [a: 1 b: 2 c: 3]
 >> do bind [a + b + c] in kontext 'a
== 6

but I first tried:

do bind [a + b + c] 'kontext 


and it did not work. So is 'kontext itself a different context than 
in kontext 'a? :-)

do bind [a + b + c] kontext ;; works.

Or you can use this mezz.

with: func [object [object!] block [block!]] [
    do bind/copy block object
]


>> kontext: context [a: 1 b: 2 c: 3]
>> with kontext [a + b + c]
== 6

The WITH mezz was proposed by greg his implementation is backward 
compatilble, while the above is for 2.6 core. For completeness here 
is his implementation:

with: func [object block] [
    if object [do bind/copy block in object 'self]
]

uh, that is cute ....

will it be accepted to Core?

It is being considered.

do bind [a + b + c] 'kontext
In which context is 'kcontext bound? ;)

(the word. Not the content of the word! its quoted! ;)

well, the quote char was there simply by mistake and because I rewrote 
example according to initial syntax of do bind load str 'a, where 
'a is quoted too ;-)

is there a reason why 'NOW' does not have refinements for hour, minutes 
and seconds.?


I would have thought that it make sense to provide those refinements 
as well..since NOW will return a value that comprise date, time and 
GMT offset

Yes it is odd :
 now/time/second
** Script Error: now has no refinement called second
** Near: now/time/second
>> my-time: now/time
== 11:04:35
>> my-time/second
== 35.0

One for RAMBO?

submitted to RAMBO

An inefficient workaround :
>> mod now/time 0:01
== 0:00:21

Oops forgot  a bit :
>> to decimal! mod now/time 0:01
== 32.0

How about:

	t: now/time
	first t
	second t
	third t