anchor.diff:  rename_mod_eclipse(FileName, NewName, SearchPaths) ->
       refac_rename_mod:rename_mod_eclipse(FileName, NewName, SearchPaths).
   
  -%% =====================================================================
  -%% @doc Rename a collection of module names in batch mode. 
  -%% <p> This refactoring is supposed to be run from the Erlang shell. For example, 
  -%% to rename all those module names which match the regular expression "foo_*" to 
  -%% "foo_*_1_0" in the directory <code> c:/wrangler/test </code>, just type the following command:
  -%% <code> wrangler:rename_mod_batch("foo_*, "foo_*_1_0", ["c:/wrangler/test"]) </code>.
  -%% </p>
  -%% <p> This refactoring has a global effect. </p>
  -%% <p> The following <em> side-conditions </em> apply to this refactoring:
  -%% <li> The new module names should not conflict with each other, or any existing module names 
  -%% in the same scope which will not be renamed. </li>
  -%% <li> This refactorings assumes that the file basename is always the same as the module name. </li>
  -%% </p>
  -%% =====================================================================
  -%% @spec rename_mod_batch(OldNamePattern::string(), NewNamePattern::string(), 
  -%%                        SearchPaths::[dir()])-> ok | {error, string()}
  -%%   
  +%% =====================================================================
  +%% @doc Rename a collection of module names in batch mode. 
  +%% <p> This refactoring is supposed to be run from the Erlang shell. For example, 
  +%% to rename all those module names which match the regular expression "foo_*" to 
  +%% "foo_*_1_0" in the directory <code> c:/wrangler/test </code>, just type the following command:
  +%% <code> wrangler:rename_mod_batch("foo_*, "foo_*_1_0", ["c:/wrangler/test"]) </code>.
  +%% </p>
  +%% <p> This refactoring has a global effect. </p>
  +%% <p> The following <em> side-conditions </em> apply to this refactoring:
  +%% <li> The new module names should not conflict with each other, or any existing module names 
  +%% in the same scope which will not be renamed. </li>
  +%% <li> This refactorings assumes that the file basename is always the same as the module name. </li>
  +%% </p>
  +%% =====================================================================
  +%% @spec rename_mod_batch(OldNamePattern::string(), NewNamePattern::string(), 
  +%%                        SearchPaths::[dir()])-> ok | {error, string()}
  +%%   
   
   
   -spec(rename_mod_batch/3::(string(), string(), [dir()])->
  
positive.code: rename_var_eclipse(FileName, Line, Col, NewName, SearchPaths) ->
      refac_rename_var:rename_var_eclipse(FileName, Line, Col, NewName, SearchPaths).
  
  %%=========================================================================================
  %% @doc Rename a function name with a user-supplied new name.
  %% <p> To apply this refactoring, point the cursor to any occurrence of this 
  %% function name, then select <em> Rename Function Name </em> from the <em> Refactor </em> menu, 
  %% after that the refactorer will prompt to enter  the new function name in the mini-buffer.
  %% </p>
  %% <p>
  %% When renaming an exported function name, this refactoring has a global effect, i.e.,
  %% it affects all those modules in which this function is imported/used.
  %% </p>
  %% <p> The following <em> side-conditions </em> apply to this refactoring:
  %% <li> The new function name should not cause confliction with any of the functions which are in scope in the 
  %% current module;</li>
  %% <li> In the case that the function to be renamed is imported by another module, the new function name (with the same 
  %% arity) should not be already in scope (either defined or imported) in that module. </li>
  %% </p>
  %% ========================================================================================
  %% @spec rename_fun(FileName::filename(), Line::integer(), Col::integer(), NewName::string(), SearchPaths::[dir()])
  %% -> term()
  
  -spec(rename_fun/5::(string(), integer(), integer(), string(), [dir()]) ->
  	     {error, string()} | {ok, [filename()]}).
  
negative.code:     refac_tuple_to_record:tuple_to_record_eclipse(File, FLine, FCol, LLine, LCol,
  						  RecName, FieldString, SearchPaths).
  
  %%@private
  %%@spec fun_to_process(FileName::filename(), Line::integer(), Col::integer(), ProcessName::string(), SearchPaths::[dir()]) ->term()
  -spec(fun_to_process/5::(filename(), integer(), integer(), string(), [dir()])->
  	     {error, string()} | undecidables | {ok, [filename()]}).
  fun_to_process(FileName, Line, Col, ProcessName, SearchPaths) ->
  