Hi Anton,

Most of the contexts of interest are those associated with objects. I am too
tired right now to go into details, but see my previous response for more
info. Your questions are well taken. REBOL currently does not have a
built-in object browser, which makes exploring objects a bit tedious. And
the docs are somewhat behind.

You can learn a lot quickly using Nenads help.r which can browse into
objects. It works with both Core and View. You can download it at:

http://rebol.dhs.org/help.r

Just put do %your-path/help.r in your user.r. Then you can start by

>> help system
OBJECT: system

WORDS:
     build      -- (Type: date)
     components -- (Type: block)
     license    -- (Type: string)
     product    -- (Type: word)
     version    -- (Type: tuple)
     view       -- (Type: none)

SUB-OBJECTS:
     console
     error
     locale
     network
     options
     ports
     schemes
     script
     standard
     user
     words

FUNCTIONS:
     stats  -- System statistics.  Default is to return total memory
allocated.

The sub-objects can then be accessed with path notation

help system/ports  ;for example

And so on, drilling deeper and deeper.

In this way, you can fairly quickly learn about the words defined in all the
accessible objects.

HTH
-Larry

----- Original Message -----
From: Anton <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 30, 2001 7:43 PM
Subject: [REBOL] Re(2): 'parse-url - where defined?


Allen, Elan, Nenad,

> Hi Anton, Elan, Nenad,
>
> That particular parse-url is in the system/view/vid object.
> read-via is also
> in the same object. (it is not the same as the one in net-utils, though it
> does call that one)

How did you discover this?
Did you know 'parse-url already or did you have to search?
How would you go about searching for a word
whose value is defined in some other context?
Is there a way of determining which
context a word's value is defined in?
Is there a way of listing all contexts?

Anton.

.

-- 
To unsubscribe from this list, please send an email to
[EMAIL PROTECTED] with "unsubscribe" in the 
subject, without the quotes.

Reply via email to