[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Dynamic loading progress
From: |
Eli Zaretskii |
Subject: |
Re: Dynamic loading progress |
Date: |
Fri, 10 Oct 2014 22:58:09 +0300 |
> From: Stefan Monnier <address@hidden>
> Cc: Aurélien Aptel <address@hidden>,
> address@hidden
> Date: Fri, 10 Oct 2014 14:42:56 -0400
>
> >> I use the .so extension to know whether a file is a binary module or
> >> elisp (compiled or source).
> > You cannot know that by the extension alone, anyway.
>
> Of course, we can: if the extension says ".el" or ".elc" we know it's
> Elisp (compiled or not), and if it says ".dll", ".so" or something like
> that, we know it's a binary module.
That's until you bump into a maliciously named file.
> > It's unreliable.
>
> If the user wants to use ".so" on an Elisp module, she'll get what she
> paid for. I'm really not worried.
You don't have to, because loading a shared library will validate it
anyway.
- Re: Dynamic loading progress, (continued)
Re: Dynamic loading progress, Aurélien Aptel, 2014/10/10
- Re: Dynamic loading progress, Eli Zaretskii, 2014/10/10
- Re: Dynamic loading progress, Stefan Monnier, 2014/10/10
- Re: Dynamic loading progress,
Eli Zaretskii <=
- Re: Dynamic loading progress, Stefan Monnier, 2014/10/11
- Re: Dynamic loading progress, Aurélien Aptel, 2014/10/13
- Re: Dynamic loading progress, Stefan Monnier, 2014/10/14
- Re: Dynamic loading progress, Aurélien Aptel, 2014/10/16
- Re: Dynamic loading progress, Stefan Monnier, 2014/10/16
- Re: Dynamic loading progress, Stephen Leake, 2014/10/18