Blocking syscalls in Tasks : ADA

> Except for DOS in todays OS all Ada partitions are executed by native OS
> threads.
This is confusing. An Ada partition is not at all the same as an Ada
task, and there's no guarantee that an Ada task maps 1-1 to an OS thread.

> Now, in a GUI system, the RC_TASK (resource task) is blocked until a input
> device such as the mouse or keyboard actives the thread.
MS Windows tasks do not block waiting for mouse or keyboard. Windows
"event based" GUI design was based on a single thread and a polling loop.

Each and every time you speak you CUT the post down Ada!
WHY are you trying to KILL Ada! And I say nothing that is
confusing except to those who hate Ada.

An event thread is a blocked thread. See Microsoft Windows Documentation!
LEARN before speaking!

In <q7GdnQCVgLL7XkLVnZ2dnUVZ_h-dnZ2d@comcast.com>, tmoran@acm.org writes:
>> Except for DOS in todays OS all Ada partitions are executed by native OS
>> threads.
> This is confusing. An Ada partition is not at all the same as an Ada
>task, and there's no guarantee that an Ada task maps 1-1 to an OS thread.
>
>> Now, in a GUI system, the RC_TASK (resource task) is blocked until a input
>> device such as the mouse or keyboard actives the thread.
> MS Windows tasks do not block waiting for mouse or keyboard. Windows
>"event based" GUI design was based on a single thread and a polling loop.

Probably because for Janus/Ada, pretty much everything you said about the
mapping of Ada tasks to threads is wrong.

Janus/Ada still maps all tasks to one Windows thread. That was originally
supposed to be a temporary Q&D implementation, but for a variety of reasons
it never got replaced. Most obviously: other things needed work more
urgently than the tasking, which is quite efficient. Depending on your
circumstances, it might actually be faster than a threaded implementation.
(Our ultimate goal is to have both.)

In any case, the point is that Ada doesn't say anything about the mapping of
tasks to OS threads: you simply have to ask your vendor. And, of course
blocking of system calls follows from that.

Randy.


"anon" <anon@anon.org> wrote in message
news:eBUDk.245076$102.150485@bgtnsc05-news.ops.worldnet.att.net...
> Each and every time you speak you CUT the post down Ada!
> WHY are you trying to KILL Ada! And I say nothing that is
> confusing except to those who hate Ada.
>
> An event thread is a blocked thread. See Microsoft Windows Documentation!
> LEARN before speaking!
>
> In <q7GdnQCVgLL7XkLVnZ2dnUVZ_h-dnZ2d@comcast.com>, tmoran@acm.org writes:
>>> Except for DOS in todays OS all Ada partitions are executed by native OS
>>> threads.
>> This is confusing. An Ada partition is not at all the same as an Ada
>>task, and there's no guarantee that an Ada task maps 1-1 to an OS thread.
>>
>>> Now, in a GUI system, the RC_TASK (resource task) is blocked until a
>>> input
>>> device such as the mouse or keyboard actives the thread.
>> MS Windows tasks do not block waiting for mouse or keyboard. Windows
>>"event based" GUI design was based on a single thread and a polling loop.
>

Most people want to know about Ada-2005 not Ada-95, and the one and only
vendor that supports the Ada-2005 is Adacore with GNAT. The information
that I gave was based on that vendor's system.

As for Janus/Ada, IBM and other Ada compilers to most they are outdated.
Janus/Ada and other vendors have had time to rebuild there Ada system for
XP, Vista and Linux using the Ada-2005 specs but for unknown reasons have
chosen not too. Plus, Janus/Ada was written for Windows 95/98 and NT
which are outdated and no longer supported by Microsoft.

Note about outdated: If you call an internet provider, and say you using
Windows 95/98, they will suggest you find another provider. Because,
they say they no longer support any outdated OS. Even though the OS is
still functional most people and companies do not want anything to do
with an outdated software.

Also, back in the late 90s using Windows 98, GNAT used threads that was
based on Microsoft Windows job scheduler which gave a higher performance
then the Intel cpu scheduler and threads. But as I say GNAT uses the OS
native threads, that is, threads specified by the OS not the cpu.



In <gbs3bb$ejt$1@jacob-sparre.dk>, "Randy Brukardt" <randy@rrsoftware.com> writes:
>Probably because for Janus/Ada, pretty much everything you said about the
>mapping of Ada tasks to threads is wrong.
>
>Janus/Ada still maps all tasks to one Windows thread. That was originally
>supposed to be a temporary Q&D implementation, but for a variety of reasons
>it never got replaced. Most obviously: other things needed work more
>urgently than the tasking, which is quite efficient. Depending on your
>circumstances, it might actually be faster than a threaded implementation.
>(Our ultimate goal is to have both.)
>
>In any case, the point is that Ada doesn't say anything about the mapping of
>tasks to OS threads: you simply have to ask your vendor. And, of course
>blocking of system calls follows from that.
>
> Randy.
>
>
>"anon" <anon@anon.org> wrote in message
>news:eBUDk.245076$102.150485@bgtnsc05-news.ops.worldnet.att.net...
>> Each and every time you speak you CUT the post down Ada!
>> WHY are you trying to KILL Ada! And I say nothing that is
>> confusing except to those who hate Ada.
>>
>> An event thread is a blocked thread. See Microsoft Windows Documentation!
>> LEARN before speaking!
>>
>> In <q7GdnQCVgLL7XkLVnZ2dnUVZ_h-dnZ2d@comcast.com>, tmoran@acm.org writes:
>>>> Except for DOS in todays OS all Ada partitions are executed by native OS
>>>> threads.
>>> This is confusing. An Ada partition is not at all the same as an Ada
>>>task, and there's no guarantee that an Ada task maps 1-1 to an OS thread.
>>>
>>>> Now, in a GUI system, the RC_TASK (resource task) is blocked until a
>>>> input
>>>> device such as the mouse or keyboard actives the thread.
>>> MS Windows tasks do not block waiting for mouse or keyboard. Windows
>>>"event based" GUI design was based on a single thread and a polling loop.
>>
>
>

