unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: What to do with too-large group ids?
Date: Mon, 29 Jul 2002 12:04:22 +0200	[thread overview]
Message-ID: <vaf4reialzt.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <je1y9mzynp.fsf@sykes.suse.de> (Andreas Schwab's message of "Mon, 29 Jul 2002 11:11:38 +0200")

Andreas Schwab <schwab@suse.de> writes:

> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai writes:
>
> |> But if you prefer, I'll return them as strings and update the
> |> documentation for file-attributes accordingly.  (Something like the
> |> following, wording needs to be changed: If the user id is too large
> |> for an int, it is returned as a string.  This never happens for normal
> |> files, but it might happen when there is a filename handler.)
>
> Why can't this happen for normal files?

Because the current file-attributes implementation never creates a
cons (or a string) for user/group id.

I don't know what happens when the id is too large for such a file.
But surely a cons/string is not what happens.

Maybe make_number automatically creates a float when the number is too
large for a Lisp int?  Then the handlers should do that, too, I guess.

kai
-- 
A large number of young women don't trust men with beards.  (BFBS Radio)

  reply	other threads:[~2002-07-29 10:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-27  9:33 What to do with too-large group ids? Kai Großjohann
2002-07-27 14:12 ` Simon Josefsson
2002-07-27 15:47   ` Kai Großjohann
2002-07-27 20:53     ` Simon Josefsson
2002-07-28 10:17       ` Kai Großjohann
2002-07-29  1:12     ` Richard Stallman
2002-07-29  7:36       ` Kai Großjohann
2002-07-29  8:08         ` Paul Eggert
2002-07-29  9:11         ` Andreas Schwab
2002-07-29 10:04           ` Kai Großjohann [this message]
2002-07-30  0:59         ` Richard Stallman

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=vaf4reialzt.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.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.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).