--- /dev/null
+Return-path: <libre-riscv-dev-bounces@lists.libre-riscv.org>
+Envelope-to: publicinbox@libre-riscv.org
+Delivery-date: Tue, 31 Mar 2020 15:11:51 +0100
+Received: from localhost ([::1] helo=libre-riscv.org)
+ by libre-riscv.org with esmtp (Exim 4.89)
+ (envelope-from <libre-riscv-dev-bounces@lists.libre-riscv.org>)
+ id 1jJHcL-0007AV-Rb; Tue, 31 Mar 2020 15:11:49 +0100
+Received: from isis.lip6.fr ([132.227.60.2])
+ by libre-riscv.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
+ (Exim 4.89) (envelope-from <Jean-Paul.Chaput@lip6.fr>)
+ id 1jJHcJ-0007AP-Up
+ for libre-riscv-dev@lists.libre-riscv.org; Tue, 31 Mar 2020 15:11:47 +0100
+Received: from asim.lip6.fr (asim.lip6.fr [132.227.86.2])
+ by isis.lip6.fr (8.15.2/8.15.2) with ESMTPS id 02VEBkNm008538
+ (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
+ Tue, 31 Mar 2020 16:11:46 +0200 (CEST)
+Received: from localhost (melon [132.227.103.13])
+ by asim.lip6.fr (8.15.2/8.14.4) with ESMTP id 02VEBkqJ021742;
+ Tue, 31 Mar 2020 16:11:46 +0200 (MEST)
+Message-ID: <e01a01fb87d745f34fa4b8e71445fb1777f308c6.camel@lip6.fr>
+From: Jean-Paul Chaput <Jean-Paul.Chaput@lip6.fr>
+To: "lkcl ." <luke.leighton@gmail.com>, Libre-RISCV General Development
+ <libre-riscv-dev@lists.libre-riscv.org>, Marie-Minerve
+ =?ISO-8859-1?Q?Lou=EBrat?= <Marie-Minerve.Louerat@lip6.fr>
+Date: Tue, 31 Mar 2020 16:11:35 +0200
+In-Reply-To: <CAPweEDx=aGvp8KbhdipG5Lt=Uo9p7L2miEmP88FcAPFvQnnryw@mail.gmail.com>
+References: <CAPweEDw_h8VQ3JJFF3FXph7Eg0ucVknuvMk=Xc0jSp0WP13=UQ@mail.gmail.com>
+ <8fb9dbcc812d3d7050c6e336dc9bf68f88536888.camel@gmail.com>
+ <de619dbb67b22514be18f4a8e4282d90de502cf6.camel@lip6.fr>
+ <CAPweEDyJKoUdHeDrQTHLWj7S42T=FDwj6bsnvCPoFHaf7bGy-Q@mail.gmail.com>
+ <752371e7a9de77d78305af838989817bfec4fda8.camel@lip6.fr>
+ <CAPweEDzGM3KEeMQWh5_wvePa4bHJvDZJExdLCVjmaMije5Jzrg@mail.gmail.com>
+ <CAPweEDwz3n_jMS2NFFU=FJe4m82QqvG9XU2e9N474s7ZKj-VcA@mail.gmail.com>
+ <CAPweEDzxhDpfv8hH5nJnJn=RCMdVkk5RZAndxvo1z1jd2AQw5Q@mail.gmail.com>
+ <CAPweEDx=aGvp8KbhdipG5Lt=Uo9p7L2miEmP88FcAPFvQnnryw@mail.gmail.com>
+Organization: UPMC
+X-Mailer: Evolution 3.28.5 (3.28.5-5.el7)
+Mime-Version: 1.0
+X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
+ (isis.lip6.fr [132.227.60.2]); Tue, 31 Mar 2020 16:11:46 +0200 (CEST)
+X-Scanned-By: MIMEDefang 2.78 on 132.227.60.2
+X-Content-Filtered-By: Mailman/MimeDel 2.1.23
+Subject: Re: [libre-riscv-dev] pyobjc, gnu objective-c and gnustep
+X-BeenThere: libre-riscv-dev@lists.libre-riscv.org
+X-Mailman-Version: 2.1.23
+Precedence: list
+List-Id: Libre-RISCV General Development
+ <libre-riscv-dev.lists.libre-riscv.org>
+List-Unsubscribe: <http://lists.libre-riscv.org/mailman/options/libre-riscv-dev>,
+ <mailto:libre-riscv-dev-request@lists.libre-riscv.org?subject=unsubscribe>
+List-Archive: <http://lists.libre-riscv.org/pipermail/libre-riscv-dev/>
+List-Post: <mailto:libre-riscv-dev@lists.libre-riscv.org>
+List-Help: <mailto:libre-riscv-dev-request@lists.libre-riscv.org?subject=help>
+List-Subscribe: <http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev>,
+ <mailto:libre-riscv-dev-request@lists.libre-riscv.org?subject=subscribe>
+Reply-To: Libre-RISCV General Development
+ <libre-riscv-dev@lists.libre-riscv.org>
+Content-Type: multipart/mixed; boundary="===============9156565726221374067=="
+Errors-To: libre-riscv-dev-bounces@lists.libre-riscv.org
+Sender: "libre-riscv-dev" <libre-riscv-dev-bounces@lists.libre-riscv.org>
+
+
+--===============9156565726221374067==
+Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature";
+ boundary="=-1xMN/UKcAW4fqZhcLB9V"
+
+
+--=-1xMN/UKcAW4fqZhcLB9V
+Content-Type: text/plain; charset="UTF-8"
+Content-Transfer-Encoding: quoted-printable
+
+
+On Tue, 2020-03-31 at 11:42 +0000, lkcl . wrote:
+> *click* what the hell am i saying?? jean-paul, we've got a clear need
+> for improvements to coriolis2, it is *really* easy to justify putting
+> in an application for NLNet funding, here.
+
+Hello Luke,
+
+This is a complicated matter. As a team of one, I have limited resources,
+so I must prioritize (and I know myself, I'm not very good at that).
+Anyway, the short term goal is to have the 180nm circuit done and
+working by October. In order to do that I/we must not "finish"
+Coriolis, but put it to a point it can fulfil that objective.
+I'm convinced it is doable, but we should go straight to the point,
+because I'm sure that lots of unexpected issues will pop-up and
+I will have to tackle them quickly.
+
+My "development cycle" are alternate steps of "adding features" then
+"improve code at constant features".
+
+So, having more hands will really be a plus (as you already proposed in
+an early mail). The problem is to have someone(s) with that triple skills
+(ASIC, algorithmic, software) and it has been proven difficult on my
+end. To have an example of the kind of code I get, you could take a
+look to the whole capacitor stuff in coriolis/oroshi/python/
+(and you will easily see where I modified the code with my unique
+ coding style). This was made by a good electrical engineer, but
+with embryonic software knowledge. The code is to draw the layout
+of one or a matrix of analog capacitors. The comments are made for
+doxygen.
+
+And besides, all of our students have already chosen their internship
+(in the industry). I think we may have a good one in June.
+And lastly, due to the Covid-19 and University shutdown we cannot
+hire anybody, should we have a candidate.
+
+I absolutely do not want to give you the impression that I do not
+want more people working on Coriolis, quite the contrary.
+But I want to expose the context as rightfully as it is.
+The question being how to circumvent those initial conditions
+to get more efficient people working on Coriolis?
+
+I've taken a look at GNUstep, it seems a bit quite by there...
+(maybe I was on the wrong site). For the record, WidowMaker is
+one of the more memory efficient window manager I have ever seen
+(still can work on my UltraSparc 1 / NetBSD).
+
+However I will remove Boost as soon as possible, it has proven to
+be a pebble in my shoes for too long. And migrating towards Python3.
+
+I'm currently making my Python code a bit more PEP8 compliant then
+backporting some of the work of Jock in soclayout. *But* I will keep
+some style that you may find bad. Paradox is that the "comma" at the
+start of line was showed to me by an early Python adopter back around
+2000...
+
+
+Best regards,
+--=20
+
+ .-. J e a n - P a u l C h a p u t / Administrateur Systeme
+ /v\ Jean-Paul.Chaput@lip6.fr
+ /(___)\ work: (33) 01.44.27.53.99 =20
+ ^^ ^^ cell: 06.66.25.35.55 home: 09.65.29.83.38
+
+ U P M C Universite Pierre & Marie Curie
+ L I P 6 Laboratoire d'Informatique de Paris VI
+ S o C System On Chip
+
+--=-1xMN/UKcAW4fqZhcLB9V--
+
+
+
+--===============9156565726221374067==
+Content-Type: text/plain; charset="utf-8"
+MIME-Version: 1.0
+Content-Transfer-Encoding: base64
+Content-Disposition: inline
+
+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KbGlicmUtcmlz
+Y3YtZGV2IG1haWxpbmcgbGlzdApsaWJyZS1yaXNjdi1kZXZAbGlzdHMubGlicmUtcmlzY3Yub3Jn
+Cmh0dHA6Ly9saXN0cy5saWJyZS1yaXNjdi5vcmcvbWFpbG1hbi9saXN0aW5mby9saWJyZS1yaXNj
+di1kZXYK
+
+--===============9156565726221374067==--
+
+
+