World: r3wp

What happens if someone changes the machine's clock while you wating 
for a length of time ?

you -> you're

graham, the only solution to that would be to wait, say, 10 seconds 
at a time, and check. but it really depends on the application...

re; wait till time, isn't that       add multiply subtract then/date 
now/date 86400 subtract then/time now/time


then - now * seconds per day + delta hours?   Negative time! possible, 
which it seems wait takes as zero anyway.

btiffin, just use difference now then

(or difference now/precise then if necessary)

Thanks Gabriele;  I knew there was a more concise method of getting 
at time!  from date arithmetic, but I got sidetracked when the google 
search wanted to show me COBOL data arithmetic.   ;)  Can't ever 
know enough COBOL, err, aaah, REBOL.

This hangs.

in R3

This?

p: make op! [[n m] [n * m]]   3 p 4

Wrong group, but good to know. MAKE op! clearly needs to do more 
parameter checking. CureCode it.

There's no reason to expect that to work, btw. An error should be 
thrown by MAKE.

why?

Because ops aren't mezzanines - they redirect to other functions.

if not divisible-by-any? n primes
if n is-not-divisible-by-any primes

if they could be made we could use this kind of grammar

There is no known spec argument for MAKE op! that is supposed work. 
You're spposed to use the OP function.

User-defined ops are a planned feature, not a currently working feature.

Thanks

How many people are in here?

It's not a bad idea though. Still, CureCode that code you posted 
above. It's a serious bug that MAKE doesn't trigger an error there.

Anybody knows what's this about?

http://www.rebol.net/cgi-bin/rambo.r?id=-4786&

Well, I do not think so...

sounds like something for a private project?

Product is command yet he talks about clicking on icons .... so he's 
confused!

I'd guess that if it's a product written in REBOL, the author is 
likely to hang out here... :-)


I'm going to leave it there for a couple days in case anyone needs 
it, then i'll delete or dismiss it.

It's not a RT product .. so I'd delete it

do you know it's not a RT product?

with 99.9999% certainty

as cmd is a non gui product

that does not seem a lot of evidence to me... :)

don't you have the email of the poster?

I do, but that's only useful to the author of the program in question, 
no?

Found a couple RAMBO tickets dated back to 13-May-2006 related to 
the double evaluation of lit-words:
http://www.rebol.net/cgi-bin/rambo.r?id=4100&
http://www.rebol.net/cgi-bin/rambo.r?id=4101&


The tickets suggest, USE might be the problem, but isn't it SAME? 
that's the problem here? See the following R2 code:

>> a: first ['word]
== 'word
>> b: 'word
== word
>> strict-equal? a b
== true
>> strict-equal? :a :b
== false
>> same? a b
== true
>> same? :a :b
== true


I would expect all 4 to return false, but with double evaluation 
of lit-words, the last should still be false.

Given that lit-words are supposed to be active values, all but the 
last make sense.

Don't forget R2's bugs related to double evaluation of words, which 
are definitely not supposed to be active values.

Never mind, http://issue.cc/r3/1434is outdated: 2.7.8 doesn't have 
the double evaluation bug for words anymore. I wonder when that was 
fixed?

Forget it, it does, just ran some test code.

im happy to see u guys cleaning up such old tickets. u keep the hope 
alive that rebol won't die :)

Rebol will never die: https://picasaweb.google.com/lh/photo/ELKDZn84LgDbQJJ4Fvo4Aw?feat=directlink

hahahahahah

:-D Actually, REBOL sounds a bit like a cartoon superhero.

i want from that crack too, maxv! ;D

*.rip
requiescat in pace ?

I think the hero is asleep in the ice castle for the next thousand 
years

Anybody can alert the actual developer here?

http://www.rebol.net/cgi-bin/rambo.r?id=-4803&

I'm not clear on the issue. 1.3.61 was just a test release, wasn't 
it? And is there a UPC lib they're using that requires rebcode or 
something? i.e. what pages are being printed?

It seems to be a user of some random REBOL app. The version number 
may be the version of the app

Didn't we have another bug report from the fed.us people last year? 
I think it also was about some problem with their internal app, misfiled 
in the wrong bug tracker.