Hi. That's the Mathematica default notation for pure function's arguments: https://reference.wolfra...rkWithPureFunctions.html

Best regards.
Alvaro.

Expanding the idea of ​​numbering, we can add syntax:

## - take all as sys|mat|line
#i#j - take from i to j
##j - take from 1 to j
#i# - take from i to end

and

#i#js - sys(#i,..,#j)
#i#jm - mat(#i,..,#j)
#i#jl - line(#i,..,#j)

#i#jfun - fun(#i,..,#j)

or

### - insert as parameters: foo(x,y,###) -> foo(x,y,#1,#2,...)
##3# - insert as parameters: foo(x,y,##3#) -> foo(x,y,#1,#2,#3)

A little step further? (And I say little because I'm not the one who has to improve the code) Take #arg as function parameter?



Best regards.
Alvaro.

mathcadblock-alnleqsolve.sm (13kb) downloaded 9 time(s).

Edited by user 15 November 2024 11:17:14(UTC)  | Reason: Not specified

I want to add a set of simple examples to the Mathcad block context menu that demonstrate how it works. Can you suggest such examples?
Similar to the X-Y Plot component. In this case, you will be able to fill in not only the input values, but also the description. You can insert arbitrary expressions inside the component.
Imagine that you can formalize the solution to a simple problem. What would you suggest as educational examples?

Edited by user 12 December 2024 10:16:51(UTC)  | Reason: Not specified

I'd like to have such things like nsol in SMath core.

How about embedded assignment, similar to FindRoot? I don't like poking the values out of S. I see that this might reduce flexibility, e.g. in the case of parametrized initial guess.

I tried to demonstrate a generic approach, i.e. you get the variables assigned without having to issue any specific command except for the generic content of the placeholder. It is just a try and fails with single variables but you get the idea.

Of course, one would like to have a solve block without the cryptic generic expression in the placeholder.

Perhaps, such a block could be created from the insert menu with pre-allocated content of the placeholder and with setting it to hidden.


BasicHandbook-nsol_Kr.sm (334kb) downloaded 8 time(s).

Hi Martin. I think the opposite: the implicit assignment of the names of the variables sought to a solution makes its call very rigid, since many times there is no direct relationship between the variables of the equation and the names of the variables that are intended to be assigned to the solution, as is precisely demonstrated in this case



Another variant among many would be to find a limiting speed and call the result v.lim, even though the variable of the equation is "v".

Best regards.
Alvaro.