I do know something about Maple code documentation from diverse sources...

I do not believe that there is a decision not to rewrite the code of fsolve because of backward compatibility fears. I think rather that this is a case of its update time not arrived yet. Indeed, several "most wanted parts" of the system have been rewritten in more modern style (as modules, including typechecking, etc) along recent versions, see e.g. this thread.

The problem is rather that this update process goes very slowly (you may read here about the systematic maintainance problem - note that the logical order of that thread was upset in the transition to Mapleprimes 2).

I do know something about Maple code documentation from diverse sources...

I do not believe that there is a decision not to rewrite the code of fsolve because of backward compatibility fears. I think rather that this is a case of its update time not arrived yet. Indeed, several "most wanted parts" of the system have been rewritten in more modern style (as modules, including typechecking, etc) along recent versions, see e.g. this thread.

The problem is rather that this update process goes very slowly (you may read here about the systematic maintainance problem - note that the logical order of that thread was upset in the transition to Mapleprimes 2).

@alex_01 Sadly, in recent years a lot of interface facilities were implemented only for graphic interaction, with no programmatic counterpart. I do not foresee any change in this trend for Maple 17 time.

Coding styles of different pieces of the library are quite diverse, depending on when and who wrote them, and whether they were later updated. At first sight, it looks like fsolve code was originally written long time ago (actually copyright is from 1992).

In my opinion, one important reason for user documentation problems like this one, is that the code itself was not properly documented (in the literate sense).

Patrick, do you mean this thread?

Patrick, do you mean this thread?

@Joe Riel 

I think that this help page needs more examples illustrating those diverse options, and probably a link to Programming Guide Chapter 15 Setting Watchpoints on Specified Errors. Actually, the Examples section begins saying: "Note: These examples illustrate the use of these debugger commands" but then it just shows a single example...

@Joe Riel 

I think that this help page needs more examples illustrating those diverse options, and probably a link to Programming Guide Chapter 15 Setting Watchpoints on Specified Errors. Actually, the Examples section begins saying: "Note: These examples illustrate the use of these debugger commands" but then it just shows a single example...

@Robert Israel 

It appears like an egg and hen problem. For a worksheet created by somebody else, containing output, you would need the Maple version that created it for safely removing that output...

