Is utf-16-codec supported or not?

Bug #189605 reported by Michael D. Adams
2
Affects Status Importance Assigned to Milestone
Ikarus Scheme
Fix Committed
High
Abdulaziz Ghuloum

Bug Description

Found this when running Larceny's R6RS "cat3" benchmark.

While (latin-1-codec) and (utf-8-codec) work just fine, using (utf-16-codec) causes the following error.

Unhandled exception:
 Condition components:
   1. &assertion
   2. &who: slow-get-char
   3. &message: "BUG: codec not handled"
   4. &irritants: (utf-16-codec)

I don't presently have a need for this particular codec, but if you don't support this codec yet, then it should be documented in the User's Guide under "Missing Features".

Changed in ikarus:
assignee: nobody → aghuloum
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Abdulaziz Ghuloum (aghuloum) wrote :

Bumping priority since this has to be fixed.

Changed in ikarus:
importance: Low → High
Revision history for this message
Abdulaziz Ghuloum (aghuloum) wrote :

utf-16 codec now works for both input and output ports (revision 1641). Bizarre that we don't have utf-16-le and utf-16-be codecs.

Changed in ikarus:
status: Confirmed → Fix Committed
Changed in ikarus:
milestone: none → 0.0.4
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.