From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,9bdd666589befb0f,start
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!postnews.google.com!u72g2000cwu.googlegroups.com!not-for-mail
From: "Le" <snelson1@llnl.gov>
Newsgroups: comp.lang.ada
Subject: Palatable Windows IO using Ada
Date: 6 Apr 2006 17:21:44 -0700
Organization: http://groups.google.com
Message-ID: <1144369304.698267.277640@u72g2000cwu.googlegroups.com>
NNTP-Posting-Host: 128.115.35.70
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1144369311 16924 127.0.0.1 (7 Apr 2006 00:21:51
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Fri, 7 Apr 2006 00:21:51 +0000 (UTC)
User-Agent: G2/0.2
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1,gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse@google.com
Injection-Info: u72g2000cwu.googlegroups.com; posting-host=128.115.35.70;
   posting-account=KkHgpQ0AAACJ6vo83UckeWojsCAJd4eu
Xref: g2news1.google.com comp.lang.ada:3741
Date: 2006-04-06T17:21:44-07:00
List-Id: <comp.lang.ada>

I are looking for Ada package(s) which make Windows serial IO more
palatable for varying length asynchronous inputs.

My team is laying a large legacy Ada application on top of Windows XP.
There is a fair amount of serial IO which follows a VMS flavor -
pending reads while writes stimulate responses back to the reading
tasks & sets of terminator characters to delimit messages. Wrappers we
have seen for the Win32 API simply export the ReadFile and ReadFileEx
which appear to be blocking by their very nature and demand that the
reader have apriori knowledge of the length of input expected at any
particular instance.

Of course one can deal with the varying length by doing all reads one
character at a time, but this is quite waseful in the face of Windows
already daunting CPU requirements.

So, if you know of a somewhat thicker wrapper for Windows external IO
that makes it a little more (may I say) (x)nix like (or some other
alternative) I'd really appreciate a pointer or copy.