r3wp [groups: 83 posts: 189283]
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

World: r3wp

[Core] Discuss core issues

Tomc
22-Oct-2005
[2432x2]
which means the server cannot take advantage of the fact the body 
is the same on all the messages and just spam/virus filter it once.
(having this issue on a  list of 2500)
Graham
22-Oct-2005
[2434]
If you want, you can write your own send command that does what you 
want.
Gabriele
23-Oct-2005
[2435x3]
Let's make this clear: SEND is not an email client. SEND is a function 
to send email. If it was an email client, it owuld just show a window 
with the ability to send TO, CC, BCC and so on, with a send button 
in it...
what send does is: taking a message, and sending it to the list of 
recipients you provide. That's what any MTA does too.
the user interface for mailers, though, of course do more than that. 
TO, CC and BCC are part of the user interface.
Graham
23-Oct-2005
[2438x2]
Hmm.  SMTP allows the sender to make multiple RCPT TO commands before 
sending the body of the message once - which then gets sent to the 
addressees of the RCPT TO.
This is how your email client would implement a CC or BCC.
Gabriele
23-Oct-2005
[2440]
yep, just like SEND.
Graham
23-Oct-2005
[2441]
I don't know how 'send works ... but I assume it does only a single 
RCPT TO ?
Gabriele
23-Oct-2005
[2442]
depends on refinements. i don't recall if it does one with a list 
of emails, or several with one email address each.
Graham
23-Oct-2005
[2443]
I think it sends it multiple times.
Gabriele
23-Oct-2005
[2444]
SEND with multiple recipients sends a copy to each recipient; SEND/ONLY 
sends the same message to many recipients
Izkata
23-Oct-2005
[2445x3]
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)
Graham
24-Oct-2005
[2448]
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.
Anton
24-Oct-2005
[2449]
>> to-date "1/10/1040"
== 1-Oct-1040
Graham
24-Oct-2005
[2450x2]
but what I want is last century !
Many languages have a way to set the window in which dates work.
Volker
24-Oct-2005
[2452x2]
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 :)
Graham
24-Oct-2005
[2454x2]
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.
Volker
24-Oct-2005
[2456]
I guess that step must be made in the conversion, to check if date 
is 2 or 4 digits.
Graham
24-Oct-2005
[2457]
I guess when it was coded, it was set to make everything the current 
century .. after all Rebol was invented last century.
Volker
24-Oct-2005
[2458]
if you know its 2, you can then make a quick check. if date > 2035 
[date: date - 100]
Graham
24-Oct-2005
[2459]
yeah ..
Volker
24-Oct-2005
[2460]
so we need a to-date/window ? How to deal with different formats?
Graham
24-Oct-2005
[2461]
what different formats?
Volker
24-Oct-2005
[2462]
thought to-date understands ultiple formats. if its always */year 
its a short check.
Graham
24-Oct-2005
[2463]
yes, I thought using /year is what is needed.
Volker
24-Oct-2005
[2464]
there are some more mentioned in the word-browser. if always "/", 
if 2 = length? find/last "/" ..
Graham
24-Oct-2005
[2465x2]
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
Volker
24-Oct-2005
[2467x2]
explicit 4 digits are not necessary?
but quick solution :)
Graham
24-Oct-2005
[2469]
Since we don't have control over the field .. users will enter 2 
digits sometimes
Volker
24-Oct-2005
[2470]
i mean user can enter 2025 explicitely. that gets 1925.
Graham
24-Oct-2005
[2471x3]
well, I see ... he made a mistake.
In my application .. you are not allowed to deal with dates too distant.
:)
Ladislav
24-Oct-2005
[2474]
this solution:

>> 24/10/55
== 24-Oct-1955
>> 24/10/54
== 24-Oct-2054
Volker
24-Oct-2005
[2475]
ok, than this is enough. but people get older in the future! (hopefully)
Ladislav
24-Oct-2005
[2476]
is considered "standard", but it doesn't look ideal for medicine 
applications
Anton
24-Oct-2005
[2477x3]
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.
Graham
24-Oct-2005
[2480]
Hey, living users won't have to worry about the next century!!
Volker
24-Oct-2005
[2481]
i would use grhams solution and feed what rebol sees back into the 
input-field. so user sees something is wrong.