Efficacy of on-line code generation

[woodb...@gmail.com]

If anyone would like a demonstration of on-line code
generation, I'm happy to make that happen. It usually
takes less than 10 minutes if you have a compiler with
C++ 2017 support. The first step is to clone/download
the software here:
https://github.com/Ebenezer-group/onwards
.

I also have an offer to help someone who is willing
to use my software. I'll spend 16 hours a week for
six months on your project if we use my software as
part of the project. There are more details here:
http://webEbenezer.net/about.html


Brian
Ebenezer Enterprises - Enjoying programming again.
http://webEbenezer.net

[Tim Rentsch]

woodb...@gmail.com writes:

> If anyone would like a demonstration of on-line code
> generation, I'm happy to make that happen. It usually
> takes less than 10 minutes if you have a compiler with
> C++ 2017 support. The first step is to clone/download
> the software here:
> https://github.com/Ebenezer-group/onwards

I downloaded the software, but I don't have the means to
compile it, because (apparently) it depends on g++-7, which
is not present on my most up-to-date system. I did some
searching with apt-cache to see if there was something I
could apt-get, but I didn't find anything. I confess I
spent very little time doing this, under 10 minutes, but
I thought you might appreciate the report.

[woodb...@gmail.com]

On Monday, April 2, 2018 at 11:02:46 AM UTC-5, Tim Rentsch wrote:

> I downloaded the software, but I don't have the means to
> compile it, because (apparently) it depends on g++-7, which
> is not present on my most up-to-date system.

You can substitute your compiler in the makefile. But it
has to have support for 2017 ++C. It should work with
clang 5 or 6 and newer versions of MSVC.

> I did some
> searching with apt-cache to see if there was something I
> could apt-get, but I didn't find anything. I confess I
> spent very little time doing this, under 10 minutes, but
> I thought you might appreciate the report.

Thank you. The requirement of a 2017 ++C compile is just
for building the software in the repo. The output from the
on-line code generator only requires a 2011 ++C compile.
I hope this helps.


Brian

[Tim Rentsch]

woodb...@gmail.com writes:

> On Monday, April 2, 2018 at 11:02:46 AM UTC-5, Tim Rentsch wrote:
>
>> I downloaded the software, but I don't have the means to
>> compile it, because (apparently) it depends on g++-7, which
>> is not present on my most up-to-date system.
>
> You can substitute your compiler in the makefile. But it
> has to have support for 2017 ++C. It should work with
> clang 5 or 6 and newer versions of MSVC.

I already had tried a different version of g++, which didn't
work. After getting your message I tried clang 5, which was
better, but then there was a problem of a missing header file
(that was <string_view>). There was some sort of experimental
version of <string_view> under /usr/include, and I arranged
to get that with a -I, but that led to some other errors at
which I point I basically gave up. Sorry but that's the
best I can do for you at present.

>> I did some
>> searching with apt-cache to see if there was something I
>> could apt-get, but I didn't find anything. I confess I
>> spent very little time doing this, under 10 minutes, but
>> I thought you might appreciate the report.
>
> Thank you. The requirement of a 2017 ++C compile is just
> for building the software in the repo. The output from the
> on-line code generator only requires a 2011 ++C compile.
> I hope this helps.

I'm not faulting your choices. For me it's important to go
through a complete build, because it helps to see what I'm
dealing with. I think at present what you have done is
just a bit too close to the cutting edge for my environment.
Sometime in the future maybe things will change enough so
I can think about giving it another try.

[woodb...@gmail.com]

On Thursday, April 5, 2018 at 12:06:59 AM UTC-5, Tim Rentsch wrote:

> woodb...@gmail.com writes:
>
> >
> > You can substitute your compiler in the makefile. But it
> > has to have support for 2017 ++C. It should work with
> > clang 5 or 6 and newer versions of MSVC.
>
> I already had tried a different version of g++, which didn't
> work. After getting your message I tried clang 5, which was
> better, but then there was a problem of a missing header file
> (that was <string_view>). There was some sort of experimental
> version of <string_view> under /usr/include, and I arranged
> to get that with a -I, but that led to some other errors at
> which I point I basically gave up. Sorry but that's the
> best I can do for you at present.
>

This sounds similar to a problem Ian had:
https://groups.google.com/forum/#!topic/comp.lang.c++/Ym2SzLgobFA

. It turned out to be a clang problem.


Brian
Ebenezer Enterprises
http://webEbenezer.net