OpenEuphoria

Re: routine_id()

• Posted by Ralf Nieuwenhuijsen <nieuwen at XS4ALL.NL> Nov 13, 1997
• 756 views

Robert Craig wrote:

> As routine_id is actually defined, if you really want to call his foo
> you
> can do it, but he must explicitly call routine_id("foo") and pass you
> the routine id himself. He will never fear that you are calling his
> routines without his permission.

    So this means it contains the same rules as normal function calling
& definition ??
    (private & global routines i mean)

    And please, please, at least consider to make calling a routine
indirect illigal (each file must include the other file itself).
    Simply add a new keyword for routine declaration: child
    Example:
            --
            child function this_func ()
                -- some happy code
            end function
            --

    Routines defined with child in front of it, can only be called when
that file is directly included.
    Same should apply to declaration of data objects:

            child sequence my_sequence
            child constant my_text = "Euphoria Rulez!"

    I hope you finally consider this, Robert, i've asked you several
times, but never got a respons, and i know you have a lot to do and i
don't want to waste your time, but for me its clear that this will be a
very good thing for Euphoria and will increase Euphoria purity. I am
sometimes trying to do develop complex mechanisms, that certainly don't
make Euphoria look good. I can give you an example, but it will be a
very complex.

Ralf N
nieuwen at xs4all.nl