X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.98.4 at av02.lsn.net
Message-ID: <55A00240.9060404@ecosensory.com>
Date: Fri, 10 Jul 2015 12:34:56 -0500
From: John Griessen <john AT ecosensory DOT com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.6.0
MIME-Version: 1.0
To: geda-user AT delorie DOT com
Subject: [geda-user] coding
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: geda-user AT delorie DOT com

If object oriented is out of style now, what was it ever good for?

I used to skim OO books and yet only dabbled in scripts to go along with chip design, so not too deeply.
OO was "the buzzword", so I thought it must be great.  Never could see much rhyme or reason to using
the word class for objects that inherit in java though...  Java seemed to use that word as name for a group
of objects, and for an object at the same time, so I thought that was a readability problem.

I just read some about the Pony language and like the intro very much, since it talks about how parallelling
bits of sequential code is low overhead -- Yay!, that's what you want usually.

Now if it allows using existing code safely, simply,  (code that is self contained or its ins and outs are well documented),
doing a rewrite with it could be breezy easy.  Pony intro talks of having a FFI (foreign function interface)
for calling C, but all Pony warranties are void when you do so, because mid level C language is inherently
powerful/deadly.  Pony intro says, "you MUST get the parameter and return types right."

So, using existing C inside of Pony is full manual.

Is there any kind of tool for sifting through code chunks in C and extracting such parameters and returns
so its easier to check them?  Do any of the auto documenting programs like doxygen help with that?