Mail Archives: djgpp-workers/1998/02/02/14:24:51
Randy Maas wrote:
>
> Here is a *much* larger example that has some functionality. My only
> concern is that it may too much to take in if you want to know what
> __FSEXT_{get,set}_data does. I've tried to vary the comments -- if
> describing it one way doesn't help, maybe the other way will. The code is
> a very stripped down version of a different one I have used; it can be
> stripped further by doing even less error checking (currently it doesn't
> set errno). This version does compile without warnings.
*looks* good! Maybe instead of being an example for
__FSEXT_{get,set}_data, it should be used as an example for FSEXT in
general. I haven't looked at the docs in the alphas, so I don't know if
there are any other FSEXT examples, but I'm thinking this example (maybe
with the init code?) and
maybe some others should go into the knowledge base.
Sorry about causing you all this extra work, Randy, but *I* like good
examples and IMHO they can make a programmers life much easier.
I just thought of something: Is it possible to have cross-references
from one info file to another? eg example sections in the libc docs
pointing to any relevant examples in the knowledge base.
>
> One possibility, is that the other io functions *could* be emulated, but
> not provided in the example. ie:
> ...inside of the switch...
> case __FSEXT_stat:
> *RV = my_stat(Args); /* see XYZ for an example of a stat handler */
> return 1;
Hmmm, yes that *could* work, especially if you can somehow put an `info'
cross reference in that comment (I know html would work, but would
texinfo? I don't know enough.).
Bill
--
Leave others their otherness
- Raw text -