tl;dr In principle, yes. In practice, it's not worth the (considerable) trouble.
In Mathematica, everything is an expression. That applies to both code and data. The standard textual representation of expressions is what InputForm
returns and what we normally think of as the Wolfram language (Mathematica's programming language). But in principle you can come up with alternative representations. In fact you'll be able to find a few examples of this:
- ExpressionML is an XML representation of Mathematica expressions
TraditionalForm
uses f(x)
instead of f[x]
and is meant to look like traditional mathematical notation (but it is ambiguous and thus not suitable for programming)
You can come up with your own representation and write a parser that converts it to input form. Then use $PreRead
to process everything through that custom parser.
This should be a considerably easier task than coming up with alternative syntaxes for other programming languages due to to uniformity, simplicity and transparency of Mathematica's expression structure. You can start with a minimalistic notation (something akin to FullForm
) and already have a language which is usable at least in principle. Then add various operators and shorthands (such as a+b
for Plus[a,b]
) gradually, according to your needs. But by no means will it be a simple or small project. Nor can I see how you or anyone else would realistically benefit from it. No one except you will be able to read this sort of code, and it would be much easier for you to just get used to the standard Mathematica notation. But making an alternative notation might be a good learning project anyway, e.g. if you would like to learn more about parsers or would like to get experience with designing a new language syntax.
TraditionalForm
-- it should meet your needs $\endgroup$