zoomablemind
Joined 8 years ago
Joined 8 years ago
That's quite remarkable. How detailed was your prompting to specify the incorrect and desired behavior?
On so many occasions I would get blinded by overly bright lights of an incoming cyclist during late evening ride.
Investment fund's commodity is value - the rest are just tools to optimize the value.
If anything, it had been quite customary to supply references for some important facts. Thus letting readers to explore further and interpret the facts.
With AI in the mix the references become even more important, in the view of hallucinations and fact poisoning.
Otherwise, it's a forum. Voting, flagging, ignoring are the usual tools.
I wonder what is author's view about user's reasons to choose a C API?
What I mean is users may want exactly the same freedom and immediacy of C that the author embraces. However, the very approach to encapsulation by hiding the layout of the memory, the use of accessor functions limits the user's freedom and robs them of performance too.
In my view, the choice of using C in projects comes with certain responsibilities and expectations from the user. Thus higher degree of trust to the API user is due.
Well, apparently [0], in a 1947 document "Planning and Coding Problems for an Electronic Computing Instrument, Part 1" by H. Goldstine and J. von Neumann it is stated:
"We call the coded sequence of a problem a routine"
[0]: https://retrocomputing.stackexchange.com/q/20335I always thought that the functions did not need a call keyword, as they normally would return a value, so that functions would appear in an assignment. So one just uses the function.
What needed a CALL was a subroutine, which effectively was a named address/label.
Indeed it would be just as possible to GOTO the address/label and then GOTO back. CALL keyword made the whole transaction more comprehensive.
So in a sense it was similar to calling up someplace using the address number. Often times this would change some shared state so that the caller would then proceed after the call. Think of it as if a 'boss' first calls Sam to calculate the figures, then calls Bill to nicely print the TPS report.
Eventually everything became a function and subroutines were associated with spaghetti...
Now, why is that it's called routine (aka program) and subroutine?
Say, if I wanted to see immediate effects of changing an incidence angle, could I just "scroll" the incidence parameter?
I like the idea. Happy New Year!