OpenEuphoria

Re: Confirmation for 2.3

• Posted by euman at bellsouth.net Aug 16, 2001
• 381 views

Well, I must be like you,  I said I would post updates
to my Dos-Windowing program but havent in almost a year.

I hope to one day and now that I know alittle more, when I ever do
get back to it, it will certainly be more powerfull and faster.

Not rushing, normally makes things much better.... 

a list of bugs may help some of the people that
have been around a while avoid possible problems that may arise
in they're programs. Some of us are actually trying to write major
app's here Rob. On the other hand, After 4 1/2 years the pitfalls
for me have narrowed somewhat so maybe the list might help the
new people get a good head start as well.......

When I made the statement that I only know of a one or two bugs
that wasnt entirely true. I said this because I think I may be the only one
doing odd shaped windows and manipulating the Windows in Win.
I know of two bugs right there....they are minor because with a little math
I get around this. (btw, these relate to the interpreter -ver- translated code.)

If you think people will be put off by bugs in Euphoria, then you might be
right.
Those people who are put off by this should be intelligent enough to realise
that you are
atleast honest about Euphoria bugs and that something is being done about them.
That very honesty would have sold me on Euphoria regardless of the list..

Euman
euman at bellsouth.net

> Euman writes:
> > You might do a search on the RDS site
> > for such things.
> >
> > Robert has talked about this atleast 10 times.
>
> In an ideal world, there would be an up-to-date list
> of all known bugs, and another list of all features
> that are planned for the next release.
>
> Besides laziness, there are a couple of reasons
> why I don't publish these lists.
>
> 1. A list of every bug that I'm aware of would include
>     lots of very minor, very rare bugs that few people
>     will ever encounter. I'd have to write a description
>     of each bug in a form that people can clearly understand it.
>     My descriptions currently are in a terse, cryptic form,
>     including references to internal data structures etc.
>     Any major bugs are almost certain to be fixed in the next release.
>
> 2. A bug list should be on the Web site, but I think
>     that people visiting the site for the first time would
>     see the long list of (minor) bugs, think the product
>     was very buggy, and leave.
>
> 3. I talk about the major features that I'm planning, but
>     I shy away from listing lots of minor features. I have
>    a huge list of small things I'd like to do, but I usually
>    commit to something only when I've finished the previous
>    task. Once I talk about doing something I feel committed
>    to do it, even if I find something else that's a lot more useful.
>
> 4. Did I mention laziness?
>
> Regards,
>    Rob Craig
>    Rapid Deployment Software
>    http://www.RapidEuphoria.com
>
>
>
>
>