X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=vPK/J67DPbw5z2I1N8KFHM5Px1yMVuj0o4LXEWcThZo=; b=zj51tkgZXgp2KpXRle6nwLh/KRI7SEAbCFbR/8WTAkvyHaQarObOki0r4dlkq2iY2J akm1K20Y3FCeYkGilLa2s8wPLQ2DMBwD/YwDvmbouRCtw/AOQJbCY/MOQ4vMzLcQu7WD yEfY0KYTJkObZlkur6qW8ZXyP5BIHECW06ebFaJiPbnZ6Vqs23/AakuEqaZ9+wIeRHjY cDmiBsjguu+FqtVVDDAXv+Qu71k7hQm44jnLHEHLLRfQ2s8VwnL+dvG4JcKVtPKmZ2kP wrcCGs3x+PkYa+R0WM5NS0fZyuvBlKIOw7dq+v/vx185d1LzUDABWtrcw42KBwBWaTnP DdvQ== MIME-Version: 1.0 X-Received: by 10.50.78.231 with SMTP id e7mr24879118igx.93.1445948457134; Tue, 27 Oct 2015 05:20:57 -0700 (PDT) In-Reply-To: <20151027121151.84a401be8b0d162eea027ad9@gmail.com> References: <20151027103752 DOT 17300 DOT qmail AT stuge DOT se> <20151027121151 DOT 84a401be8b0d162eea027ad9 AT gmail DOT com> Date: Tue, 27 Oct 2015 13:20:57 +0100 Message-ID: Subject: Re: [geda-user] home/bkerin/geometry_module branch From: "Levente (leventelist AT gmail DOT com) [via geda-user AT delorie DOT com]" To: gEDA User Mailing List Content-Type: multipart/alternative; boundary=089e013c649e26b9f40523151c19 Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk --089e013c649e26b9f40523151c19 Content-Type: text/plain; charset=UTF-8 Okay people... sorry. Calm down. Let us start a technical discussion. Igor2: I didn't want to reflect your other points. There is for exaple distance calculation code, polygon handling, so for example we could detect polygons that are fully covered by another one. That is only one thing. But there are others. > Levente (leventelist AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: > > transform PCB to C++ > > That's orthogonal to new geometry code. > > > > I think C++ is a better tool to code a PCB editor application than C. > > I don't neccessarily agree but regardless of that, the current code is C. > > It's not at all impossible to use a C++ library from C code but it > requires writing a wrapper. > > > //Peter Other direction is easier. To use C functions from C++ is simple and it is not to hard to export C functions from C++. Nicklas Karlsson --089e013c649e26b9f40523151c19 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Okay people... sorry. Calm down.

Let us start a technical discussion.

Igor2: I didn't want to reflect your other points.

There is for exaple distance calculation code, polygon handl= ing, so for example we could detect polygons that are fully covered by anot= her one. That is only one thing.
But there are others.

> Levente (leventelist AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
> > transform PCB to C++
>
> That's orthogonal to new geometry code.
>
>
> > I think C++ is a better tool to code a PCB editor application tha= n C.
>
> I don't neccessarily agree but regardless of that, the current cod= e is C.
>
> It's not at all impossible to use a C++ library from C code but it=
> requires writing a wrapper.
>
>
> //Peter

Other direction is easier. To use C functions from C++ is simple and it is = not to hard to export C functions from C++.

Nicklas Karlsson
--089e013c649e26b9f40523151c19--