Re: Tasking issues

["Steve" <nospam_steved94@comcast.net>]

Shaun,

Take a look at:  http://en.wikibooks.org/wiki/Ada_Programming/Tasking

There is an example of a Protected_Buffer that is along the lines of what 
you need.

I worked with several other systems using multi-tasking (multi-threading or 
whatever they decide to call it this year) before learning Ada.  At first I 
found Ada tasking difficult to understand.  It turns out Ada tasking is 
really very simple.  Simpler than any other tasking I've used, and I like it 
a lot more.

There are two basic objects assosciated with tasking: task types and 
protected objects.  There are a few constructs that go along with these 
types "entry", "accept", "select", "delay", "requeue", and "terminate" (I 
probably missed one or two).  Once you understand the basics of what they 
do, tasking is easy.

Regards,
Steve
(The Duck)


<shaunpatterson@gmail.com> wrote in message 
news:1186851804.567302.223160@q4g2000prc.googlegroups.com...
> I'm having trouble with tasking in Ada.  I'm used to working with
> pthreads
> in C/C++... and I'm finding tasks to be somewhat different/annoying.
>
> My basic problem is I want to have 2 threads in my program.
>
> One thread sits in the background and reads in messages,
> dispatches them, etc and the other thread reads off a queue
> and sends out messages when they are available.
>
> As an analogy, let's assume my background task just got
> input from the user (simulating the socket read) and the other
> task just printed out stuff.
>
> Something like
>
> procedure main is
> begin
>  task get_name;
>  task print_something;
>
>  task body get_name is
>      Name : String (1..25);
>      Last : Integer;
>  begin
>      loop
>          Get_Line (Name, Last);
>      end loop;
>  end get_name;
>
>  task body print_something is
>  begin
>      loop
>      Put_Line ("blah...");
>      end loop;
>   end print_something;
>
> begin --- main
>
>     loop;
>          null;
>     end loop;
> end main;
>
>
> Of course, this doesn't work as I'd expect.  Is there a way to
> "timeout" the
> first get_name thread... so the OS only waits on that thread for a
> short period
> of time to allow the other threads to do their business? and then go
> back to
> the thread?
>
> Thanks
> -- Shaun
>