1. Bug Reports - To where ?

Greetings,

To where should one send bug reports and how can one [easily] check that
a bug hasn't been found and reported already ?

Also, in the same vain, is there anywhere to send things to be added to
the Wish List for the next version ?



John Bown

Origin UK Ltd
323 The Science Park
Milton Road
Cambridge
CB4 4WG
United Kingdom

mailto:john.bown at uk.origin-it.com
http://www.psynet.net/hippy

new topic     » topic index » view message » categorize

2. Re: Bug Reports - To where ?

On Wed, 21 Oct 1998 11:26:57 +0100, Bown, John <John.Bown at UK.ORIGIN-IT.COM>
wrote:

>Greetings,
>
>To where should one send bug reports and how can one [easily] check that
>a bug hasn't been found and reported already ?
>
>Also, in the same vain, is there anywhere to send things to be added to
>the Wish List for the next version ?
>
This is the place for both! RDS monitors the list.
You could also use the search engine on the listserver to
look for earlier bug reports: http://listserv.muohio.edu

Irv

new topic     » goto parent     » topic index » view message » categorize

3. Re: Bug Reports - To where ?

John Bown writes:
> To where should one send bug reports and how can one
> [easily] check that a bug hasn't been found and reported already ?

Bug reports should be sent to me at rds at msn.com
or you can post them on this list.

Every now and then, I post a list of bugs to this list.
Perhaps there should be a place on the Web site for it,
but I'm worried that newcomers will see a long list of
bugs (mostly very rare and minor) and be scared off.

> Also, in the same vain, is there anywhere to send things to
> be added to the Wish List for the next version ?

You can send them to me directly or post them on this list.


-----------------------------------------------------------------------
         Known Bugs in Euphoria v2.0
(all have been fixed in the working copy at RDS)

- BUG FIX: added if ... then to allocate_string() so it won't
  store into address 0 when allocate() returns 0
  User can check for 0. Thanks to Ralf N. and Greg Harris

- BUG FIX: In ex.err "traced lines leading up to the failure"
  would drop the first piece of each statement
  when "with trace" and either "with profile" or "with profile_time"
  were selected. Thanks to Christopher Hickman.

- BUG FIX: save_text_image and display_text_image were not correct for
number of lines > 25 AND using an alternate active page (>page 0) Thanks to
Jean Bayon.

- BUG FIX: in message_box() there was a storage leak - thanks to Terry
Constant

- BUG FIX: the object() type now returns 1 in every case.
  (object() previously existed, but was undocumented and incorrect)

- BUG FIX: read_bitmap() was neglecting to close the bitmap file
  if it had an unsupported format. Thanks to Jesus Consuegra
  and Graeme Burke.

- BUG FIX: trace() will no longer have any effect unless it is executed
  inside a "with trace" section. This will prevent it from causing get_key()
to delay 8 seconds each time, unless you are really doing an interactive
trace.

- BUG FIX: scramble was not handling ascii character 255 properly
  - thanks to Graeme Burke.

- BUG FIX: bind/shroud would have an error if you give it control-Z
  for the filename - Andy Kurnia.

- BUG FIX: (Irv Mullins) numbers typed into your program greater than
about 88 digits would crash Euphoria (due to WATCOM C sscanf() failing!).

- Bug FIX: In WIN32, C functions declared as returning char, unsigned
char, short or unsigned short would not always have the value returned
correctly. The low order 8 or 16 bits would be correct,
  but the upper bits of the Euphoria atom returned from c_func()
  might be garbage. Thanks to Greg Harris.

- Bug FIX: bind/shroud would sometimes choose the same name as a
   user's symbol name in cases where the user's name was not
  shroudable, e.g. -clear_routines was specified, or it was a
  global name in the main file, and it was a very short name.
  This would cause an error when the program was run -
  "name already defined". (thanks to Rolf Schroeder)

- BUG FIX: get/value will now avoid inf in cases like 0.0000001e310
  where the exponent part would have been inf, but the mantissa was
  less than 1.

