Smalltalk taught me a very valuable lesson and is the reason why I hate all dynamic typed languages.
On Jan 11, 2020, at 7:30 AM, Larry Rix <lar...@moonshotsoftware.com> wrote:
--
You received this message because you are subscribed to the Google Groups "Eiffel Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eiffel-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/eiffel-users/15eab46c-f4ba-40fe-82d9-0f4e93744c2c%40googlegroups.com.
Hello, in my quest to pick correct language for the open-source GUI project have eliminated some more languages from my list and while waiting for installation issue to be resolved, I'd like to get some input on the following issue: introductory docs very often compare Eiffel with C++ and Smalltalk. I did eliminate C++ from my equation long ago and would like to get some inputin regard to Eiffel vs Smaltalk... Here I'm thinking about Pharo and some of its aspects provide clear advantages over Eiffel like size & activity of the community, clear roadmap of the project, licensing etc. On the other hand Eiffel does support usage of convenient tools like editor (e.g. Vim in my case), VCS tool (Fossil), file-based projects vs image-based in Pharo. However, there are many unknown things to me, about which I'd like to get more info to make it easier to finally decide... So, can anyone shed some more light about Eiffel vs Pharo (Smalltlak) as adequate language to be used for hobby project? Sincerely, Saša
-- SmartDevelopersUseUnderScoresInTheirIdentifiersBecause_it_is_much_easier_to_read
Saša
--
--
You received this message because you are subscribed to the Google Groups "Eiffel Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eiffel-users+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/eiffel-users/20200112085915.6b29a1fe%40atmarama.ddns.net.
Looks like wxWidgets is a very current and lively project. @ https://github.com/wxWidgets/wxWidgets
Javier or Jocelyn, please help me to clarify if WrapC can do C++ or is it just C?
On Mon, 13 Jan 2020 07:40:49 -0500
Larry Rix <lar...@moonshotsoftware.com> wrote:
> I stand corrected! Only C and not C++. That's too bad!
For my project binding C is enough and welcome to have some tool to autoamte
process a bit.
> But—on the bright side, it is far better than nothing at all!
Yes. Moreover wxEiffel seems to be made without any tool, but any tool to help
with the C++ bindings would be nice to have...
On Mon, 13 Jan 2020 07:31:14 -0800 (PST) javier hector
<javier...@gmail.com> wrote:
Hello Javier,
> If you can share the list of C libraries that you want to wrap, I can
> help you get started with them,
Here is the lib I want to use:
https://www.astro.com/swisseph/swephprg.htm
On Tue, 14 Jan 2020 04:32:21 -0800 (PST)
javier hector <javier...@gmail.com> wrote:
> > > If you can share the list of C libraries that you want to wrap, I
> > > can help you get started with them,
> >
> > Here is the lib I want to use:
> >
> > https://www.astro.com/swisseph/swephprg.htm
>
> Ok I will take a look.
In order to get real feeling (still have to digest Larry's elaborate answer)
for the language & (Eiffel) method, I'd like to check how easy/difficult is to
wrap 3rd party C library which I'd need for my project.
Moreover, I'm interested whether WrapC tool can help providing thicker bindings
which are more in Eiffel's spirit instead of plain thin wrapper over C API?
Lastly, I'm curious what does happen with Eiffel's "void safety" when dealing
with C libs and what about GC?