Re: Interrupts handling in ADA

[Simon Wright <simon@pushface.org>]

"Ada @ BRL" <ada.brl.2011@gmail.com> writes:

> The environment of ADA applcation is:

Ada, please!

> I have 4 tasks that execute at the same time:
> one is the main task,
> the other three execute a "read" from network (socket) function inside
> their bodies (on the other side there's the C/C++ application with 3
> network sockets).
[...]
> I want that when new data is available on one or more socket threads,
> this / these threads somehow notify the main thread that data is
> arrived and then safely send the data to it.

First off, I'd use a Queue.

The new Ada2012 standard includes a synchronised Queue, which would be
just what you want out of the box, but you won't find that in the
current compilers, so you'll need to roll your own.

Starting from Ada.Containers.Vectors[1], the Queue abstraction would
come from using Append to put new mesages on the queue, Is_Empty to
check whether there's something to get from the queue, and First_Element
followed by Delete_First to fetch the front element.

You then need to wrap this container in a protected object[2], so that
the updates from the different input tasks don't corrupt each other, and
so that the main task can block until there's something to read. Use a
Put procedure to post messages onto the queue, and a Get entry to read
the next message or block if there isn't one.

The spec might look like

   with Ada.Containers.Vectors;
   package Queueing is
      type Message is new Integer;
      package Queue_Data
      is new Ada.Containers.Vectors (Index_Type => Natural,
                                     Element_Type => Message);
      protected Queue is
         procedure Put (M : Message);
         entry Get (M : out Message);
      private
         Buffer : Queue_Data.Vector;
      end Queue;
   end Queueing;

and (as a hint) the body of the Get entry might start like

      entry Get (M : out Message) when not Buffer.Is_Empty is
      begin

If your input messages are not all the same type (in Ada-speak, type
Message is indefinite), things get more complicated; but let's cross
that bridge only if we need to.

[1]http://www.adaic.org/resources/add_content/standards/05rm/html/RM-A-18-2.html
[2]http://en.wikibooks.org/wiki/Ada_Programming/Tasking#Protected_types