finalize or withdraw? Alex Shinn (19 Aug 2005 04:24 UTC)
Re: finalize or withdraw? Thomas Bushnell BSG (19 Aug 2005 05:18 UTC)
Re: finalize or withdraw? Alex Shinn (19 Aug 2005 05:21 UTC)
Re: finalize or withdraw? Hans Oesterholt-Dijkema (19 Aug 2005 07:57 UTC)
Re: finalize or withdraw? Hans Oesterholt-Dijkema (19 Aug 2005 07:57 UTC)
Re: finalize or withdraw? Michael Sperber (20 Aug 2005 06:54 UTC)
Re: finalize or withdraw? Alex Shinn (22 Aug 2005 04:17 UTC)
Re: finalize or withdraw? Michael Sperber (22 Aug 2005 16:06 UTC)
Re: finalize or withdraw? Per Bothner (22 Aug 2005 18:04 UTC)
Re: finalize or withdraw? Michael Sperber (23 Aug 2005 07:19 UTC)
Re: finalize or withdraw? Per Bothner (23 Aug 2005 07:59 UTC)
Re: finalize or withdraw? Michael Sperber (23 Aug 2005 08:14 UTC)
Re: finalize or withdraw? Per Bothner (24 Aug 2005 04:07 UTC)
Re: finalize or withdraw? Michael Sperber (24 Aug 2005 17:30 UTC)
Re: finalize or withdraw? Alex Shinn (24 Aug 2005 02:57 UTC)
Re: finalize or withdraw? Alex Shinn (23 Aug 2005 01:27 UTC)
Re: finalize or withdraw? Michael Sperber (23 Aug 2005 07:21 UTC)
Re: finalize or withdraw? Alex Shinn (23 Aug 2005 08:10 UTC)

Re: finalize or withdraw? Thomas Bushnell BSG 19 Aug 2005 05:18 UTC

Alex Shinn <xxxxxx@gmail.com> writes:

> The library style of reading and writing single different sized numbers
> at a time is especially well suited to such applications as writing a
> portable assembler.  However, an assembler invariably needs to read and
> write strings within the binary data, and SRFI-56 provides no portable
> means to do this.

An assembler does not write strings "within the binary data".
Remember, a string is a sequence of characters, not a sequence of
encodings.  Assemblers need to write specific numbers in specific
places, not "strings"; that is, they need control over the coding
used.  Which means they should encode the characters, and then write
numbers.