Someone added "Duplicate question" tag on this question.

How is this duplicate question? Where is the duplicate question? 

Is this a bug?

Accoding to this help page 

A derived class must not redeclare (via a local or export declaration) any members inherited from the base class

this example does not do this. But derived class gets an error when using ::static on a method declared in base class and this only shows up when using kernelopts('assertlevel'=2):

So it is either kernelopts('assertlevel'=2): is wrong or help is wrong.  Here is example

Download static_error.mw

Removing the line kernelopts('assertlevel'=2): the error goes away. Also keeping kernelopts('assertlevel'=2): but removing the ::static from the derived class the error goes way.

What is going on?

Maple 2023 on windows 10.

When making a module with option object, help says 

To create a new class of objects, use the named module declaration syntax with option object.

and it gives an example.  But what is the difference from using the standard module syntax?

This seems to work the same but may be there are cases where it makes a difference?  Here is an example. second case below is what help says to use. But first case is the original module syntax. Both work the same in this simple example.

Can one use either syntax, or is there any subtle difference in semantics that will show under more complicated setup?

Download syntax_of_OOP_module.mw

In traditional OOP, one can have a base class with its own constructor. Then extends this class, where the sub class has also its own consturctor. The first thing one does in the extending class constructor is to initialize the base class by calling base class constructor directly, before finishing the initializing of the extending class.

This is done in different ways. in Java the call super(...) is used for example. in C++ it is done by explicit call to base class constructor. Here is an example.  from the net.

But in Maple, I am not able to duplicate this. Because once ModuleCopy is defined (which is the name for the module constructor) in the base class, I can't have another ModuleCopy in the extending/child class. Maple complains because the name already exists.

In the following example, the base class represents a generic ode.

Then the extending/child class is meant to represent a first order ode which extends the base class and adds some specific functions that only meant to apply for first order ode type.

Later on I want to make a second order ode class and so on. All extend the base ode class. 

My question is: How to extend a class in Maple and have the extending/child class constructor call the base class constructor if one can't have more than one constructor when extending?

This Maple help shows one example of inhertance using Objects but this example does not use a constructor in the base of the child. I am assuming one needs to use ModuleCopy as the name for the constuctor since it specifies how an object is copied by Object so can't make my own function and pretend it is the constructor.

Download base_class_constructor.mw

UPDATE

This is workaround which seems to work OK. do not use ModuleCopy to construct an object, but have custom named function for each base and each child and call these explicitly.

So child constructor will  now call its parent constuctor using the specific name of that function. May be using some convention as  module_name_constuctor(....)   passing it what the parents needs.

The drawback is that now copying an object does not work automatically since ModuleCopy is missing.  but so far, I never had the need to copy one object to another, so I can live without it for now.
 

I think Maple OOP is not fully OOP,  but it is better than nothing.

Download base_class_no_constructor.mw

I was translating some code from Mathematica to Maple. Why MmaTranslator does not know about Mathematica's CubeRoot function? This was added in 2012 (more than 11 years ago).

Is this known? How could one teach Maple's MmaTranslator to convert CubeRoot[x] to surd(x,3)? Is it possible to manually add missing translations to this package? Otherwise I would have to manually edit lots of code and do this myself each time.

restart; 
with(MmaTranslator);
FromMma(`CubeRoot[9]`);

Gives CubeRoot(9) it should be surd(9, 3)

Version 2023 on windows 10

Is there a mathematical reason why Maple does not allow expansion point for solving an ode using series solution to be different than where initial conditions are located?

I do not see why this restriction is there. Here is first order ode, where expansion point is x=1 and initial condiitons are also at x=1

restart;
ode:=diff(y(x),x)=x^3;
dsolve([ode,y(1)=1],y(x),'series',x=1)

            y(x) = (1 + (x - 1)) + 3/2*(x - 1)^2 + (x - 1)^3 + 1/4*(x - 1)^4 + O((x - 1)^6)

No problem. But when expansion point at x=0, it complains

restart;
ode:=diff(y(x),x)=x^3;
dsolve([ode,y(1)=1],y(x),'series',x=0)

Error, (in dsolve/SERIES) conflicting specifications of the series expansion point: 1 v.s. 0

I know help mentions that it uses initial conditions point for expansion if given, and if no IC is given, then it uses x=point if given and if no x=point is given then it default to x=0.

But my question is, why it does not handle the case when the expansion point is given explicitly and is at a different location than where IC are given? Is this simply just a feature missing that could be added in a future release if needed, or is it due to some mathematical reason that I do not see?

I would have expected it to first find the series solution around the given expansion point, then use the IC to determine the unknown constant after that, just like we normally do when solving an ode using standard methods not using series expansion.

I am using Maple 2023