OpenEuphoria

Re: Changes in the ESL papers

• Posted by "Juergen Luethje" <j.lue at gmx.de> Jul 24, 2005
• 548 views

Pete Lomax wrote:

> I think the best way to handle errors consistently is:
> }}}
<eucode>
> 	result=f(x,y,z)
> 	if error then
> 		...
>
> 	p(x,y,z)
> 	if error then
> 		...
>
> </eucode>
{{{

> Where result should be the correct type rather than an object,
> and error is a global boolean (just the one for the whole of the
> standard library), reset at the start of every [global] routine.
> If error is set the value of result is meaningless. You can equally
> have a separate global object errorDetails if need be, the contents of
> which are routine-specific.

I vote for this one! Very cool! 
But currently it seems to be hard to get an agreement regarding this
point.

> Regards,
> Pete
> PS Another thought: All dates used in comments in the standard library
> should be unambiguous, eg 6 JUL 2005, since 6/7/05 may be read as
> June 7th 2005 by some. Not sure if that was mentioned.

Well, kind of, but not that clearly. In the General Guidelines in
'road_map.htm' we already had:

"For all things that are handled differently in different countries
(like the date format), our code [and documentation] follows generally
accepted international recommendations, mainly ISO and the RFCs, as far
as internet communication is concerned."

I added "and documentation" in the above paragraph, and also added the
following:

"Although e.g. the date 2005-07-06 /is/ unambiguous according to ISO,
some people might not realize that this is ISO format, or might not know
the ISO rules, and so it may be read erraneously as June 7th 2005 by
some. In order to express dates unambiguously, all dates used in
comments and documentation should preferably use the /name/ of the month
rather than its number."

Thanks,
   Juergen