Forum

Thank you, Rosivaldo!

Hi Larry, Maybe you can take a look at https://gcc.gnu.org/onlinedocs/gcc-10.2.0/gcc/Invoking-G_002b_002b.html#Invoking-G_002b_002b. It's a short description on the difference of gcc and g++ for compiling C++ code. Best regards, Rosivaldo. Em 03/08/2020 09:35, Larry Rix escreveu: >

Hi Louis! Can I use the "inline" as-is with C++ calls? I suppose I could try to look that up on the Eiffel support site, but you might be able to answer better and faster. Thank you! Larry

Thanks, Ulrich. I will give it a look. On Monday, August 3, 2020 at 1:50:09 AM UTC-4 Ulrich W. wrote: > >>> Larry Rix schrieb am 31.07.2020 um > 14:32 in > Nachricht <35501688-0d6c-4528...@googlegroups.com>: > > I am now getting comfy with gcc, but the Freenove

Excellent feedback, Louis! Thank you! On Sunday, August 2, 2020 at 10:46:49 AM UTC-4 eif...@tioui.com wrote: > Hi Larry, > > With the "signature" version, you specify the C type in the external > section while in the inline version, you have to specify everything in the > "alias" section.

Nachricht <35501688-0d6c-4528-a374-f361cbed1d67n@googlegroups.com>: > I am now getting comfy with gcc, but the Freenove sample code has C++ code > that it wants to me to compile with g++ rather than gcc. > > QUESTION: If I put a C++ external wrapper into my Eiffel code, is the > Eiffel

Hi Larry, With the "signature" version, you specify the C type in the external section while in the inline version, you have to specify everything in the "alias" section. "inline" is more powerful than "signature" and everything that can be done with the "signature" version can be translated

Actually for me it would be that simple, a compilation of my project on a rpi takes 58 minutes.... on a computer it would take so much less time.... On Sat, Aug 1, 2020 at 6:28 PM 'Louis M' via Eiffel Users < eiffel...@googlegroups.com> wrote: > Yes! > > Louis M > On 2020-07-28 6:56 a.m., Larry

Hey Louis! Isn't the "signature" the indicator to the compiler of an external call to external code, whereas "inline" indicates the C/C++ code is fully contained in the feature body? Kindest regards, Larry On Sunday, August 2, 2020 at 1:22:50 AM UTC-4 eif...@tioui.com wrote: > On 2020-08-01

That is OK. Then: "C++ signature ..." instead of: "C signature ..." Unless I am mistaken, both are valid and present (not obsolete) Eiffel syntax (see: https://www.eiffel.org/doc/solutions/Interfacing_with_C_and_C%2B%2B ). Good day, Louis M

BTW—I do realize that my use of "alias" is redundant because my Eiffel feature name is precisely the same (case insensitive) as the C feature name, which negates the need for the "alias" clause. I do this only for a future case where I might decide to do a rename of the feature into something

So far, my C externals have looked like this: On Saturday, August 1, 2020 at 6:34:51 PM UTC-4 eif...@tioui.com wrote: > I do not know if it is important, but when you use C++ instead of C in > external, I have to use: > > "C++ inline" > > instead of: > > "C inline" > > Like this: > > frozen

Or Gitlab. It does not belong to Microsoft and is open source. Louis M

I do not know if it is important, but when you use C++ instead of C in external, I have to use: "C++ inline" instead of: "C inline" Like this: frozen ObjectA_new:POINTER -- C initialisation of a ObjectA external "C++ inline use " alias

Yes! Louis M On 2020-07-28 6:56 a.m., Larry Rix wrote: Oh, I see! I think I was missing some information in your first message. It is now clear that by cross-compiler, you mean that you have a compiler that runs on my PC (Intel CPU), but compiles for ARM7/8? Therefore, I can do quicker compiles