Re: Bug#190948: Violation against The Single UNIX ? Specification, Version 2

[Peter Stephenson <pws@csr.com>]

Zefram wrote:
> Peter Stephenson wrote:
> >/* ZLE entry point pointers.  They are defined here because the initial *
> > * values depend on whether ZLE is linked in or not -- if it is, we     *
> > * avoid wasting space with the fallback functions.  No other source    *
> > * file needs to know which modules are linked in.                      */
> 
> I wrote that comment.  The intent was as described, and I have a mental
> image of the fallback functions being in an appropriate conditional
> section.

The autoload version of zleread (now) sets the pointer to the fallback
version in case it fails.  So the only gain would seem to be you can
eliminate the autoload versions if zle is already linked.  However, the
standard mechanism at the moment is to use the dynamic link routines
even if zle is built into the shell (or at least zmodload acts the same
however the library is linked, I haven't checked further).  Plus if zle
is built into the shell removing the autoload functions to save space is
rather laughable.  So I don't think I'll change anything, except maybe
update the comment.

OK, it's back to Bluetooth scatter mode...

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070


**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
prohibited.  
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************