OpenEuphoria

built-ins and include files

• Posted by Bernie Ryan <bwryan at PCOM.NET> Feb 03, 2000
• 441 views

Why are some features implemented by using machine level

  constants. If there is a machine-level constant for a given feature

  then why isn't that feature just implemented as a built-in feature

  instead of requiring an include file and the use of overhead code in

  the include file. A good example is the seek command why is it necessary

  to implement that feature via the file.e include file. This requires

  the user to use some built-ins and some include files to do standard

  file i/o. This is only one example of a built-in being implemented

  via a include file, there are many others. dll.e, graphics.e, get.e,

  mouse.e, machine.e and etc.

  Using these machine-level constant does nothing to aid the user in

  using, modifying or extending the language. It only requires user to

  add more include files and causes more naming conflicts.

  If a function has a machine-level constant then It should be built-in

  and not implemented in a include file. The include files should only

  be should be used for user add-ons

  Bernie