<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>I'm wondering about Cstdio.i3..<BR>
<BR>
It bugs me to see duplicated code/declarations, code I can't easily verify the correctness of, code that duplicates internal details either that aren't necessary and/or are subject to change (ie: it *might* be useful to know the size of a FILE, but knowing the internal makeup is not generally useful, as well the size can be abstracted away behind a tiny bit of portable C), etc.<BR>
<BR>
interface Cstdio seems<BR>
<BR>
- almost not used at all within the "std" packages<BR>
I realize folks out there with other code could be using it.<BR>
The only use I see is related to the next:<BR>
<BR>
- to offer little in the way of a portable interface<BR>
About the main portable thing is presents is that there is a type FILE_star, though even that isn't quite universial across them all; conceptually it is of course<BR><BR>
However, a medium sized very portable interface is easy to expose, though it isn't necessarily easy to make much use of.<BR>
<BR>
So:<BR>
- do nothing?<BR>
- reduce it all down to just a common two-liner TYPE FILE = RECORD END; FILE_star = UNTRACED REF FILE ?<BR>
- bulk it up slightly to a very portable (target-independent) interface?<BR>
NT386/Cstdio.i3 is close to what that would be.<BR>
<BR>
And no, I'm not forgetful. I know I brought this up a few months ago when I introduced NT386/Cstdio.i3.<BR>
<BR>
Does anyone find the knowledge built up in the myriad Cstdio.i3 files useful?<BR>
One thing to do is leave all the per-platform files but not put them in the m3makefile, only actually compile the two line or medium sized portable version.<BR>
<BR>
?<BR>
<BR>
- Jay<BR></body>
</html>