jakubi

1384 Reputation

12 Badges

20 years, 1 days

MaplePrimes Activity


These are replies submitted by jakubi

A bit of testing and a bit of intuition.

You said elsewhere that you use a dictionary, etc, for English. I do not know what the expression "on God's green Earth" means. What have you found for it? Or, do you have a pointer to a good online "dictionary" of English expressions?

Certainly, it is important that this failures to produce math images be corrected as soon as possible. Note also that I have not got make it work with the comma yet.

This leaf is dedicated to the Mapleprimes team. Had the site worked better, I would not have got it.

 

table[]; ``[table[1,2]]; ``[table[3,4]];

Code:

<maple> table[]; </maple> <maple>``[table[1,2]];</maple>   <maple>``[table[3,4]];</maple>

I can read this article, apparently  without  registration.

Is it usual in Northamerica that software companies face lawsuits because of false advertising?

 

whimsical: determined by chance or impulse or whim rather than by necessity or reason.

Interesting. The words identify the personality. There should be something more than phonetics.  

frequently sound to me nonsensical, not being a native English speaker. This one is no exception. Hence hardly I could get it. It sounds to me something like "waterloo-maple-musical".

This way I get 'true' for any input that I have tried.

This way I get 'true' for any input that I have tried.

The mathml code example in Posting 2D Math on MaplePrimes does not seem to work at present.

The page How can I login? is a bit outdated.

on her age. So, right or wrong it would not be much of gentleman...

But OK, chances are she is Paulina Chin.

I find it absurd applying mathematical typesetting rules to pure computational objects.

But, may be that this issue should be moved to a new thread.

Property expressions? Where are they clearly listed and described? (I mean something like ?property ). Should there be a type for them? (if there is none).

There is in ?assume a possible parameter listed:

 xpropreli        - relation describing property propi on expression xi
 

but there is not much more explanation. And I do not find that relation is a proper name for eg Not(x::posint).

Property expressions? Where are they clearly listed and described? (I mean something like ?property ). Should there be a type for them? (if there is none).

There is in ?assume a possible parameter listed:

 xpropreli        - relation describing property propi on expression xi
 

but there is not much more explanation. And I do not find that relation is a proper name for eg Not(x::posint).

You read in ?assume:

AndProp(a,b,...) an and expression of properties,                           
                 a and b and .. where a, b, etc.                            
                 are properties as defined above.

and say OK, the phrase/relation 'x>0' is not a property and it should not be used as argument of 'AndProp'. But I get:

 

assume(AndProp(x>0,x<2));about(x);
Originally x, renamed x~:

  is assumed to be: RealRange(Open(0),Open(2))

And so on. You may argue bug in the documentation. It is debatable. The documentation on the assume facility is confusing to my taste (though it has being improving). I wonder whether the behavior up to Maple 10 is a bug, an issue of design in the handling of properties or a problem in documentation. Perhaps it was change about what is right or wrong.

You read in ?assume:

AndProp(a,b,...) an and expression of properties,                           
                 a and b and .. where a, b, etc.                            
                 are properties as defined above.

and say OK, the phrase/relation 'x>0' is not a property and it should not be used as argument of 'AndProp'. But I get:

 

assume(AndProp(x>0,x<2));about(x);
Originally x, renamed x~:

  is assumed to be: RealRange(Open(0),Open(2))

And so on. You may argue bug in the documentation. It is debatable. The documentation on the assume facility is confusing to my taste (though it has being improving). I wonder whether the behavior up to Maple 10 is a bug, an issue of design in the handling of properties or a problem in documentation. Perhaps it was change about what is right or wrong.

First 108 109 110 111 112 113 114 Last Page 110 of 123