AltME groups: search

ok, now another question. Let's say that currently you know, that 
there is http://www.rebol.com/RSs/calc-time.r, so you know direct 
path ... how much penalty will there be with Chord, if you do something 
like send-message [calk-time-:-at-rebol-com], simply if it will start 
to look up?

the time required for a look up depends on the number of nodes.

dinner time, later!

as Carl says, it's so hard to make it simple... i guess i'll run 
out of time and just do something that works.

Gabriele, if I'm online at the time, you can ask me.

anyway it's going much better than the last time... though i'd prefer 
to have it running on udp (it's much faster)

It is still running...I drag selected text...maybe printing the time 
would help tell it is alive easier for testers...

Perhaps in time we'll see a *real* IOS based on a P2P stack on top 
of REBservices. Didn't you call that IOS-NG ;-)

Looks like i don't need that util after all.  My host located a 500Mb 
movie file uploaded by a hacker a couple of weeks ago .. must be 
at the same time my site got defaced.

I'm playing around with mediawiki .. a great little wiki.  Even has 
preferences for your time zone so that you can see when edits were 
done according to your own local reference.

But if you want to access a mysql server, the cgi script loads each 
time, right?

Well, I wonder what has less overhead.. reading a 23kb protocol with 
each call, or taking the time to do a tcp call?

Forced to reduce the number of iterations to 100 for mysql sake.. 
and even then it would choke 50% of the time.. results.. 


Reading the DB used mysql-protocol.r with join mysql://.. localhost 
{select email from table where name='name' }
Reading the file used a: load %file.txt, b: select a 'email
mysql - 1.35 seconds (using time/now/precise

file - 0 seconds (timestart - 18:35:25.531, timefinish - 18:35:25.531)


Conclusion.. no contest.. loading and selecting from file wins hands 
down.

Graham, if i need to wait for a response, then i would need to add 
that time to the total for mysql.

Took about 6 mins to move the directory.   So it appears to be a 
trade off.
Benefits of using files... 

- much more flexible (ie: a 10mb binary file in a DB is not a good 
idea)
- easier to manipulate.
- magnitude faster access time

the magnitude faster time breaks down pretty quickly when you need 
to retrive a file based on it contents not its title

Time to delete before the wife sees them!

Date: Sun, 23 Jan 2005 17:03:16 +0100
From: Bryan Rasmussen <[bry-:-itnisk-:-com]>
Reply-To: [rebolist-:-rebol-:-com]
To: [rebolist-:-rebol-:-com]
Subject: [REBOL] Intro to Rebol article for DevX



Hi, i've been asked to write an intro to rebol article for devX, 
a task for

which there are any number of people better suited and for which 
i wouldn't have

the time anyway. So if anyone is interested in writing this i can 
direct the

devx editors to you as i still follow this list well enough to know 
who knows,
even if i hardly ever use the language anymore. 


-- 
Bryan Rasmussen

I quoted the part above as I too have not managed to get my thank-you 
notes out ... but by a somewhat greater period of time :(

I like Carl's code - I can't remember the last time I used the 'unless 
function.

I do it all the time to optimize my scripts these days

unless is a nice addition to standard rebol, I know use it alll the 
time.

it' not my first license.key. I had also problems and got a new key 
some time ago.

There should be a way to vote for tickets, to help RT put a measure 
of weight on them. I also think the same person should be able to 
revote more than once, lets say once per month, this helps weed out 
issues which are long standing and are a big issue for one person. 
 otherwise, you cannot really differentiate what is continually causing 
concern for you over time.  persistent bugs are the most important 
ones IMHO.

Hmm.. I've often considered whether to immediately submit a post 
of dubious importance. It would be nice to reliably delay my submission 
by six months or so. Maybe by that time the submission would become 
irrelevant because of a fix or new rebol version etc, and by not 
posting it I am keeping others free from distraction. But I am not 
using calendar software to remind me. (One of my goals this year 
is to start using calendar software.)

I'm not sure I'd change the time... the above, as explained by Gabriele 
is what is happening, and its very logical... the dot is consistent. 
and fixes the inconsistency of  0:10:0 and  0:10 being the same thing.

if we wanted to support decimal minutes and hours, I'd suggest that 
time then support using decimal values in all parts of a time like 
so:

0:.1:00
0.2:00
0:0.25:0.124


then we'd be forced to write 0:0:0.124 and the inconsistency would 
disapear.  a part from the above discrepancy in that you don't have 
to supply seconds

Regarding the decimal point in time value issue - my POV is, that 
if users find it natural, then there is no need to change the behaviour

I find the current time is adequate in all scripts I've done so far... 
it just has to be documented... if it currently isn't

view layout [area mold system]

the text would include this  area the  next time, then include a 
text  which inlcudes the lastlast text and so on?

perhaps you could fix mine at the same time :)

i was just testimg how far the (at the time alleged) bug went

I show you something from my article:

a: b: charset [#"a" #"b"] c: insert charset [#"a"] #"b
identical?: func [
    {are the values identical?}
    a [any-type!]
    b [any-type!]
    /local var var2
] [
    ; compare types

    if not-equal? type? get/any 'a type? get/any 'b [return false]
    ; there is only one #[unset!] value
    unless value? 'a [return true]
    ; errors can be disarmed and compared afterwards
    if error? :a [a: disarm :a b: disarm :b]
    ; we need to be transitive for decimals and money
    if any [decimal? :a money? :a] [
        return found? all [same? a b zero? a - b]
    ]
    ; we need to be transitive for dates

    if date? :a [return found? all [same? a b same? a/time b/time]]
    ; we need to be able to compare even the closed ports
    if port? :a [return equal? reduce [a] reduce [b]]
    ; our function has to work for structs
    if struct? :a [return same? third a third b]
    ; we can have something stronger than SAME? for bitsets
    if bitset? :a [
        unless same? a b [return false]
        if 0 = length? a [return true]
        unless equal? var: find a 0 find b 0 [return false]
        either var [
            remove/part a 0
            var2: find b 0
            insert a 0
        ] [
            insert a 0
            var2: find b 0
            remove/part a 0
        ]
        return var <> var2 
    ]
    same? :a :b
]
identical? a b ; == true
identical? a c ; == false

Nice one. I seem to remember a bug like this a long time ago, though.

This seems like an easy fix to someone who has the time, the SDK 
source and the inclination.

I'm just missing the time (and the need).

BUT the default for ssl:// is LF! that is a bug i reported some time 
ago. (it created problems for https:// too)

Anton: I thinl you're right to add it to rambo

Brian: It's in Core 2.5.6 so I'd guess it was some time ago.

>> make date! [0 0 0]
== 30-Nov-65535
>> make date! [0 0 1]
== 30-Nov-0000
>> make date! [75 0 1]
== 13-Feb-0001
>> make date! [01 0 75]
== 1-Dec-0074


sorry, but these make dates are just funny. 0 becomes a negative 
offset in time in some instances... like the last.  should I RAMBO 
this?  I would expect make date to accept only one 0 value, being 
the year... any other 0 makes no sense.

I realised when mimicking the behaviour of DO EVENT, that the reason 
the target face is not given is because its impossible to know at 
the time DETECT is called. Events travel down through the face hierarchy 
through the DETECT functions, the evaluation of which could have 
an effect on the result. The DETECT function can block events or 
allow them through, depending on the result they return, which is 
programmable and therefore dynamic. So a DETECT function higher up 
in the face hierarchy which is evaluated before a DETECT lower in 
the face hierarchy cannot know which is the target-face, because 
the result of the lower DETECT may change the target-face.

In most cases it is sufficient to know which face is under the mouse 
cursor at the time of the detect event. Coded as a mezz this is pretty 
slow.

I use it all the time ...

i don't have time for it now :)

I see. Unfortunately it seems I hit it close to every time I do a 
specific operation, but I have no time to debug it...

Clear -- It's probably a good idea for this reason: the block will 
grow to its maximum size after repeated uses, and so saves time in 
memory allocation / block extension.
May be a bad idea if that max size is causing problems :-)

I don't know, but I've seen similar allocations that continue over 
time and then seem to stop.

never? maybe it would be good to have some way how to force rebol 
to release what does not require from time-to-time. That's probably 
the reason why my nonstop running server requires 5MB instead of 
3MB when was started.

I just think there should be better clarity on what are do's and 
don'ts in terms of how to preserve memory and have a stable application 
at the same time. Some apps of mine never eat more than 3-5 MB RAM, 
while others eat 250 MB RAM, and I don't know what causes it.

next bug fix - no idea. depends on Carl's time.

i actually want to  try that out before july... but not sure i'll 
have the time.

note, i didn't say "won't be fixed", i said that i find it unlikely 
that Carl will spend more time on 2.7 at this time (ie before july 
15th r3 release).

Doc, ah yes, I think I agree because I seem to remember doing the 
above sequence myself at some time.

On windows platforms, you'll get the infamous DOS window flashing 
when executing an external CGI ! It's just a matter of 1 flag to 
correctly set in 'call C source code, if you're really annoyed by 
that, ask RT to fix it asap (for 2.7.6 that would be good)! ;-) I 
may reimplement completely call command in REBOL, but it would be 
a big waste of time and energy...it should be a 10 minutes fix for 
RT. Addind a time limit to 'call would be a good thing too, it would 
also avoid me the reimplementation of 'call to add such feature....
 - DocKimbel

Anx chance of getting above fixed? Should we rambo it?

the main thing is, that changing rambo (i don't know the code) would 
take me more time (especially testing and making sure we're not going 
to lose data) than the 20 seconds or so it takes to delete the spam. 
So I never get to study the code and see what can be done...

I've searched RAMBO about a WAIT inconsistency : the dictionnary 
says that "If the value is a DATE/TIME, wait until that DATE/TIME", 
but date! are not accepted as argument (both directly or in a block). 
If this a known bug? I can't find it in RAMBO.

doesn't it mean a time value?

Being able to wait for specified date/time would be great for doing 
cron

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

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.

Seems it was also the forest service last time. I don't really remember 
how this was resolved back then, though.

The people in Syllable have also gone through this process. Eventually 
we each decided that instead of spending all our time getting Linux 
to work, we could also spend it building a complete new system

I thought that Syllable uses it's own kernel AlthOS, right? What's 
the role of Linux (Linux kernel?) than? You mention Linux from time 
to time but why do you need it?

Further, a lot of nonsense happened and I had to spend a lot of time 
on other things, such as creating alternatives for disappearing websites

It wasn't very usable at the time, though. It has fundamental and 
practical problems

yes, otherwise the time etc won't keep

I'm out of time for working on Syllable, but I'll squeeze some things 
in here and there

I hear that Syllable Desktop can run for a week on VMware without 
loosing time, so I don't know what the problem with Fedora is

Hm. A Syllable colleague says loosing time is basically through a 
heavily loaded machine

Do you have time problems on all VMs?

#!/sbin/rebol  -qw
Rebol [
 file: %update.r

 purpose: {Update the system clock based upon the nist.gov time server}
 author: {Graham Chiu}
 date: 15-Apr-2007
]

get-nist-correction: func [/local nist-time cpu-time mjd hms] [
 nist-time: read daytime://time-a.nist.gov
 cpu-time: now

 parse/all nist-time [skip copy mjd 5 skip 2 thru " " copy hms 8 skip]
 nist-time: 17/Nov/1858 + to integer! mjd
 nist-time/time: to time! hms
 nist-correction: difference nist-time cpu-time
]

forever [
 if error? set/any 'err try [
 print [ "Current time was: " now ]
 current-time: now + get-nist-correction
 print [ "New time is: " current-time ]

 s: rejoin [ "date -s " {"} current-time/month "/" current-time/day 
 "/" current-time/year " " current-time/time {"} ]
 probe s
 call s 
 ][ probe mold disarm err ]
 wait 00:02:00 ;; wait 2 mins
]

the other way is just setup a time server on the host os and use 
the daylight protocol

Saved me time :)

Sounds like it costs more time to configure all the pieces (and keep 
them running on time) then to write it in REBOL

Porting and configuring Dovecot and RebelBB will take some time, 
anyway

do you have time for a day job?

Haven't had for years, but will have to make time for it now

It will be extra work to figure this out, so it will take me some 
more time

Various Linux distros have a hard time supporting the EeePC, too

It's taken a long time this time, but we released Syllable Desktop 
0.6.6

So it looks like for some time to come, you will still need X11 for 
hardware accelerated OpenGL

I really wish, I had more time, so I could also try this out. Well, 
hopefully some day, I'll see this in action.

going OT we are in syllable group, and I think now is not the time 
for a license debate.

Oh, that's Mike Saunders, our regular reporter, but this is the first 
time I see him writing here

I'd like to have more time.

A screencast would be nice. I don't have time for it, though. It 
would be a nice thing for someone to contribute

The situation with Syllable Server is much easier, although at the 
same time a bit more difficult. It doesn't have an installer yet, 
so although the installation procedure is clear and straightforward, 
it's manual. But that also means you can move the installation package 
from anywhere to anywhere

For REBOL people, Server is the only Linux distro that caters to 
their needs, shipping a collection of REBOL software preconfigured, 
including Boron and ORCA. The latter are hard to try out when you 
have to install them yourself, and because most REBOL people come 
from Windows, they generally have a hard time installing and configuring 
a REBOL server when they want to use Linux

MMmm pitty... i realy liked to kick some asm code around in rebol.. 
it all looked realy orgenized at the time..

carl answer was, we need this RSN... no time for this. (others agreed, 
sort of)

so my answer was, well, let's improve vid, and at the same time develop 
the new system, so that we have vid (with resizing, liquid-alike 
stuff, more styles etc.) for 3.0 (or at worst 3.1) and we can have 
the new system later on.

probably most will run... but it's hard to say at this point. it 
depends on the amount of time we have. keep in mind reichart is taking 
my and richard's time too.

Oldes - but maybe RT has real concern here. You can imagine there 
will be many requests for furhter improvements, bug fixes, etc., 
so that we can "steal" time from RT's resources and hence View could 
get even more postponed ... dunno ...

even if there are only a few... it's still some time subtracted from 
other stuff. so i can't promise anything about that, especially since 
i don't know the details of everything.

Carl would have to visit us here from time to time, to get us a better 
answer :-)

There's something wrong with my compare with a 1MHz 6502. I counted 
the number of cycles in the inner loop and found 17 cycles. A 1MHz 
6502 can then do 1'000'000 / 17 * 40 = 2'352'941 loops in 40 seconds. 
But the BeebEm emulator made 16.7 mio. loops in that time. It should 
have taken 285 sec. So programming in rebcode is more like a 107 
MHz cpu in this test.
(It's probably not correct to measure it this way.)

Steeva, about flags: e.g. the zero flag Z (bit 1 of P). In stead 
of that I set it each time A, X or Y become zero, I could save any 
of those (A, X or Y) in a variable, and then test on that var and 
set the flag correctly, if and when the flag is actual used. Is that 
what you mean?

i give you an example with the TAX opcode

; updating flags in real time

label TAX
seti X A
eq X 0
either [or P 2] [and P 253]
seti i X
and i 128
eq i 128
either [or P 128] [and P 127]
bra continue

;  delay the calcul of flags

label TAX
seti X A

or maskA (2 + 128)     ; remember that we have to recalculate zero 
and negative flags using A, but don't do it now
bra continue

I had a problem some time ago showing PS files, I produced. I think, 
it was some cache.

rich text has some bugs, which cyphre is able to fix once he gets 
time, so I hope this will be possible to hook into. i.e. it's not 
a closed part that we can't touch.