World: r3wp

missing things count as as non-dirs too.

foreach f read %./ [ print [ "directory? " dir? f ]]

So, why does this work?

because it's in the current directory ?

yes. "dir? %synapse-chat/April/" would work too.

foreach f read dir: %synapse-chat/ [ ?? f either dir? dir/:f [ print 
[ "directory: " f ]][print ["file: " f] ]]

I guess the lesson is that you need to remember where you are when 
doing these things.

It's faster to check for final slash than to use DIR?, which, as 
Volker pointed out, makes an OS call.

Yeah, I moved to doing that.

This is from the REBOL command prompt under Mac OS X. Does REBOL 
behave the same under other OSs?
>> 31-12-16383
== 31-Dec-16383
>> 1-1-16384  
** Syntax Error: Invalid date -- 1-1-16384
** Near: (line 1) 1-1-16384
>> d: 1-1-0000
== 1-Jan-0000
>> d - 1
== 31-Dec-65535

Windows:

>> 31-12-16383
== 31-Dec-16383
>> 1-1-16384
** Syntax Error: Invalid date -- 1-1-16384
** Near: (line 1) 1-1-16384
>> d: 1-1-0000
== 1-Jan-0000
>> d - 1
== 31-Dec-65535

The Gregorian Reformation occured in September 1752. This is output 
from the UNIX 'cal' command:
$ cal 9 1752
   September 1752
 S  M Tu  W Th  F  S
       1  2 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30

Notice the jump from 2. to 14. Sep.!

And then some REBOL:
>> d: 2-9-1752
== 2-Sep-1752
>> d + 1
== 3-Sep-1752


Seems like the reformation didn't occur in REBOL-land. Maybe that 
should be noticed in the wikibook, Henrik?

it probably should. could you put it in? I'm a little strained for 
time

Also there is no year 0. So this is not absolutely correct:
>> 1-1-0000
== 1-Jan-0000
The year before year 1 is year -1 (or 1 BC).

I'm wondering, how REBOL handle leap year...

strange that this year was picked, since the gregorian reformation 
didn't happen everywhere at once

yeah, this is from UNIX 'man cal':

The Gregorian Reformation is assumed to have occurred in 1752 on 
the 3rd

     of September.  By this time, most countries had recognized the reforma-

     tion (although a few did not recognize it until the early 1900's.)

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? :-)