@pagan 

I have checked that this parse error occurs, with very similar message, back to Maple V Release 5, aparently the first version where the command line option -c was introduced.

@pagan 

I have checked that this parse error occurs, with very similar message, back to Maple V Release 5, aparently the first version where the command line option -c was introduced.

@PatrickT 

There is also a diversity of file managers of all kinds and for all tastes. I like the dual-pannel "commander style" ones, and on Windows I use Total Commander (formerly Windows Commander). It is very powerful and highly configurable. A quite useful feature, in regards to your question, is its customizable button bar where the user can add buttons for launching applications, or additional button bars. Each button executes a command in an specialized script language. So, I have a dedicated Maple button bar, with two buttons for each Maple version: for Classic and Standard GUIs. This means, that I can launch any of these GUIs opening the file under the file manager cursor by just clicking on the button.

Then certainly, the Maple 15 Standard GUI button does not open a text input file with extension mpl if the placeholder for the file in the script is not quoted or has normal quotes. And it opens fine if the quotes are escaped. No such problem occurs when launching the Standard GUI of previous Maple versions.

In short, yes, I think that it is exactly the same problem.

@PatrickT 

There is also a diversity of file managers of all kinds and for all tastes. I like the dual-pannel "commander style" ones, and on Windows I use Total Commander (formerly Windows Commander). It is very powerful and highly configurable. A quite useful feature, in regards to your question, is its customizable button bar where the user can add buttons for launching applications, or additional button bars. Each button executes a command in an specialized script language. So, I have a dedicated Maple button bar, with two buttons for each Maple version: for Classic and Standard GUIs. This means, that I can launch any of these GUIs opening the file under the file manager cursor by just clicking on the button.

Then certainly, the Maple 15 Standard GUI button does not open a text input file with extension mpl if the placeholder for the file in the script is not quoted or has normal quotes. And it opens fine if the quotes are escaped. No such problem occurs when launching the Standard GUI of previous Maple versions.

In short, yes, I think that it is exactly the same problem.

@pagan 

I have verified this behavior in the cmd shell on Windows XP 32. Maple 15 Standard executable needs escaped quotes for opening an input file with termination mpl, while Maple 14 Standard executable works the same whether the quotes are escaped or not. Idem for the read form, with the parse error message though. By the way, what do you think about this error? Bug or feature?

@pagan 

I have verified this behavior in the cmd shell on Windows XP 32. Maple 15 Standard executable needs escaped quotes for opening an input file with termination mpl, while Maple 14 Standard executable works the same whether the quotes are escaped or not. Idem for the read form, with the parse error message though. By the way, what do you think about this error? Bug or feature?

@PatrickT 

May be that I am not firm on earth...

What is a bug is frequently a subjective issue. In this case, missing a specification of how the executable file should behave, everyone, me, the developer, etc, may have completelly different opinions on the correctness of this behavior. I do not know, if a SCR were submitted against it, what would be the answer: bug, works as designed, product limitation, etc . Note that the answer "works as designed" is frequently "perverse" as such reference of the design exists, at best, only in the developer's mind.

Yes, my batch file for Maple 15 Standard is basically like that.

Indeed, in Windows I keep installed from Maple V R2 on. It is very useful. Sometimes you cannot believe the regressions that have occured!

There are editors of every kind and for every taste. What helps making the job done is fine. On Windows, my default editor is TSE which is very fast and has a powerful macro language. Counting its ancestor Qedit, I have been using it for about 20 years. Along this period I have developed my custom set of macros, etc.

Yes, the medit window can be splitted both horizontally and vertically. I have not used this feature very much. though.

@PatrickT 

May be that I am not firm on earth...

What is a bug is frequently a subjective issue. In this case, missing a specification of how the executable file should behave, everyone, me, the developer, etc, may have completelly different opinions on the correctness of this behavior. I do not know, if a SCR were submitted against it, what would be the answer: bug, works as designed, product limitation, etc . Note that the answer "works as designed" is frequently "perverse" as such reference of the design exists, at best, only in the developer's mind.