anon schrieb:
> Most people want to know about Ada-2005 not Ada-95, and the one and only
> vendor that supports the Ada-2005 is Adacore with GNAT.

Are you sure? Just a few days ago, an Aonix news letter
informed about Ada 2005 courses...


> written for Windows 95/98 and NT
> which are outdated and no longer supported by Microsoft.

Larger US companies (such as GM) and larger European companies
(such as Daimler) seem to think that Vista is inadequate for
their businesses. They chose to keep Windows XP.

On Sep 30, 3:06 am, a...@anon.org (anon) wrote:
> Most people want to know about Ada-2005 not Ada-95, and the one and only
> vendor that supports the Ada-2005 is Adacore with GNAT.

Yeah, Randy, weren't you aware that as soon as the Ada 2005 standard
was officially finalized, all your customers immediately quit using
Janus/Ada since it's merely an Ada 95 compiler? If they're still
bugging you with customer support questions, obviously it's just an
attempt to make you feel less lonely. Or maybe they're all figments
of your imagination!

Sigh......

I'm not sure I can let this one go, though:

> As for Janus/Ada, IBM and other Ada compilers to most they
> are outdated. Janus/Ada and other vendors have had time to
> rebuild there Ada system for XP, Vista and Linux using the
> Ada-2005 specs but for unknown reasons have chosen not too.

Might I suggest that part of the reason Janus/Ada has "chosen not too
[sic]" spend the time "rebuilding" their system for Ada 95 is that the
person most responsible for working on their compiler has also been
spending time doing things like helping create the Ada 2005 standard,
participating in discussions of how to improve it and fix problems,
maintaining the actual manual including the online version, and
developing the test suite, not to mention taking the time to deal with
my annoying nitpicks about the test suite and missing characters in
the online RM and stuff like that. I realize he's not doing this
alone, but from my point of view he (along with others) have been
doing a tremendous amount of work, and (I'm sure) spending a
significant amount of time, making Ada 2005 possible so that punks
like you can benefit from it and then throw it back at him for not
upgrading the compiler as fast as you think it should be done and then
saying that his company "chose" not to support Ada 2005 "for unknown
reasons".

Please forgive my rant. I normally don't get that heated. But that
comment of yours is TOTALLY out of line.

-- Adam

Adam Beneschan wrote:
> Please forgive my rant. I normally don't get that heated. But that
> comment of yours is TOTALLY out of line.

I not only forgive your rant but I approve it wholeheartedly. You're
much kinder than I am. Anon, why don't you just shut up?

--
Ludovic Brenta.

Ludovic Brenta wrote:
>
> I not only forgive your rant but I approve it wholeheartedly. You're
> much kinder than I am. Anon, why don't you just shut up?

I'm amazed that anyone still reads its posts, much less responds to them.

--
Jeff Carter
"I unclog my nose towards you."
Monty Python & the Holy Grail
11

That good, about Aonix, but like within the last year when a few poster
stated that others vendor were coming out with Ada-2005 very soon. Has
it happen as of OCT 1, 2008, the answer is "NO!" And until they do, it is
only talk! And I am sure someone here (like you) will make a post when it
happens!

Vista, is current, but XP is still supported by Microsoft and in some areas
it is still the current OS. But the moment that Microsoft drops support
you will find only a few owner still using XP. All others will have move
to either an updated version Windows OS or a different OS.



In <48e20721$0$6567$9b4e6d93@newsspool4.arcor-online.net>, Georg Bauhaus <rm.dash-bauhaus@futureapps.de> writes:
>anon schrieb:
>> Most people want to know about Ada-2005 not Ada-95, and the one and only
>> vendor that supports the Ada-2005 is Adacore with GNAT.
>
>Are you sure? Just a few days ago, an Aonix news letter
>informed about Ada 2005 courses...
>
>
>> written for Windows 95/98 and NT
>> which are outdated and no longer supported by Microsoft.
>
>Larger US companies (such as GM) and larger European companies
>(such as Daimler) seem to think that Vista is inadequate for
>their businesses. They chose to keep Windows XP.

anon schrieb:
> Most people want to know about Ada-2005 not Ada-95, and the one and only
> vendor that supports the Ada-2005 is Adacore with GNAT. The information
> that I gave was based on that vendor's system.

More on which compilers do support Ada 2005:

"Most recently, Mr. Baird worked for IBM, which acquired Rational in
2003. As Senior Software Engineer, he was responsible for adapting the
Ada 95 “middle pass” portion of the Rational Ada compiler to implement
the dynamic semantics of Ada 2005."

So IBM is also the only vendor supplying a compiler for Ada 2005 ;-)

(Quoted from AdaCore's press center announcing "the appointment of Ada
expert Stephen Baird to the company’s GNAT Pro implementation team",
2008-09-09.)