@Carl Love What I gave you is an empty example. All it does is count invocations of function g in trivial constructions.
The expression is the fundament of SC. A code is an expression and an expression is a code. This duality makes SC codes easy to read and understand. Composing, manipulating, sampling, evaluating, inspecting, decomposing is first in SC. I am not saying "it is available", I am saying "it is the base". And so as I would expect [[[[[[g(0)]]]]]] is same as [[[[[[g]]]]]](0), but unexpectedly [[[[[[g(0)(0)]]]]]] I find is not [[[[[[g]]]]]](0)(0) nor [[[[[[g(0)]]]]]](0). Even more surprisingly the last two are equal. Ofcourse all of this can be explained by kernel rules but it matters not. What is clear Maple is not SC based. It is OOP based. The consequences can be seen in the results.
My first Maple was 5.4 and it certainly was SC base. They have alluded they would be implementing modules and overloading. I have easily imagined the implements. Why they sacked SC I cannot imagine.