Re: Problem with Unbounded Strings

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On Fri, 4 Dec 2015 08:53:54 -0800 (PST), in comp.lang.ada you wrote:

> I don't use append?

No. There is nothing that is not in the buffer read already. Why would you
append anything?

In some protocols payload data are accumulated from several packets.
Unbounded_String is not used for that either. You want to limit the size of
the accumulated data to prevent DoS attacks unless the protocol limits that
already, as most protocols do. Simply keep the buffer in the communication
object, that is all.

> What is this then doing? Where U_B = ada.strings.unbound...
> 
>                  U_B.Append (Source   => Buffer, 
>                             New_Item => Line (5 .. Line'Last)); 
> 
> ETX is as the other commands 5 chars long because in the txt file I read
> from, it is  used as <ETX> . To lazy to rewrite the <>. So ETX : String
> constant := "<ETX>";...

In such cases I am usually match the current string prefix against a table
of tokens (table-driven recursive descent).

But if you want an explicit form it is like this (a recursive descent
parser):

   case Buffer (Index) is -- Index is the current position
      when '<' =>
         Index := Index + 1;
         case Buffer (Index) is
            when 'A' =>
               Index := Index + 1;
               ...
            when 'E' =>
               Index := Index + 1;
               ...
            when 'G' =>
               Index := Index + 1;
               ...
            when 'R' =>
               Index := Index + 1;
               ...
            when 'S' =>
               Index := Index + 1;
               ...
            when others =>
               raise Protocol_Error with
                     "ACK, ETX, ENQ, STX or GS is expected at" &
                     Integer'Image (Index);
      when others =>
         raise Protocol_Error with
                "< is expected at" & Integer'Image (Index);
   end case;

The point is to visit each source character just once and prevent excessive
copying. That is also the reason why you practically never need or should
not use Unbounded_String for I/O. It won't make your life easier anyway.
You would have to convert it to String anytime you would use its contents
as your code demonstrates. The code will be cleaner, safer and many times
faster.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de