World: r3wp

Is there a useful DIFF-type function anywhere that extracts the substring 
differences between strings?

>> text: "redblueyellow"
== "redblueyellow"

>> take/part text 3
== "red"

>> text
== "blueyellow"

IIRC Gabriele and Bohdan both have provided diff-style scripts for 
R2 in the script library.

Strictly
 per current behavior of R3, just tested:

- For decimal! it means more precise comparison (17 digits versus 
15 by default, also with EQUIV?).
- For string types it means case-sensitivity.

- For word types it means case-sensitivity and binding (only binding 
for EQUIV?).
- For block types it means strictly equivalent contents.

This seems reasonable to me, but it should be documented. I'll review 
the ticket mentioned above.

Thanks Brian, much appreciated.

I updated the docbase "comparisons" page to reflect this: http://www.rebol.net/wiki/Comparisons#EQUAL.3F

Added a comment to that ticket, with a suggestion for doc strings 
that fit the limit:

- STRICT-EQUAL? "Returns TRUE if the values are equal and of the 
same datatype, case."

- STRICT-NOT-EQUAL? "Returns TRUE if the values are equal and of 
the same datatype, case."

Nice, consise, and 68 and 69 characters, respectively, no problem. 
You can even change "datatype, case" to "datatype & case".

eh?

STRICT-EQUAL? == STRICT-NOT-EQUAL?

Sorry, replace TRUE with FALSE (as I did in the comment).

That was a typo above.

why do we need both?

Because != and <> need a function to redirect to.

And you can use STRICT-NOT-EQUAL? as a function value if need be, 
but not NOT STRICT-EQUAL?.

maybe we should dispense with all infix operations

make life very messy!

People like them. And they'll like them more when you can make user-defined 
op! functions.

Returns TRUE if the values are equal and of the same datatype, case.

That ending doesn't read very well to me.

Like I said, ", " could be replaced with " & " and it would do as 
well. Would you like that? Either is considered standard English...

Would it be possible to make R3 a Windows-Host-Script language?

Yes, but it wouldn't be useful unril we have user-defined datatypes 
(to wrap the OLE objects in).

unril -> until

There might be a workaround for that with extensions, but I'd wait 
until we have the next host kit before making an ActiveScripting 
host, so we can use embedded extensions and the revamped command! 
type.

Ok. IMO we need callbacks as well. And a good documentation how this 
will be integrated into the event system.

The plan has always been to implement callbacks and integrate them 
into the event system through devices.

But you never know until it happens.

Is there a way to get the literal of a function parameter? 

Example:
 "my-funct my-data" and "my-funct: funct [parameter]..."



Can I get 'my-data within my-funct?

In R2 I could write: in object 'self, but no longer in R3. What's 
the equivalent in R3?

Those things shold be defined by Carl ASAP, as those are pretty fundamental. 
We talk about u-types for ages, but noone knows, how in fact those 
are they going to be implemented or how they will work in the end. 
Ditto for callbacks :-)

BIND? - and it works in R2 as well.

That's the equivalent to in object 'self, bind? object.

As for your first question, try a lit-word parameter like this: my-funct: 
funct ['parameter]...

Unless you want no evaluation at all, not just for words, then use 
a get-word parameter. Yes, that's an awkward way to refer to it - 
it's already been reported.

In R2 I could write: in object 'self, but no longer in R3. What's 
the equivalent in R3?

 - I do not understand all that "harakiri" going on in R3 with 'self. 
 Nevertheless, the expression:
    first bind [self] object
works

Self is still there but within its own context which is the way it 
should be.

Nevertheless, I think, that the fact, that
    first bind [self] object]
works, while
    in object 'self
does not, is at least surprising. What is that good for?

Probably to do with the new changes allowing us to protect object 
code.

Inconsistent

what is? - be more specific.

See above

Again, it may have to do with protection features.

No, as long as one of the above expression works, while the other 
does not

I don't know how you can say "NO" Ladislav.

just easy: the functions are equivalent for me - I do not mind whether 
I use the former or the latter. If one of them works, while the other 
does not, it is inconsistent, and not protecting

Protect feature is still evolving at last check so I don't see how 
you can say it isn't part of that direction.

well, "part of that direction" - maybe, just not working in this 
case, as demonstrated

Then CureCode it, and maybe Carl will answer that one :-)

Brian, if "Returns TRUE if the values are equal and of the same datatype 
& case." is OK, but "Returns TRUE if the values are equal and of 
the same datatype and case." is not, that's where I think uor priorities 
are out of order. 


Maybe the first thing we should do is write a clear goal for doc 
strings. What is their main purpose and what constraints should be 
placed on them for each purpose (or maybe I just haven't seen the 
doc that does this)? For example, are they be limited for console 
output only when listed with other funcs, or also when used with 
HELP individually? Should ? be short help and ??? link to a detailed 
help page for funcs? If console group list is the constraining factor, 
can it truncate and ellipsize longer strings?

Is there a difference between an object! or context! Any rules wheren 
to use one or the other? I use contexts more likea "class"(data, 
functions) and objects mor like blocks.

I think that modules are the way to go, but than why we have context! 
and object! ?