Yes, my batch file for Maple 15 Standard is basically like that.

Indeed, in Windows I keep installed from Maple V R2 on. It is very useful. Sometimes you cannot believe the regressions that have occured!

There are editors of every kind and for every taste. What helps making the job done is fine. On Windows, my default editor is TSE which is very fast and has a powerful macro language. Counting its ancestor Qedit, I have been using it for about 20 years. Along this period I have developed my custom set of macros, etc.

Yes, the medit window can be splitted both horizontally and vertically. I have not used this feature very much. though.

@PatrickT 

Insisting with the same thing as this one for several hours is not healthy!

As I see it on Win XP 32, pagan's suggestion of using the command read from the shell command line suffers of exactly the same problem. It does not open Maple 15 Standard unless the termination of the input file is mw, in which case it prompts the same dialog box and its content is echoed to the input, differently to the behavior of read when called from within the UI. And indeed, this syntax produces the parse error, which appears innocuous and occurs in any UI (ie also in the CLI), even when no input file is included in the command line. And again, input files with termination mpl are opened directly in previous Standard GUI versions, though with the parse error message.

In short, I do not find this suggestion as advantageous. I wonder whether pagan got better results with it.

By the way the syntax in his barebones idea is wrong as in DOS/cmd shell the backslash "\" goes single.

As a general advice, it is better to test a new syntax first in the shell command line rather than writing a batch/unix script file with it.

@PatrickT 

Insisting with the same thing as this one for several hours is not healthy!

As I see it on Win XP 32, pagan's suggestion of using the command read from the shell command line suffers of exactly the same problem. It does not open Maple 15 Standard unless the termination of the input file is mw, in which case it prompts the same dialog box and its content is echoed to the input, differently to the behavior of read when called from within the UI. And indeed, this syntax produces the parse error, which appears innocuous and occurs in any UI (ie also in the CLI), even when no input file is included in the command line. And again, input files with termination mpl are opened directly in previous Standard GUI versions, though with the parse error message.

In short, I do not find this suggestion as advantageous. I wonder whether pagan got better results with it.

By the way the syntax in his barebones idea is wrong as in DOS/cmd shell the backslash "\" goes single.

As a general advice, it is better to test a new syntax first in the shell command line rather than writing a batch/unix script file with it.

@PatrickT 

I do not know whether there is a quick, programmatic way of converting Standard worksheets into input text files or viceversa. Never looked at it as I have not used the Standard GUI for any serious purposes. May be that something could be done using the Worksheet and XMLTools packages, similarly as Robert did above.

@PatrickT 

I do not know whether there is a quick, programmatic way of converting Standard worksheets into input text files or viceversa. Never looked at it as I have not used the Standard GUI for any serious purposes. May be that something could be done using the Worksheet and XMLTools packages, similarly as Robert did above.

@PatrickT 

Certainly, there is a quirk in Maple 15 Standard: it does not open if the input file has extension .mpl, but it does with a stupid workaround. Just change the extension to .mw (it means the same text file with different extension). Then, a "Text Format Choice" dialog box appears, and pressing "Maple Input" does open it. In previous versions the .mpl file is opened directly.

I do not know the reason of this change (for bad) or whether there is a better workaround.

@PatrickT 

Certainly, there is a quirk in Maple 15 Standard: it does not open if the input file has extension .mpl, but it does with a stupid workaround. Just change the extension to .mw (it means the same text file with different extension). Then, a "Text Format Choice" dialog box appears, and pressing "Maple Input" does open it. In previous versions the .mpl file is opened directly.

I do not know the reason of this change (for bad) or whether there is a better workaround.

@Michael 

You should be happy with those replies... At least they have said that those bugs "will be fixed", instead of saying "works as designed" or "product limitation" :)

About legality, see this thread.