World: r3wp

if I have something like following:

event: wait [server client1 client2 ... clientx 0.001]
if block? event [event: first events]


and now I just maintain one port and its data, I wonder what happens 
with next 'wait? Remember I am not using wait/all, but still I am 
not sure, what happens if there is even waiting on more than one 
port?

... or simply without /all refinemet 'wait will always return only 
one of ports, even if data is waiting on multiple of them?

will not I loose data when 'wait is entered for the second time because 
of "if block? event [event: first event]"? Hopefully not ... or maibe 
wait without /all never returns a block, even if there is event on 
more than one port at a time?

If I remember right, you get only the first event, the others will 
still appear as long as you did not satisfiy them.

ok ... so what happens if there is still data on first port in the 
wait-list? will it always return that one? So it means that other 
ports will simply wait for maintanance, because first port in the 
wait-list is still receiving a data?

I do not know if you will get your first port again as the first, 
if you did for example just copy/part from it.

But imagine, that you do a copy on it, and new data arrives at the 
same time. This will probably raise a new event on it and this port 
will probaby the last in your queue of waiting events.

ah, thanks a lot ... so wait [port1 ... portn] does not anything 
in common with the order how 'wait returns the events? That is good, 
because otherwise I would maintain only first port, till the data 
would not stop appearing ...

Just what I think is a little bit annyoing, that sometimes you do 
not get the proper timeout, if you have a timeout value in your wait 
list  and many events.

Yes, I always thought that I got the ports ordered according their 
event time and not according their position in the event list.

I have to correct me.
I just tested this approach, and it does not look so good.
It always gave me the data from one port

ah, that is bad .... but expectable ... so I have to prioritise ports 
myself and probably always use wait/all ... but then - I am not sure 
I want to maintain them all at once ....

but maybe that is the only corrent aproach - to use wait/all and 
maintain data on all ports in a loop, then go for the next wait ...

or, to use random to pick ports randomly :-) .... but it is interesting 
that 'wait returns events according to wait-list order ....

anyway - I am doing very small util for my friend who programs our 
new board for kiosk system event detection and am having fun with 
it :-)

Just use small messages.

I gather every day messages in the tenth of thousands with peaks 
during the working hours and it is working so far.

yes, it surely will work ... I was just curious what would by the 
correct aproach for multiplexing engine ....

My test now revealed, that you will maintain the port you get as 
first, until it is empty, but then there is always some prioritize.

I just tested it with awake functions and this gave me data from 
two ports alternately.  Thanks god, that I use this approach since 
I heard about it. Probably the efficiency and the time granularity 
there is higher.

How can I avoid the scientific notation?
>> round/to (sm/n * sm/s * 0.9) 0.0001
== 9E-2

I want to get back: 0.09

>> round/to (sm/n * sm/s * 1.111231) 0.0001
== 0.1111

It seems that only for values < 0 the E notation is used.

I wrote the function for it. It was debated several times, but I 
do not remember if some solution came-up ...

robert the short but usless answer is don't use windows

other platforms do not have this behavior

should also be noted that other  langs i.e. perl exibit the same 
behavior on windows do it is apt to be an OS call that decides two 
decimal places is wau too heady for its users

that said it has been solved here and on the maillist several times

Robert, here is my solution used in Canvas:

form-decimal: func [n /local p d] [
	n: form n
	if p: find n #"E" [
		if d: remove find n #"." [d: index? d p: back p]
		if not d [if d: remove find n #"," [d: index? d p: back p]]
		if not d [d: index? p]
		either p/2 = #"-" [
			insert/dup n #"0" (to-integer skip p 2) - d + 1
			insert n "0."
		][
			insert/dup p #"0" (to-integer next p) - (index? p) + d
		]
		clear find n #"E"
	]
	n
]

>> form-decimal 9E-2
== "0.09"

Robert you can use the PRINTF wrapper function in rebol.org. It helps 
with all kinds of number formating.

Thanks a lot. But I really can't believe that this formatting stuff 
isn't supported by default.

>> form-decimal -0.099
== "0.-99"

rebol []
form-decimal: func [n /local p d s] [
	all [s: negative? n n: abs n]
	n: form n
	if p: find n #"E" [
		d: index? any  [
			all [ d: remove find n #"." 	p: back p	d]
			all [ d: remove find n #"," 	p: back p	d]
			p
		]
		either p/2 = #"-" [
			insert/dup n #"0" (to-integer skip p 2) - d + 1
			insert n "0."
		][
			insert/dup p #"0" (to-integer next p) - (index? p) + d
		]
		clear find n #"E"
	]
	if s [insert n "-"]
	n
]

can anyone refresh my memory as to how to insert new lines within 
blocks so that saved blocks are tidy?

I have searched the net, the update docs and have no found it.  ' 
:-/

see NEW-LINE

thanks !   I feel a little dumb ... hehe

strange, I just searched it again, and for some reason, now, new-line 
is the first thing returned in google... damn... last week it wasn't 
in the first 3 pages   > :-(

ahhh...  I had searched for "rebol newline" ,  searching is subtle 
sometimes.<Petra2PnrXmlResponse>

I knew that name would cause trouble.

how to substract two dates including time?

difference in recent versions will subtract dates and times

hmm, not sure .... is difference any different from date1 - date2

I mean - when substracting two 'now values, the time is not being 
taken into account ..

>> a: now - 125:00:00
== 19-Mar-2006/9:08:07
>> a - now
== -5    ;; five days
>> difference a  now
== -125:00:16    ;;; 125 hours
That's the difference!
>>

There must be no timezone present

why should be difference call different to simple usage of minus 
op?

it's a strange hack -- difference was originally for sets. So making 
it work for time is seriously non-orthogonal.

I hate those hacks

Maybe we need three types instead of two. date! time! and idate! 
or stamp!

difference hadles timezones too.