I find this discussion fascinating. It reminded me of an idea that I've been playing with: whether abstract linear algebra (for use with LinearAlgebra, say) might be done reasonably well using attributes. Attributes on just what,.. that I don't know. acer

I tried this in both Maple 11.00 and 10.06, just for fun. In 10.06 it ran longer and seemed to use more memory. Interestingly, in 11.00 I saw no garbage collection messages while in 10.06 I did see gc update messages. I'm not sure how to reconcile that with more apparent memory consumption/use in 10.06. acer

I tried this in both Maple 11.00 and 10.06, just for fun. In 10.06 it ran longer and seemed to use more memory. Interestingly, in 11.00 I saw no garbage collection messages while in 10.06 I did see gc update messages. I'm not sure how to reconcile that with more apparent memory consumption/use in 10.06. acer

I'm not sure what it means, to be "first class objects" in Maple. Hardware scalar floats can exist stand-alone. But they'll only come into being (apart from when using their constructor explicitly) within a proc with option hfloat. > kernelopts(version); Maple 11.00, X86 64 LINUX, Feb 16 2007 Build ID 277223 > x:=HFloat(1.2); x := 1.19999999999999996 > dismantle(%); HFLOAT(2): 1.2 Also, see ?option_hfloat acer

I'm not sure what it means, to be "first class objects" in Maple. Hardware scalar floats can exist stand-alone. But they'll only come into being (apart from when using their constructor explicitly) within a proc with option hfloat. > kernelopts(version); Maple 11.00, X86 64 LINUX, Feb 16 2007 Build ID 277223 > x:=HFloat(1.2); x := 1.19999999999999996 > dismantle(%); HFLOAT(2): 1.2 Also, see ?option_hfloat acer

The mixture sin-Pi isn't very useful. Does one apply it, as an operator, or evaluate it at a point, or...? > k := sin-Pi; k := sin - Pi > k(1.1); 0.8912073601 - Pi(1.1) > eval(k(x),x=1.1); 0.8912073601 - Pi(1.1) How would you plot it? Distinguishing between sin-1/2 and sin-sqrt(2) seems inconsistent to me. acer

R[3] accesses the 3rd entry of Vector R. More abstractly, R[i] accesses the ith entry, given a positive integer i less than the upper index bound (here, 10^6). You can also extract sub-Vectors, eg. R[3..11] . If Vector R has a million entries, then how would you want to look at them? ArrayTools[AddAlongDimension](R) should sum all the entries in Vector R. acer

R[3] accesses the 3rd entry of Vector R. More abstractly, R[i] accesses the ith entry, given a positive integer i less than the upper index bound (here, 10^6). You can also extract sub-Vectors, eg. R[3..11] . If Vector R has a million entries, then how would you want to look at them? ArrayTools[AddAlongDimension](R) should sum all the entries in Vector R. acer

I used a Vector, rather than a list, to store the final result. And I gave it a hardware datatype, just to try to keep allocation down. I don't think that I used lists at all, trying instead to use add() to sum the 12 values (at each iteration) without forming the sequences explicitly. acer

I used a Vector, rather than a list, to store the final result. And I gave it a hardware datatype, just to try to keep allocation down. I don't think that I used lists at all, trying instead to use add() to sum the 12 values (at each iteration) without forming the sequences explicitly. acer

Running all the built-in functions with no arguments should be done as part of basic testing and quality assurance. acer

> kernelopts(version); Maple 11.00, X86 64 LINUX, Feb 16 2007 Build ID 277223 > `^`(f); Execution stopped: Stack limit reached. That's 8 keystrokes, counting the return. acer

A post by DJKeenan contains, `^`(`$`(x,n)); Maple 10.2 gave "Error, invalid input: ^ expects 2 arguments, but received 1" for that input. But Maple 11.00 (and 11.01 it seems) crash immediately with "Execution stopped: Stack limit reached". That's 15 keystrokes, including the return. A moderately interesting variation is this, which cuts out two keystrokes, `^`($(x, n)); acer

The Matrix and Vector constructors will generally attempt to "flatten" the data, for most input forms. But someone might actually want to create a Vector of rtable objects, with no flattening occuring during construction. Someone else might want or expect flattening, and be caught unawares when it was not done, and for that user an error raised may be helpful. So, some balance is needed, to get all these effects. Personally I don't find the current behaviour of Vector() to be so bad, since the square-brackets are also used to delimit data (separating rows, say) for the Matrix constructor. Having written all that, what is the corresponding format for entering an unflattened Matrix of other rtables? When I tried a similar thing, with Matrix(), I obtained a Matrix whose entries were actual lists. Maybe there's a way, that I did not see. acer

Hi Roman, Is enabling system/ssystem calls only necessary to install it? Or is it required in order to run the package (and if so, why, may I ask)? What's the story behind the commented-out free_memory() call in the ModuleUnload of module sdmp? Does the compiled shared object do its own memory management, and if so why, and what would happen if it couldn't free on restart? Have you considered distributing the mpl sources in a .mla file, and the .mw as an embedded help-page within a .hdb file? Have you considered using InstallerBuilder from Maple to create a self-installing .mla (container, which unpacks the various files)? How about putting the materials under a subdirectory of /toolbox/ , so that .mla/.hdb and bin. get found automagically by the maple kernel? acer