| ▲ | shevy-java 2 hours ago | ||||||||||||||||||||||
The syntax is so archaic ... it really is anything but a thing of beauty.
It's such a strange mix-up of stuff. PREVIOUS() is a macro or looks
like one, right? But it is a function call assumingly. But then what's
with .Running_Balance? Guess that also ties into a function. But why
use different syntax for essentially the same thing? It seems rather
weird to write code like that. What would the python variant be like?
Or a DSL?The syntax strangeness continues:
Does that really convey most easily what is wanted? It seems needlessly
verbose. Why would it require both $Person and $Date? Should that not
be easier to figure out in its own right? Is that efficient?People need to remember that mentally, unless they use AI. | |||||||||||||||||||||||
| ▲ | whizzter an hour ago | parent | next [-] | ||||||||||||||||||||||
I think it's an push in Spreadsheets to become more "DB-alike" for less arbitrary results (like in the problem example the article starts out with) but kind-of misguided since it's complicated to do "easy things". The root issue is that there's almost 50 years of spreadsheet syntax to consider and not colliding with. | |||||||||||||||||||||||
| ▲ | paulfitz an hour ago | parent | prev | next [-] | ||||||||||||||||||||||
It is straight Python. Yes the spreadsheet habit of making functions SHOUT does look weird mixed in with Python syntax. PREVIOUS returns a record, then .Running_Balance pulls out one field of it. | |||||||||||||||||||||||
| |||||||||||||||||||||||
| ▲ | librasteve an hour ago | parent | prev [-] | ||||||||||||||||||||||
hmmm sigils, eh? | |||||||||||||||||||||||