OpenEuphoria

Re: Documenting functions that rely on namespace?

• Posted by Jason Gade <jaygade at yah??.com> Apr 25, 2008
• 619 views

Bernie Ryan wrote:
> 
> Jeremy Cowgar wrote:
> > 
> > Ok, maybe they do not rely upon, but are easier understood by namespace.
> > Here's
> > what I am speaking of...
> > 
> > }}}
<eucode>
> > include datetime.e as d
> > include map.e as m
> > 
> > datetime d1
> > map m1
> > 
> > d1 = d:new(2008, 10, 20, 12, 30, 0)
> > m1 = m:new()
> > </eucode>
{{{

> > 
> > So, we have 2 new functions. How do I go about documenting that?
> > 
> > --
> 
> Jeremy:
> 
>   How did datetime all of a sudden become a type ??
> 
>   I think you are going to push or force Euphoria away from being
> 
>   a simple easy to learn and use language.
> 
>   This is what draws users to Euphoria not a lot exotic features.   
> 
>   We don't need another Python or APL language.
> 
>   The basic concept of Euphoria will be lost.
> 
>   There are NO strings in Euphoria only sequences, objects, integers and
> 
>   user define types.
> 
>   Any of your so called string operations can be done easily with
> 
>   sequence manipulation.
> 
> 
> Bernie
> 
> My files in archive:
> WMOTOR, XMOTOR, W32ENGIN, MIXEDLIB, EU_ENGIN, WIN32ERU, WIN32API 
> 
> Can be downloaded here:
> <a
> href="http://www.rapideuphoria.com/cgi-bin/asearch.exu?dos=on&win=on&lnx=on&gen=on&keywords=bernie+ryan">http://www.rapideuphoria.com/cgi-bin/asearch.exu?dos=on&win=on&lnx=on&gen=on&keywords=bernie+ryan</a>

It would be his user-defined-type for his standard library project, not a
built-in type.

--
A complex system that works is invariably found to have evolved from a simple
system that works.
--John Gall's 15th law of Systemantics.

"Premature optimization is the root of all evil in programming."
--C.A.R. Hoare

j.