Re: Standard Euphoria Library Project
Al Getz wrote:
>
> Mainly, when using any function like this, some sort of
> range checking is always desirable in order to reduce
> errors that cause the program to hault.
>
Yes, range checking is required for a) debugging, and b) handling user
input. When it is used for debugging it should give the programmer an
informative error message so that the program errors can be found and
corrected. This is best done through the use of type(). Although there are
exceptions, I think it is unwise to write routines that simply ignore
errors, as this just interferes with the debugging process.
I think the SELP is a good idea. Any includes developed with this project
should be group/team efforts. To avoid total anarchy, there needs to be an
agreed process covering:
1. Decision on what include files are to be produced,
2. Decision on what routines are to be put into each include.
3. Review, debugging, documentation process.
4. Approval by the group.
5. Submission to Rob for stamping
Less important, but still worth mentioning, is the matter of programming
style and documentation style, so that the product has a reasonably uniform
and easy-to-understand appearance. I would suggest we follow RDS's example
as seen in graphics.e (programming style) and library.doc (documentation
style), unless someone can offer a better idea.
- Colin Taylor
|
Not Categorized, Please Help
|
|
