octave-maintainers
[Top][All Lists]
Advanced

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

Re: removing __dispatch__


From: John W. Eaton
Subject: Re: removing __dispatch__
Date: Fri, 21 Oct 2016 14:37:23 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.4.0

On 10/21/2016 12:09 PM, Rik wrote:
On 10/21/2016 09:00 AM, address@hidden wrote:
Subject:
Removing __dispatch__
From:
"John W. Eaton" <address@hidden>
Date:
10/21/2016 08:13 AM

To:
Octave Maintainers List <address@hidden>

List-Post:
<mailto:address@hidden>
Content-Transfer-Encoding:
7bit
Precedence:
list
MIME-Version:
1.0
Message-ID:
<address@hidden>
Content-Type:
text/plain; charset=utf-8; format=flowed
Message:
3


About 6 years ago, we deprecated the "dispatch" function.  The actual
functionality was moved to the internal function __dispatch__ and a .m
file wrapper preserved the original function name.  The dispatch
function was removed in Feb 2012 for the 3.8 release but we kept the
__dispatch__ function and all the internal machinery for it.  Now I
can find no uses of either dispatch or __dispatch__ in Octave or
Octave Forge.  Does anyone object to completely removing this obsolete
feature?

jwe

More Code = More Maintenance Burden

Seems like a fine idea to get rid of this cruft.

Pushed to default:

http://hg.savannah.gnu.org/hgweb/octave/rev/e7a9dfb8bf16

jwe




reply via email to

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