Robert,

I also have Windows XP and Wordpad and Maple 12, and I tried your technique twice--being careful not to select the single black > in the Wordpad text. Both times the final result had the > symbols at the beginning of each line in Standard.  I was able to execute the code.   It just doesn't look good.

It is interesting that the problem doesn't occur when copying and pasting from one Standard worksheet to itself or to another Standard worksheet. But for me if I go thru a copy and paste in Wordpad, the problem of the extra >s persists.

I am not so much interested in Classic to Standard, but just text to Standard.  All input is 1d.

Edwin

 

 

Robert,

I also have Windows XP and Wordpad and Maple 12, and I tried your technique twice--being careful not to select the single black > in the Wordpad text. Both times the final result had the > symbols at the beginning of each line in Standard.  I was able to execute the code.   It just doesn't look good.

It is interesting that the problem doesn't occur when copying and pasting from one Standard worksheet to itself or to another Standard worksheet. But for me if I go thru a copy and paste in Wordpad, the problem of the extra >s persists.

I am not so much interested in Classic to Standard, but just text to Standard.  All input is 1d.

Edwin

 

 

Thanks, Alec and Acer.

Alec's suggestion  to replace print(lasterror) by

print(StringTools:-FormatMessage(lastexception[2..-1]));

gives the best output and I see that it is given as an example at ?error.

But I will probably forget it by the time I next need to use it.  I guess the easiest thing to do is just print("something is wrong") and let it go at that.

Cheers,

Edwin

 

Hi Alex, In Maple 12 standard your suggestion apparently doesn't apply.

Axel, with Maple 12 Classic I have no such problem. When pasting into Classic from say Notepad I don't get those nasty prompts at the beginning of each line. Lately I have been doing a lot  of graphics with standard Maple 12 and this problem has started to annoy me. There ought to be a simple way to do this with the standard interface.  Your method doesn't work for me using Word and standard Maple.

I can avoid the problem by reading in the file where the code is located, but sometimes I want to do a quick check of something by cutting and pasting.

To make matters worse when I try to copy and paste from Maple Classic to Maple Standard I get >> at the beginning of each line and the code will not execute.  For example if I copy and paste the following from Maple Classic

>for i from 1 to 10 do
 i;
od;

to standard interface Maple I get

>for i from 1 to 10 do
>>i;
>>od;

and if I try to execute the latter I get:   Error, `>` unexpected

 

Hi Alex, In Maple 12 standard your suggestion apparently doesn't apply.

Axel, with Maple 12 Classic I have no such problem. When pasting into Classic from say Notepad I don't get those nasty prompts at the beginning of each line. Lately I have been doing a lot  of graphics with standard Maple 12 and this problem has started to annoy me. There ought to be a simple way to do this with the standard interface.  Your method doesn't work for me using Word and standard Maple.

I can avoid the problem by reading in the file where the code is located, but sometimes I want to do a quick check of something by cutting and pasting.

To make matters worse when I try to copy and paste from Maple Classic to Maple Standard I get >> at the beginning of each line and the code will not execute.  For example if I copy and paste the following from Maple Classic

>for i from 1 to 10 do
 i;
od;

to standard interface Maple I get

>for i from 1 to 10 do
>>i;
>>od;

and if I try to execute the latter I get:   Error, `>` unexpected

 

Thanks Acer, But I don't see how to use that in my applications. Perhaps you can see how to use it in the procedures AreEqual and IsMemberOf in my thread "Equality of sets (and sets of sets) of lists of floating point real numbers" (in "How do I ...? with Maple"). --Edwin PS I don't see how to link directly to another posting in this forum. It would help if individual posts were numbered. Or, perhaps they are and I just don't see the numbers?

Thanks Scott, Now I see my problem. I now see why evalf[10] has always frustrated me. I wanted something to return for evalf[10](0+1.0*10^(-30)) the number 0.0000000000 Now I see that it doesn't behave that way. Edwin

I agree that a video podcast would be much better. Something like www.rocketboom.com--only with Maple topics.

In my case the problem was that in geom3d "point(A,P1)" assigns to the list P1 the name A. Then in the line > rotation(Q,P,evalf(theta),el); rotation is supposed to rotate P throught theta radian about the line el into a new point named Q. But I used "point" in place of Q, so I was changing the definition of the procedure "point". Then Maple is confused about the meaning of point and next time it is used trouble is inevitable.