Well, exactly. And most of it is in the same highly inefficient style, so no wonder it is slow.

I'm not sure that it's good form to post other people's complete programs (especially when a link is possible, as Axel showed.)

acer

I looked at SHA_ROTL, and then could not look at the rest.

acer

I looked at SHA_ROTL, and then could not look at the rest.

acer

These ideas seem to suffer from skewness, either in placement of the values toward an endpoint or in respect to the distribution of the size of the jumps (while the combinat solutions apparently don't).

acer

These ideas seem to suffer from skewness, either in placement of the values toward an endpoint or in respect to the distribution of the size of the jumps (while the combinat solutions apparently don't).

acer

Very nice.

Can it stay so simple, while getting the ability to restrict the maximum stepsize as the submitter mentioned in a postscript?

acer

Very nice.

Can it stay so simple, while getting the ability to restrict the maximum stepsize as the submitter mentioned in a postscript?

acer

If you add the location of your new .mla Library archive to libname, then you ought to be able to access its contents. The ?libname help-page gives examples (Unix, but easy to adjust for MS-Windows style paths).

The command to modify the read-write permissions of a Library archive is LibraryTools:-WriteMode. Trying to use that on Maple's own installed archives would generally be a very bad idea.

Adding custom written prodecures to private archives, and reusing them after augmenting libname, is common practice. There should be no need to overwrite anything in Maple's own archives (even patches and fixes aren't implemented as direct in-place edits, but are pushed out as alternate versions in a new archive which gets found first by having a higher internal access-priority).

acer

If you add the location of your new .mla Library archive to libname, then you ought to be able to access its contents. The ?libname help-page gives examples (Unix, but easy to adjust for MS-Windows style paths).

The command to modify the read-write permissions of a Library archive is LibraryTools:-WriteMode. Trying to use that on Maple's own installed archives would generally be a very bad idea.

Adding custom written prodecures to private archives, and reusing them after augmenting libname, is common practice. There should be no need to overwrite anything in Maple's own archives (even patches and fixes aren't implemented as direct in-place edits, but are pushed out as alternate versions in a new archive which gets found first by having a higher internal access-priority).

acer

Names commonly returned by anames(user), in which you are not interested, can be removed from your inquiry.

> T:=5*Unit(degF):
> setattribute('T',"temperature"):
> L:=[4,5]:
> V:=Vector(L):
> setattribute('h',"height"):
> eqn:=T*h:

> p:=proc() local x;
>   seq([x,whattype(eval(x)),[attributes([x][1])]],
>       x in {anames('user')} minus {'lasterror','lastexception',:-p});
> end proc:

> p();
 [L, list, []], [T, *, ["temperature"]], [V, Vector[column], []], [eqn, *, []]

Note that name `h` is not reported, since it has not been assigned a value.

acer

Names commonly returned by anames(user), in which you are not interested, can be removed from your inquiry.

> T:=5*Unit(degF):
> setattribute('T',"temperature"):
> L:=[4,5]:
> V:=Vector(L):
> setattribute('h',"height"):
> eqn:=T*h:

> p:=proc() local x;
>   seq([x,whattype(eval(x)),[attributes([x][1])]],
>       x in {anames('user')} minus {'lasterror','lastexception',:-p});
> end proc:

> p();
 [L, list, []], [T, *, ["temperature"]], [V, Vector[column], []], [eqn, *, []]

Note that name `h` is not reported, since it has not been assigned a value.

acer

I think that he just ran into a name instead of a string.

> X:="18DBD3547552C73BE4DE87731C500":
> num:=convert(X,decimal,hex);
               num := 8067107224306383990011936212370688

> convert(num,hex,decimal);
                     18DBD3547552C73BE4DE87731C500

> lprint(%);
`18DBD3547552C73BE4DE87731C500`

Procedure `p` can work with names as well as with strings, since `cat` and StringTools:-LengthSplit can also.

acer

I think that he just ran into a name instead of a string.

> X:="18DBD3547552C73BE4DE87731C500":
> num:=convert(X,decimal,hex);
               num := 8067107224306383990011936212370688

> convert(num,hex,decimal);
                     18DBD3547552C73BE4DE87731C500

> lprint(%);
`18DBD3547552C73BE4DE87731C500`

Procedure `p` can work with names as well as with strings, since `cat` and StringTools:-LengthSplit can also.

acer

That is an interesting notion, Axel -- that the default installation location (folder name) for Maple, with a space in it, might cause problems for using OpenMaple with the default MS compiler. I wonder if there's anything else that the space can cause problems for. It's a nice commonsense tip, to always remove the space when selecting an installation location.

acer

That is an interesting notion, Axel -- that the default installation location (folder name) for Maple, with a space in it, might cause problems for using OpenMaple with the default MS compiler. I wonder if there's anything else that the space can cause problems for. It's a nice commonsense tip, to always remove the space when selecting an installation location.

acer