I'm not sure if I understand your point, but in every instance you have listed (aside from code direction or difference in programming languages), the syntax would follow the raw data. Am I right? I mean you have a Raw data in the first place and after that you decide how to manage it (based on specific syntax of your program).
My point is only that there are programming languages which do have the codes such that they are read from left to right, like the ML family of languages.
Yes, there are many syntactic differences between programming languages, but in this case we are just discussing the path of thought. Thank you for your attention
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Let's say you want to get the user's name, capitalize it (which may be incorrect... sorry k d lang), convert it to a greeting, and print it out.
Most languages would do it this way, in pseudo-code:
And could do it as a one liner, also in pseudo-code:
See the onion-like nesting? Just like what the article is talking about. This code is read inside-out to see the order of operations.
There are other programming languages that would do the one-liner in a slightly different way, in pseudo-code:
No onion! It reads in order, more like the first step-by-step example.
I'm not sure if I understand your point, but in every instance you have listed (aside from code direction or difference in programming languages), the syntax would follow the raw data. Am I right? I mean you have a Raw data in the first place and after that you decide how to manage it (based on specific syntax of your program).
My point is only that there are programming languages which do have the codes such that they are read from left to right, like the ML family of languages.
Yes, there are many syntactic differences between programming languages, but in this case we are just discussing the path of thought. Thank you for your attention