Back to the main page.
Bug 2171 - remove deprecated code that has passed its expiration date (THT)
| Status | CLOSED FIXED |
| 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 |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: | http://bugzilla.fcdonders.nl/show_bug.cgi?id=2162 |
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 http://fieldtrip.fcdonders.nl/code_guidelines?&#document_deprecated_source_code
Robert Oostenveld - 2013-05-17 08:35:09 +0200
(In reply to comment #1) Furthermore, I have provided a link on the page http://fieldtrip.fcdonders.nl/development/deprecated 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 ;) http://fieldtrip.fcdonders.nl/development/dashboard
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 :)