Re: converting a 700,000+ line Fortran 77 plus 50,000+ line C++ program to C++, part 2

Lynn McGuire <lynnmcguire5@gmail.com> schrieb:

On 4/10/2025 2:52 PM, Lawrence D'Oliveiro wrote:

On Thu, 10 Apr 2025 14:39:02 -0500, Lynn McGuire wrote:
 

On 4/9/2025 7:35 PM, Lawrence D'Oliveiro wrote:
>

This is why you have build systems.

>
I started using the first IDE (interactive development environment) in
1983 ??? with Turbo Pascal.  $49 IIRC.  It was a simply amazing way of
doing things.  Nowadays, Visual Studio comes closest to the Turbo Pascal
IDE but even it is not quite there.  Visual Studios lack of a decent
Fortran compiler sucks.

 
IDEs tend to be limited in their build systems. They’re not flexible: they
insist you build things their way.
 

I moved back to build systems on the Apollo Domain in 1989 using DSEE
but it was a downer compared to Turbo Pascal.  It did allow multiple
user development teams to work together though.  We only had a few
hallway fights on code conflicts, most were resolved by DSEE.

 
Back in the day, we called them “CASE tools”, and they cost €€€. Nowadays,
they are just “developer tools”, and they are part of the standard package
repositories.
 
The one thing Git does better than any other VCS is merging branches. No
more hallway fights ...

>
One of my items on my long term plan is to move from CVSNT to Git.

I find git very unpleasant to work with.  Merge conflicts are
handled quite ungracefully, but my main problem is that I have
no mental model of what is happening with which command (which
means that I remove my local copies of the repos from time to time).

The conversion from svn to git of gcc was a _huge_ project, and
extremely difficult (took > man-year).