Perhaps a filtering script could be written, keeping the input regions (apparently those with {MPLTEXT...) and removing the output regions.

@Robert Israel 

It appears like an egg and hen problem. For a worksheet created by somebody else, containing output, you would need the Maple version that created it for safely removing that output...

Perhaps a filtering script could be written, keeping the input regions (apparently those with {MPLTEXT...) and removing the output regions.

You are right, this is the content of the file updtsrc.txt that came with Maple V Release 4:

The updtsrc File Converter 
===========================


DESCRIPTION

- The updtsrc file converter takes a Maple source file containing code
  written in Maple V Release 3, and updates it to conform with rules for
  use with Maple V Release 4. 

- See the platform specific documentation for information about how to
  use updtsrc on your platform. 

- The updtsrc program reads from the specified files.  Output is written
  to the standard output.

- The program reads from command line files or from standard input and
  writes to standard output. 

RUNNING updtsrc

You can access updtsrc from within Windows or OS/2,
or from the DOS command line.

  Windows and OS/2:   Click on the updtsrc application icon.

  DOS:   Enter "updtsrc" at the command line prompt.  You can find the
	 executable updtsrc.exe in the bin.win directory.


OPTIONS

Once inside uptsrc, you may specify any any options and the names of
the files you wish to update.

- updtsrc has the following options: 

    -p allow printing of copyright procedures          
    -w suppress warning messages of deleted procedures 
    -h suppress printing of file name header            

- If a procedure definition is copyright K.O. Geddes, G.H. Gonnet, M.B.
  Monagan, University of Waterloo, Waterloo Maple Inc., or
  ETH-Zentrum(Zurich) then it is not copied to the output file and a
  newer version of the procedure is available. The -p option will
  override this. 

- A warning message is written to standard error whenever text is not
  copied to the output file.  The warning gives the procedure name and
  line number in the source text.  The use of outdated library procedures
  also gives a warning message of the same form. 


- The ":" delimiter, when used for declaring parameter types in procedure
  definitions, is replaced by "::".

- Operator procedures defined using "<" and ">" (angle bracket notation) are
  replaced by a different notation as follows:

       "<expr>" becomes either "() -> expr", "var -> expr", or "(var,...,var)
       -> expr", where the vars are determined by computing "indets(expr)".

       "<expr|var>" becomes "var -> expr".

       "<expr|var,...,var>" becomes "(var,...,var) -> expr".

       "<expr|vars|locals>" becomes "proc(vars) option operator; local
       locals; expr end".

       "<expr||locals>" becomes "proc(vars) option operator; local locals;
       expr end", where the vars are determined by computing "indets(expr)".


DIAGNOSTICS

- Exit status is 0 for normal exit and 1 if an error occurs.


SEE ALSO

- See also the updtsrc help page which may be viewed from within Maple
  by typing ?updtsrc.

You are right, this is the content of the file updtsrc.txt that came with Maple V Release 4:

The updtsrc File Converter 
===========================


DESCRIPTION

- The updtsrc file converter takes a Maple source file containing code
  written in Maple V Release 3, and updates it to conform with rules for
  use with Maple V Release 4. 

- See the platform specific documentation for information about how to
  use updtsrc on your platform. 

- The updtsrc program reads from the specified files.  Output is written
  to the standard output.

- The program reads from command line files or from standard input and
  writes to standard output. 

RUNNING updtsrc

You can access updtsrc from within Windows or OS/2,
or from the DOS command line.

  Windows and OS/2:   Click on the updtsrc application icon.

  DOS:   Enter "updtsrc" at the command line prompt.  You can find the
	 executable updtsrc.exe in the bin.win directory.


OPTIONS

Once inside uptsrc, you may specify any any options and the names of
the files you wish to update.

- updtsrc has the following options: 

    -p allow printing of copyright procedures          
    -w suppress warning messages of deleted procedures 
    -h suppress printing of file name header            

- If a procedure definition is copyright K.O. Geddes, G.H. Gonnet, M.B.
  Monagan, University of Waterloo, Waterloo Maple Inc., or
  ETH-Zentrum(Zurich) then it is not copied to the output file and a
  newer version of the procedure is available. The -p option will
  override this. 

- A warning message is written to standard error whenever text is not
  copied to the output file.  The warning gives the procedure name and
  line number in the source text.  The use of outdated library procedures
  also gives a warning message of the same form. 


- The ":" delimiter, when used for declaring parameter types in procedure
  definitions, is replaced by "::".

- Operator procedures defined using "<" and ">" (angle bracket notation) are
  replaced by a different notation as follows:

       "<expr>" becomes either "() -> expr", "var -> expr", or "(var,...,var)
       -> expr", where the vars are determined by computing "indets(expr)".

       "<expr|var>" becomes "var -> expr".

       "<expr|var,...,var>" becomes "(var,...,var) -> expr".

       "<expr|vars|locals>" becomes "proc(vars) option operator; local
       locals; expr end".

       "<expr||locals>" becomes "proc(vars) option operator; local locals;
       expr end", where the vars are determined by computing "indets(expr)".


DIAGNOSTICS

- Exit status is 0 for normal exit and 1 if an error occurs.


SEE ALSO

- See also the updtsrc help page which may be viewed from within Maple
  by typing ?updtsrc.

@Joe Riel 

The location is given here.

@st345 

No, the same status quo continues up to Maple 15: both postscript export drivers are still there. The "positive" side of this situation is that you can still use the older driver by exporting from the CLI or the Classic GUI, using plotsetup as above (well, Joe may hack some code for calling the old driver from within Standard :) )

In any case, David Clayworth is no longer working at Maplesoft. It would be very interesting to know the current official stand on this issue.

@John Starrett 

The Classic GUI is, fortunatelly, still distributed in 32-bit versions of Maple 15 on Windows and Linux. And you can install both the 32bit and 64bit versions on the same PC.