Subject | Re: [IB-Architect] Engineering project description |
---|---|
Author | rfm@collectivecomputing.com |
Post date | 2000-05-16T22:43:44Z |
Ann Harrison wrote:
log file etc too...
be a function in a library which accepts a FILE handle and passes
it to a regular RTL function. Thus any functions that takes a FILE *
argument is suspect unless you know it also uses BSD stream IO.
Or do the ib_ functions take and IB_FILE * ? that would seem to
make the whole problem irrelevent... Maybe thats what's already been
done ?
Reed Mideke
rfm(at)collectivecomputing.com
>What about the client shared lib ? The client gets to write to the
> Reed,
>
> Thanks for the warning. The BSD routines will be compiled and
> linked as part of the InterBase engine on Solaris. (Down group,
> this is not significant bloat.) Those handles never leave the
> engine.
>
log file etc too...
> However, we do plan to document the ib_stdio.h and all its littleImportant point: It need not be a different process. It can just
> pals so people writing UDF's can use it. UDF's that use buffered
> file I/O will fail in the same way as our internal fopens on
> Solaris with large numbers of users. That documentation should
> (must) include a warning not to pass an open file to a different
> process.
be a function in a library which accepts a FILE handle and passes
it to a regular RTL function. Thus any functions that takes a FILE *
argument is suspect unless you know it also uses BSD stream IO.
Or do the ib_ functions take and IB_FILE * ? that would seem to
make the whole problem irrelevent... Maybe thats what's already been
done ?
>--
> Regards,
>
> Ann
>
> ------------------------------------------------------------------------
Reed Mideke
rfm(at)collectivecomputing.com