Re: Base64-Encoding

[Stephen Leake <stephen_leake@stephe-leake.org>]

Stefan Bellon <sbellon@sbellon.de> writes:

> Ok, bad wording on my part. Let my try to explain what I mean.
>
> The German Wikipedia page for Base64 has a nice coloured illustration:
> http://de.wikipedia.org/wiki/Base64

In English: http://en.wikipedia.org/wiki/Base64

Not quite the same illustration, but the same idea.

> My basic idea is to define an array of Six_Bits and "overlay" this at
> the same address as the String with the usual 8-bit Character encoding.

I think Adam is correct that this is non-portable.

The GNAT Ada compiler has special code for each case of packed arrays.
For Six_Bits_Array, see the package System.Pack_06 (in file
s-pack06.adb). It defines:

   for Cluster use record
      E0 at 0 range 0 * Bits .. 0 * Bits + Bits - 1;
      E1 at 0 range 1 * Bits .. 1 * Bits + Bits - 1;
      E2 at 0 range 2 * Bits .. 2 * Bits + Bits - 1;
      E3 at 0 range 3 * Bits .. 3 * Bits + Bits - 1;
      E4 at 0 range 4 * Bits .. 4 * Bits + Bits - 1;
      E5 at 0 range 5 * Bits .. 5 * Bits + Bits - 1;
      E6 at 0 range 6 * Bits .. 6 * Bits + Bits - 1;
      E7 at 0 range 7 * Bits .. 7 * Bits + Bits - 1;
   end record;

where Bits is 6. There is no Bit_Order pragma on this, so it is in
native bit order; apparently little-endian in your case (x86).

So Base64_Data (0) has bits 0 .. 5 of Data (0), Base64_Data (1) has
bits 6, 7 of Data (0) and bits 0 .. 3 of Data (1), etc. In effect, the
bytes in Data are reversed in groups of 6. Not easy to draw :(.

AdaCore does not implement Bit_Order for machine sizes greater than 1
(last I checked; a couple years ago). If they did, and applied
bit_order to this record, it would be endian-independent, and work the
way you expect. It would also break any current code, so they probably
never will. But you could at least code it yourself in a cleaner
endian-independent way. So ask them to!

-- 
-- Stephe