zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh workers <zsh-workers@zsh.org>
Subject: Re: PM_ flags (Re: mikachu/badarrays ...)
Date: Wed, 7 Jun 2017 15:18:02 -0700	[thread overview]
Message-ID: <170607151802.ZM17932@torch.brasslantern.com> (raw)
In-Reply-To: <16943.1496832826@thecus.kiddle.eu>

On Jun 7, 12:53pm, Oliver Kiddle wrote:
}
} Should we perhaps change the flags field in struct param to be a 64-bit
} value to make room for more flags? Can we portably use something like
} uint64_t or is it not that simple?

The main problem is that there is assumed to be a mapping from bit
positions to indexes in the TYPESET_OPTSTR string.  At some point we
started adding PM_FLAGS at the opt of the range to mean things other
than what could be assigned via "typeset -C" for some value of C,
and now the stack has grown down to meet the heap, so to speak.

So we'd have to renumber everything to move to a 64-bit representation,
opening up that space in the middle again.

This, by the way, is an example of why it's very difficult to build zsh
modules outside the tree that can be re-used across zsh versions; there
are lots of cases (wordcode being another example) where values that are
built into a module at time T could be dangerously wrong for a shell
compiled at T+N.


      parent reply	other threads:[~2017-06-07 22:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-26  5:04 Valgrind testing, ideas Sebastian Gniazdowski
2017-05-26  5:50 ` Bart Schaefer
2017-05-26  7:57   ` Sebastian Gniazdowski
2017-05-26 10:56     ` Daniel Shahaf
2017-05-26 23:48       ` Bart Schaefer
2017-05-28 19:43 ` mikachu/badarrays (Re: Valgrind testing, ideas) Bart Schaefer
2017-05-29 13:21   ` Mikael Magnusson
2017-05-31  5:47     ` Bart Schaefer
2017-06-01 16:31       ` Sebastian Gniazdowski
2017-06-01 20:35         ` Bart Schaefer
2017-06-02  1:40           ` Sebastian Gniazdowski
2017-06-02 22:00             ` Bart Schaefer
2017-06-04  0:49             ` Bart Schaefer
2017-06-04  7:08               ` Sebastian Gniazdowski
2017-06-01 21:22       ` Mikael Magnusson
2017-06-01 21:38         ` Bart Schaefer
2017-06-07 10:53       ` PM_ flags (Re: mikachu/badarrays ...) Oliver Kiddle
2017-06-07 18:15         ` Mikael Magnusson
2017-06-07 22:18         ` Bart Schaefer [this message]

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=170607151802.ZM17932@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.org \
    /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).