World: r3wp

SEND with multiple recipients sends a copy to each recipient; SEND/ONLY 
sends the same message to many recipients

I don't see the use of using /only, really...  With /show, I see 
all recipients whether or not /only is there - and without /show, 
with /only, it won't show any email address, and without /only, just 
it only shows the recipient.

(without /only, without show for that last one)

(/show)

Quick question .. how do you set the century to-date defaults to 
?

>> to-date "1/10/40"
== 1-Oct-2040

is not what I want.

>> to-date "1/10/1040"
== 1-Oct-1040

but what I want is last century !

Many languages have a way to set the window in which dates work.

WOuld own handlling work? Where do you get the dates from? always 
"1/10/40"?

(i guess there is nothing inbuild, but would be pleasanly surprised 
if i am wrong :)

I want to automatically set a window so I can deal with dates - for 
birthdates and appts.

If I have to, I will have to write my own mezzaine - just was hoping 
that Rebol had something built in.

I guess that step must be made in the conversion, to check if date 
is 2 or 4 digits.

I guess when it was coded, it was set to make everything the current 
century .. after all Rebol was invented last century.

if you know its 2, you can then make a quick check. if date > 2035 
[date: date - 100]

yeah ..

so we need a to-date/window ? How to deal with different formats?

what different formats?

thought to-date understands ultiple formats. if its always */year 
its a short check.

yes, I thought using /year is what is needed.

there are some more mentioned in the word-browser. if always "/", 
if 2 = length? find/last "/" ..

to-date: func [ value /local tmp ][ tmp: to date! :value if tmp/year 
> ( now/year + 10 ) [ tmp/year: tmp/year - 100 ] tmp]

this ensures that years more than 10 ahead get changed

explicit 4 digits are not necessary?

but quick solution :)

Since we don't have control over the field .. users will enter 2 
digits sometimes

i mean user can enter 2025 explicitely. that gets 1925.

well, I see ... he made a mistake.

In my application .. you are not allowed to deal with dates too distant.

:)

this solution:

>> 24/10/55
== 24-Oct-1955
>> 24/10/54
== 24-Oct-2054

ok, than this is enough. but people get older in the future! (hopefully)

is considered "standard", but it doesn't look ideal for medicine 
applications

I would require users to enter four digits. Get them used to being 
precise.

sorry "we don't have control of the field..."

mmm.. so you have to guess. A bad situation.

Hey, living users won't have to worry about the next century!!

i would use grhams solution and feed what rebol sees back into the 
input-field. so user sees something is wrong.

Ladislav, how did you know the cut off date?

middle? 50 years?

ahh...

well, I think we need an adjustable window

adjustable window - you may put it to RAMBO as a request, but I am 
not sure if you succeed

would something in system/options be a big effort?

I thought RT wanted to get into medical applications :)

OK, try to put it there and let's see :-)

system/options sounds appropriate

currently it is -50 to 50 but even -100 to 0 isn't "safe" (ever heard 
anecdotes about inviting over 100 people to elementatry schools?)

I think it is importan if you get dates as strings, you dont know 
after the converion if it was 2 or 4 digits. makes the smartness 
of to-date useless, going back to self-made conversion. OTOH in most 
cases defaults are enough, but so are english month :)

main point may be, some dates cant be in the future, like being born.