THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 28/01/2009 at 11:52, xxxxxxxx wrote:
Just wanted some insight to COFFEE for general knowledge and practical use reasons...
Coffee is certainly procedural, but does it also possesses object-oriented features as well?
Thanks.
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 28/01/2009 at 13:02, xxxxxxxx wrote:
Quote from the C.O.F.F.E.E. documentation 
What is C.O.F.F.E.E.?
C.O.F.F.E.E. is a platform independent and object-oriented programming language that can be used to develop plugins and extensions for C4D. The language is similar to C++ and Java but is more simplified, which makes it easy to learn and use.
cheers,
Matthias
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 28/01/2009 at 14:40, xxxxxxxx wrote:
Matthias,
You're killing me by making me look dumb. The SDK documentation should have been the first place that I should have looked.
Thanks.
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 28/01/2009 at 15:52, xxxxxxxx wrote:
Not dumb and good to ask. These days, most programming languages are object-oriented. The tides turned towards the mid to late 1990s away from LISP, Pascal, Fortran, COBOL, C, BASIC, and other procedural languages in favor of OOP languages, if anything, because of the compartmentability of the data and functions. Nowadays, we have C++, C#, Objective-C, Java, Javascript, Python, Ruby, COFFEE, and a host of other OOP languages. It is definitely the winning paradigm until something better comes along.
While some of these OOP languages can be 'forced' into procedural paradigms (C++ by way of its underlying C substrata but not Java, for instance), they are fully OOP-capable.
Going a bit nastalgically off topic, I started firmly in procedural programming back in the late 1980s. In the early days, OOP was a magical-mystery that was ill-explained and ill-understood. This goes for veteran computer engineers of the time - they drove masses of programmers into incorrect notions about OOP due to their vague misunderstandings. C++ itself took about ten years to evolve from a thinly-veiled C with loose-OOP into a true OOP language. One reason that I leaped from C to Java instead of C++ - there were still remnants of misunderstanding and misdirection.
Thankfully, things are better. 
