zsh-workers
 help / color / mirror / code / Atom feed
From: Zefram <zefram@fysh.org>
To: opk@u.genie.co.uk (Oliver Kiddle)
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: completion
Date: Tue, 26 Oct 1999 14:35:14 +0100 (BST)	[thread overview]
Message-ID: <E11g6ks-0004Mi-00@crucigera.fysh.org> (raw)
In-Reply-To: <3815A627.19C7F2A@u.genie.co.uk> from Oliver Kiddle at "Oct 26, 1999  2: 1:27 pm"

Oliver Kiddle wrote:
>Note that all the .o files have two dots (e.g. modentry..o) when
>building on
>AIX. This is probably a mistake somewhere but it has always compiled
>happily so
>I've never bothered.

This should probably be documented in the development guide or somewhere.

In the very first dynamic linking patches, all objects were ".o",
as usual.  However, objects need to be compiled with different options
when they're in a module than from when they're linked into the main
executable.  After changing the list of compiled-in modules, it was
necessary to remove all the objects.  So we changed it so that objects
to be linked into modules got the suffix "..o", so that both lots of
object files could coexist, and even when you don't need both lots to
exist at once it avoids a lot of potential confusion.

The module install directory was changed from $prefix/lib/zsh
to $prefix/lib/zsh/$ZSH_VERSION at the same time, for similar
confusion-avoidance reasons (plus coexistence of multiple installed zsh
versions).  Ever since then, I've been glad that we got that right from
the start.  I hate to think, if we hadn't done these two things, how many
support queries we'd be answering where it turned out that people had got
the wrong objects linked together.  (This is all related to the principle
of least surprise; I'm going to dub it the "principle of least support".)

-zefram


  reply	other threads:[~1999-10-26 13:35 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-26 13:01 Oliver Kiddle
1999-10-26 13:35 ` Zefram [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-02-21  9:50 Sven Wischnowsky
1999-10-28  8:12 Sven Wischnowsky
1999-10-28  6:58 Sven Wischnowsky
1999-10-27  8:42 Sven Wischnowsky
1999-10-27 16:39 ` Bart Schaefer
1999-10-27  7:14 Sven Wischnowsky
1999-10-27 21:26 ` Tanaka Akira
1999-10-26 13:17 Sven Wischnowsky
1999-10-26 11:03 Sven Wischnowsky
1999-10-26 17:17 ` Bart Schaefer
1999-10-26 17:22 ` Tanaka Akira
1999-10-26 17:32   ` Tanaka Akira
1999-08-30  9:30 Sven Wischnowsky
1999-08-27  7:03 Sven Wischnowsky
1999-08-27  8:29 ` Tanaka Akira
1999-08-28  6:01   ` Tanaka Akira
1999-08-26 13:52 Sven Wischnowsky
1999-08-26 12:20 Sven Wischnowsky
1999-08-26 13:17 ` Tanaka Akira
1999-08-26 17:56 ` Tanaka Akira
1999-08-25 12:57 Sven Wischnowsky
1999-08-25 12:54 Sven Wischnowsky
1999-08-25  8:24 Sven Wischnowsky
1999-08-26 10:54 ` Tanaka Akira
1999-08-24 10:43 Sven Wischnowsky
1999-08-25  1:56 ` Tanaka Akira
1999-08-24  9:12 Sven Wischnowsky
1999-08-24 10:04 ` Tanaka Akira
1999-08-23 13:46 Sven Wischnowsky
1999-08-23 16:16 ` Tanaka Akira
1999-08-24 15:56 ` Tanaka Akira
1999-08-23 12:00 Sven Wischnowsky
1999-08-23  9:32 Sven Wischnowsky
1999-08-23 10:54 ` Tanaka Akira
1999-08-20 12:59 Sven Wischnowsky
1999-08-20 23:22 ` Tanaka Akira
1999-08-21  8:39   ` Tanaka Akira
1999-08-21 17:47     ` Tanaka Akira
1999-08-20  7:42 Sven Wischnowsky
1999-08-19 13:59 Sven Wischnowsky
1999-08-19 10:44 Sven Wischnowsky
1999-08-19 14:38 ` Tanaka Akira
1999-08-24 13:46 ` Peter Stephenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E11g6ks-0004Mi-00@crucigera.fysh.org \
    --to=zefram@fysh.org \
    --cc=opk@u.genie.co.uk \
    --cc=zsh-workers@sunsite.auc.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).