Does the TODO/FIXME Report work with m-files in a package?

This issue is resolved in R2013b

---------------------------------

Is the TODO/FIXME Report supposed to work without limitations on m-files in a package? I cannot find any indication on http://www.mathworks.com that it should not do that.

I use R2013a 64bit, Win7

My TODO/FIXME Report on the package folder is generated without any warnings or errors being issued. The report looks ok. However, clicking a link causes this error

    Error using edit (line 66)
    File 'H:\m\test4ida\ xyzw4ida\Reference.m' not found. 
    66      throw(exception); % throw so that we don't display stack trace
    >>

The problem is obviously that the "+" in the folder name is replaced by space, " ". In the header of the report the "+" is in place: "Report for folder H:\m\test4ida\+xyzw4ida"

Packages have been around for several releases and the TODO/FIXME Report even longer.

.

More reasons to be frustrated

• it's the function urldecode, which causes the problem. It calls java.net.URLDecoder.decode
• Class URLDecoder says: "The plus sign "+" is converted into a space character " " . "

.

Temporary fix. Overloading the function, urldecode, with

    function urlOut = urldecode(urlIn)
        urlOut = urlIn;
    end

makes my report on m-files in a package work. However, I guess urldecode is called for some reason and that this fix will cause hassles when I least expect it.

.

Is there a better fix?

• The TODO/FIXME Report is that an html-file, which I could edit?
• Is it possible to put my function, urldecode, in a place where it will make less harm?

Answer 1

[Christoph]

This is a known issue with the Todo/Fixme report. You can 1) Remove the calls to urldecode in lines 152 and 157 of dofixrpt.m, i.e. line 152: s{end+1} = sprintf('<tr><td valign="top" class="td-linetop"><a href="matlab: edit(''%s'')"><span class="mono">%s</span></a></td>', ...

line 157: s{end+1} = sprintf('<span class="mono"><a href="matlab: opentoline(''%s'',%d)">%d</a> %s</span><br/>', ...

2) Upgrade to R2013b or R2014a where this issue is resolved