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 av01.lsn.net
Message-ID:	<55A0209A.6000806@ecosensory.com>
Date:	Fri, 10 Jul 2015 14:44:26 -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:	Re: [geda-user] coding
References:	<55A00240 DOT 9060404 AT ecosensory DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1507102001230 DOT 6924 AT igor2priv>
In-Reply-To:	<alpine.DEB.2.00.1507102001230.6924@igor2priv>
Reply-To:	geda-user AT delorie DOT com

On 07/10/2015 01:08 PM, gedau AT igor2 DOT repo DOT hu wrote:
> I am not sure I fully understand the context; are you looking for a tool that can extract the return type and the type of
> arguments of a C function reading the source?
>
> If so, I happen to have a project called c99tree. It parses C files and emits an AST (Abstract Syntax Tree). With some scripting,
> it's possible to extract info on function argument types which then can be used to generate bindings or validate the API.

Yes, that's promising.

Embedding old code in a new language might be a way to generate interest.

Pony may be too new, too few users, but maybe some others.

On 07/10/2015 01:13 PM, Stefan Salewski wrote:> I prefered writing rect.draw
 > instead of draw_rectangle(rect).
+1

First saw that with Python.


On 07/10/2015 01:13 PM, Stefan Salewski wrote:> I think I will concentrate on Nim for the next year, it has the
 > advantage being close to version 1.0 already and having really all low
 > level functionality, so that kernel and microcontroller coding is
 > possible.

Hmmm...  micros and such are my interest also, and being community supported is tops on my list,
so Nim is the one to study up on. Or rust....   Or ??   :-)


On 07/10/2015 01:19 PM, Stefan Salewski wrote:> Nim uses a similar tool called c2nim, which processes C files and
 > generation Nim code. Mainly used for processing C header files, I used
 > that for creating the GTK3 bindings. Works fine generally

Wow.

How about erlang elixir?  That has some proving ground testing done.

For instance say I wanted to reuse the ConTiki mesh networking code, plus add lwip for ethernet.
Would nim handle that?  Could you autogenerate and retest in a couple of weeks, or would it be five-hundreds of hours?

On 07/10/2015 01:59 PM, DJ Delorie wrote:> OO allows you to provide an API
 > between parts of your program that reduces the overhead of adding more
 > "things" of each type.

So, OO is usually built in.  Some of the langs that support functional and paralleling
don't mention it.  Will want to look for it in erlang/elixir, rust, nim, go...

- Raw text -