[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: hijack C function, use it transparently with in-between layer

From: Barry Margolin
Subject: Re: hijack C function, use it transparently with in-between layer
Date: Mon, 06 Jun 2016 10:42:18 -0400
User-agent: MT-NewsWatcher/3.5.3b3 (Intel Mac OS X)

In article <address@hidden>,
 Stefan Monnier <address@hidden> wrote:

> >>> Good point, any ideas how to get to that as well?
> >> Report the cases you bump into as bugs.
> > You mean there should be no C to C calls for
> > stuff that are in Elisp as well?
> Just because you report it as a bug doesn't mean the maintainers will
> fix it or agree that it should be fixed.  There will sometimes be
> overriding concerns.  I think the main 2 reasons why a C-to-C call
> should not be replaced by a call "via Elisp" are:
> - the call is made in a context where it's unsafe to run arbitrary Elisp
>   code (e.g. GC is not allowed, or something like that).
> - the performance cost would be too high compared to the benefit of the
>   added flexibility.
> So whether the code can be changed or not will depend on the
> specific cases.  Hence report them as bugs and so the maintainers can
> look into it.

Is that a bug or a feature request? The documentation for advice 
specifically warns that it doesn't have any effect on calls to built-in 
functions from the C layer.

Barry Margolin, address@hidden
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***

reply via email to

[Prev in Thread] Current Thread [Next in Thread]