OpenEuphoria

Re: What's holding Euphoria back?

• Posted by MICHAEL J CARVALHO <Mikey45 at WORLDNET.ATT.NET> Jan 30, 1999
• 409 views

Touche Rob! Well said!!
-----Original Message-----
From: Robert Craig <rds at EMAIL.MSN.COM>
To: EUPHORIA at LISTSERV.MUOHIO.EDU <EUPHORIA at LISTSERV.MUOHIO.EDU>
Date: Friday, January 29, 1999 9:12 PM
Subject: Re: What's holding Euphoria back?


>Irv Mullins writes:
>> 1. Lack of structures
>
>This has been discussed at length. There might be some
>support eventually, but it has to be something elegant and powerful.
>I don't want to keep adding "missing" features until Euphoria
>becomes "C++ with sequences".
>
>> 2. Name space problems
>
>I consider name space issues to be very high priority for
>the next major release. I did not want to open this
>issue just before this release, as it impacts several different
>things in Euphoria, such as binding, tracing and routine_id(),
>in addition to normal symbol look-up. I want to do it right,
>not just a quick band-aid solution.
>
>> 3. Abysmal waste of disk space when writing data files.
>> ... We need to store single characters as one byte on
>> disk, not two, three or more
>
>When you write one or more characters to disk using
>puts(), they *are* stored as one byte each. If you think
>that print() to disk is wasteful, don't use it.
>
>> 4. A lack of true random access for files.
>
>You can use seek() and where() to position yourself
>randomly at any byte in a file.
>
>If you want to set up a large database, where the size
>of the disk files matters, and the speed matters, I think
>you can easily write your own set of very simple low-level routines
>to take specific sequences and store them on disk compactly
>and efficiently, since you will typically know the format of the
>data you are storing, the sizes of integer values, the maximum
>length of strings etc.
>
>Regards,
>     Rob Craig
>     Rapid Deployment Software
>     http://members.aol.com/FilesEu/