emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: commit 7719734dd7 org-compat.el: New compatibility function `org-random'
Date: Thu, 06 Sep 2012 20:02:47 +0200	[thread overview]
Message-ID: <877gs7do6w.fsf@Rainer.invalid> (raw)
In-Reply-To: 87bohj3vx0.fsf@altern.org

Bastien writes:
> The real problem is (random t) in previous versions of org-id.el.

Yes.

> Do you mean this should be (random) instead of (random t) in those
> versions?  Why?  If so, we can simply get rid of the compatibility
> macro and use (random).

That would be the correct thing to do.

>> No package should ever use `(random t)´ at all and especially not
>> repeatedly.
>
> I thought (random t) was okay especially because related functions
> (e.g. org-id-new) are *never* repeated at regular intervals.

That unfortunate misconception is built into many Emacs packages, hence
the effort to finally make this operation a no-op and move the seeding
of the PRNG to the Emacs init code.

> Besides, (random t) is documented in Emacs <24.3 and XEmacs.

Sure, but you still aren't supposed to re-seed a PRNG each time you want
a random number from it.  Especially not with the seeding method that
Emacs used to use.  Each Emacs session should call `(random t)´ exactly
once, in the user init file.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

  reply	other threads:[~2012-09-06 18:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-06 16:01 commit 7719734dd7 org-compat.el: New compatibility function `org-random' Achim Gratz
2012-09-06 17:26 ` Bastien
2012-09-06 18:02   ` Achim Gratz [this message]
2012-09-06 18:24   ` Nick Dokos
2012-09-11 18:01   ` Achim Gratz
2012-09-11 18:30     ` Bastien
2012-09-11 19:49       ` Achim Gratz

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.orgmode.org/

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

  git send-email \
    --in-reply-to=877gs7do6w.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=emacs-orgmode@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/org-mode.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).