Re: [Chicken-janitors] #1182: utf8 egg silently accepts invalid byte sequences

[Chicken Trac]

#1182: utf8 egg silently accepts invalid byte sequences
-------------------------+--------------------------------------------------
  Reporter:  syn         |       Owner:  ashinn 
      Type:  defect      |      Status:  closed 
  Priority:  major       |   Milestone:  someday
 Component:  extensions  |     Version:  4.9.x  
Resolution:  invalid     |    Keywords:  utf8   
-------------------------+--------------------------------------------------
Changes (by ashinn):

  * status:  new => closed
  * resolution:  => invalid


Comment:

 That's not a complete test, and you're using different code now.
 You're now implicitly referring to utf8-lolevel procedures.  The
 meaning of "lolevel" is that it is dangerous, and allows you to
 shoot yourself in the foot.

 (use utf8) puts the standard procedures in utf8 mode.  If you
 pass valid inputs to those procedures and get an invalid output
 it's a bug, and I will fix it.  If you pass invalid inputs, you get
 undefined results.  Both of your examples are of invalid inputs,
 created outside of utf8.

-- 
Ticket URL: <http://bugs.call-cc.org/ticket/1182#comment:6>
CHICKEN Scheme <http://www.call-with-current-continuation.org/>
CHICKEN Scheme is a compiler for the Scheme programming language.