World: r3wp

ok, so parse is the root of my problem.  it specifically word binding 
for its keywords, but looks up all other words... which is what's 
causing the inconsistency in my code.

specifically *ignores* word

I don't see your point, what you say seems wrong, can you give us 
an example ?

in my code, I was getting different results for some keywords.  any 
is bound to global, but some isn't anything in rebol.

so since I can't create my rules using to-block (cause the parse 
rule is actully changing itself, using pre-bound rules... I'm stuck.

well, just bind yout rules in a specific context.
con: context [
	any: 'any
	some: 'some
	opt: 'op
	...
]

redefines the parse keywords as you want

so what I'll do is follow parse's functioning.  if a word maps to 
a function or a native, ignore it... I know my rules don't bind functions, 
cause they'd fail anyways.

yeah that would work too.

Maxim, BOUND? doesn't bind words to the global context - that was 
done by LOAD. Try this:
>> bound? first to-block "a"
== none

yes yes... that was understood later on.

I'm trying to hack up an UNBIND backport to R2/Forward though.

load is the core culprit here.  I didn't realize that all my rules 
where being bound at application load time, since every word is created 
by load initially.

That was one of the first things changed in R3. If need be you write 
your own loader for R2 that uses TO-BLOCK and then does the binding 
itself - LOAD in R3 is a mezzanine that does the same.

>> d: now/time
== 17:11:08
>> d/1
== 17
>> d/2
== 11
>> d/3
== 8.0
>> d/3: 0
== 0
>> d
== 17:11
>> d: now
== 23-Oct-2009/17:11:37+13:00
>> d/4
== 17:11:37
>> d/4/3
== 37.0
>> d/4/3: 0
== 0
>> d
== 23-Oct-2009/17:11:37+13:00
>> t: d/time
== 17:11:37
>> t/3: 0
== 0
>> d/time: t
== 17:11
>> d
== 23-Oct-2009/17:11+13:00

I can change the second component of a time! but now when it is part 
of date!    ???

but not ...

date doesn't have accessors for individual time values...

once you use d/time, its a new value of type time!

you have to use d/time: t  in order to push it back into the date.

inconsistent

I would have tought R3 would have addressed this, but it hasn't  
:-(

... I just checked

>> date: now
== 23-Oct-2009/19:31:27+13:00
>> type? date/time
== time!
>> date/time/3
== 27.0
>> date/time/3: 0
== 0
>> date
== 23-Oct-2009/19:31:27+13:00

What exactly is the explanation here??

I'm accessing a time value .. not a date value

date is a point in time... 
time is an amount of time...

they aren't the same thing.


you can have time values with 50 hours in them,  but you can't have 
50 hour days.

but I would like to be able to interact with the time within a date 
directly anyways myself.

Lets put it in curecode

yep. it might already be there as a request.

the issue probably is that if you did

date/hours: 50


its a logic error.  so how is it resolved? ... an error... add two 
days, two hours?

You can alter the day, month, year and zone ... just not the time

there is a bug in any case!!!  

>> t: 50:00
== 50:00

>> d: now
== 23-Oct-2009/2:40:09-4:00

>> d/time: t
== 50:00

>> d
== 25-Oct-2009/2:00-4:00

here it seems it added two days ... but didn't add the 2 extra hours 
!!

so, I guess the handling wasn't speicifically designed by the date 
object, and is simply a side effect of its internals.

(thats in R2 A90)

actually all i wanted to do was to round the time off to remove all 
the seconds

*R3*

but I have to extract the time, round it off and then set the date 
time value back :(

put it into curecode and add the above bug within the report... it 
will add to its relevance (and priority) within the post.

I don't hve the link close to hand ...

google rebol curecode... first link

Not for me .. I get vid extension kit!

nope .. not in google on those parameters

Let me try google.ca

I get the rebol doc base page for R3

Hmm... perhaps I need to remove "google" from the search!!

hahahahha

I pass ...

hum... that can take different meanings... hehe

  http://curecode.org/rebol3/

I don't wish to create an account ...