Back to the main page.

Bug 2171 - remove deprecated code that has passed its expiration date (THT)

Reported 2013-05-15 13:48:00 +0200
Modified 2019-08-10 12:29:02 +0200
Product: FieldTrip
Component: core
Version: unspecified
Hardware: PC
Operating System: Windows
Importance: P3 normal
Assigned to: Eelke Spaak
Depends on:
See also:

Eelke Spaak - 2013-05-15 13:48:01 +0200

e.g. fieldtrip/compat, freqanalysis

Robert Oostenveld - 2013-05-17 08:32:42 +0200

I have documented it in the guidelines at

Robert Oostenveld - 2013-05-17 08:35:09 +0200

(In reply to comment #1) Furthermore, I have provided a link on the page where deprecated functions and options are to be listed. I realize that the list on that page is very incomplete, but nevertheless it might help in deciding on the expiry date.

Roemer van der Meij - 2013-05-22 12:20:51 +0200

I removed all the references to legacy code in ft_freqanalysis, removed all trunk/compat functions dealing/containing with this old code, and removed 3 faqs detailing the differences between the legacy and the specest code. The info not covered by the other faqs I put into a new one (i.e. absolute phase convention).

Eelke Spaak - 2013-06-14 11:57:34 +0200

I removed all files from compat/ which had as their contents the compatibility wrapper for non-ft_-prefixed calls, as of r8264. I thought I'd wait with all the other compat files to see what this would bring about first :)

Roemer van der Meij - 2013-06-14 13:20:12 +0200

So far so good ;)

Eelke Spaak - 2014-01-29 15:12:33 +0100

Just deleted everything from /compat/ except ft_prepare_atlas, since all the rest was last edited in December 2012.

Eelke Spaak - 2014-01-29 15:13:49 +0100

Resolved for now, if we want to delete stuff in the future I propose to make a new bug out of it. Of course, if my recent delete action (revision 9150) causes troubles, this bug should be reopened :)

Robert Oostenveld - 2019-08-10 12:29:02 +0200

This closes a whole series of bugs that have been resolved (either FIXED/WONTFIX/INVALID) for quite some time. If you disagree, please file a new issue describing the issue on