- BUG FIX: get() and value() were allowing ''' as single-quote character
  but ex/exw were declaring it an error. Now get() and value()
  declare it as an error too.

- BUG FIX: if you have a unary minus operation applied to a constant
  symbol that is defined earlier in the *same* constant statement,
  ex.exe and exw.exe may crash. e.g.
    constant a = 10, b = -a

- BUG FIX: the call_proc/call_func error traceback might be slightly
  off by a statement or so.

- BUG FIX: search.ex no longer writes control-Z (26) characters into
  search.out (ed can't read beyond 26 because it opens files in text
  mode, and 26 is taken as EOF.)

Regards,
     Rob Craig
     Rapid Deployment Software
     http://members.aol.com/FilesEu/

new topic     » goto parent     » topic index » view message » categorize

4. Re: Bug Reports - To where ?

That's too many bugs. I'm giving up EUPHORIA and going back to QBasic.

Just kidding.

If I have a DOS 32-bit program and want to take it to WIN, there's no easy,
quick procedure, is there, since I will have to be using Windows in the WIN
version. Or does WIN create a window wherein things happen?

Robert Craig wrote:

> John Bown writes:
> > To where should one send bug reports and how can one
> > [easily] check that a bug hasn't been found and reported already ?
>
> Bug reports should be sent to me at rds at msn.com
> or you can post them on this list.
>
> Every now and then, I post a list of bugs to this list.
> Perhaps there should be a place on the Web site for it,
> but I'm worried that newcomers will see a long list of
> bugs (mostly very rare and minor) and be scared off.
>
> > Also, in the same vain, is there anywhere to send things to
> > be added to the Wish List for the next version ?
>
> You can send them to me directly or post them on this list.
>
> -----------------------------------------------------------------------
>          Known Bugs in Euphoria v2.0
> (all have been fixed in the working copy at RDS)
>
> - BUG FIX: added if ... then to allocate_string() so it won't
>   store into address 0 when allocate() returns 0
>   User can check for 0. Thanks to Ralf N. and Greg Harris
>
> - BUG FIX: In ex.err "traced lines leading up to the failure"
>   would drop the first piece of each statement
>   when "with trace" and either "with profile" or "with profile_time"
>   were selected. Thanks to Christopher Hickman.
>
> - BUG FIX: save_text_image and display_text_image were not correct for
> number of lines > 25 AND using an alternate active page (>page 0) Thanks to
> Jean Bayon.
>
> - BUG FIX: in message_box() there was a storage leak - thanks to Terry
> Constant
>
> - BUG FIX: the object() type now returns 1 in every case.
>   (object() previously existed, but was undocumented and incorrect)
>
> - BUG FIX: read_bitmap() was neglecting to close the bitmap file
>   if it had an unsupported format. Thanks to Jesus Consuegra
>   and Graeme Burke.
>
> - BUG FIX: trace() will no longer have any effect unless it is executed
>   inside a "with trace" section. This will prevent it from causing get_key()
> to delay 8 seconds each time, unless you are really doing an interactive
> trace.
>
> - BUG FIX: scramble was not handling ascii character 255 properly
>   - thanks to Graeme Burke.
>
> - BUG FIX: bind/shroud would have an error if you give it control-Z
>   for the filename - Andy Kurnia.
>
> - BUG FIX: (Irv Mullins) numbers typed into your program greater than
> about 88 digits would crash Euphoria (due to WATCOM C sscanf() failing!).
>
> - Bug FIX: In WIN32, C functions declared as returning char, unsigned
> char, short or unsigned short would not always have the value returned
> correctly. The low order 8 or 16 bits would be correct,
>   but the upper bits of the Euphoria atom returned from c_func()
>   might be garbage. Thanks to Greg Harris.
>
> - Bug FIX: bind/shroud would sometimes choose the same name as a
>    user's symbol name in cases where the user's name was not
>   shroudable, e.g. -clear_routines was specified, or it was a
>   global name in the main file, and it was a very short name.
>   This would cause an error when the program was run -
>   "name already defined". (thanks to Rolf Schroeder)
>
> - BUG FIX: get/value will now avoid inf in cases like 0.0000001e310
>   where the exponent part would have been inf, but the mantissa was
>   less than 1.
>
> - BUG FIX: get() and value() were allowing ''' as single-quote character
>   but ex/exw were declaring it an error. Now get() and value()
>   declare it as an error too.
>
> - BUG FIX: if you have a unary minus operation applied to a constant
>   symbol that is defined earlier in the *same* constant statement,
>   ex.exe and exw.exe may crash. e.g.
>     constant a = 10, b = -a
>
> - BUG FIX: the call_proc/call_func error traceback might be slightly
>   off by a statement or so.
>
> - BUG FIX: search.ex no longer writes control-Z (26) characters into
>   search.out (ed can't read beyond 26 because it opens files in text
>   mode, and 26 is taken as EOF.)
>
> Regards,
>      Rob Craig
>      Rapid Deployment Software
>      http://members.aol.com/FilesEu/

new topic     » goto parent     » topic index » view message » categorize

Search



Quick Links

User menu

Not signed in.

Misc Menu