That style is definitely not objectivist, real objectivist functions always take exactly one argument and return one argument.
a -> a
Rational randian functions never obey imperatives or procedures, and certainly never return void to their investors, they obey only the Rearden calculus as defined in the Rearden-Taggart theory of universal exchangability.
Re:Objectivist C
by shalmanese on Friday May 18, 2012 @06:35PM
(#3994381)
Functions take in 0 arguments and generate one argument. Arguments are created out of ontological necessity.
Re:Objectivist C
by roguecoder on Friday May 18, 2012 @01:28PM
(#3992976)
I would assume that such method calls are actually descriptive reports by lesser objects of things the superior objects have already decided they are going to do. Otherwise those superior objects wouldn't have listed them in their public interface.
"Another principle that Objectivist-C software engineers have little use for is Don’t Repeat Yourself."
But is printHelloWorld a proper function? It neither accepts something, and it returns "void". As the proper means of interaction with others is trade, this function seems rather aberrant. Functions like this probably listen to Beethoven, too.
Can a function that produces output, yet doesn't accept any parameters in return pass the compiler?