The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

    Mastodon

  • Twitter Updates

  • My Flickr Stream

    20140508-Delphi-2007--Project-Options--Cannot-Edit-Application-Title-HelpFile-Icon-Theming20140430-Fiddler-Filter-Actions-Button-Run-Filterset-now20140424-VMware-Fusion-6.0.3.-no-reclaimable
    More Photos

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 2,947 other followers

Archive for November 15th, 2017

Happy 60th birthday, Fortran

Posted by jpluimers on 2017/11/15

I remember a FORTRAN IV (or was it 66?) course during my chemistry studies at the end of the 1980s. Luckily, the VAX/VMS version (not sure which one, it ran on a VAX 11/750) where we had to program on came with an extended FORTRAN 77 compiler even supporting 132 columns and other nice features.

My favourite program was about an algorithm to assemble 3 tables (one relating atom numbers and their valencies, a second with atom-atom distances, a third with 3-D atom positions) into a chemical compound indicating any rings. I implemented my own recursion with stacks citing a Dire Straits song with “and when you finally reappear, at the place where you came in…”.

Later I ported this to a PC reviewing the Microsoft FORTRAN 5.1 compiler for the Dutch PCM (Personal Computer Magazine). Recently I learned Lahey had a big role in the Fortran.NET compiler.

This year FORTRAN turned 60 years old and it is still in used, though not as heavily as a few decades ago.

The Fortran compiler, introduced in April 1957, was the first optimizing compiler, and it paved the way for many technical computing applications over the years. What Cobol did for business computing, Fortran did for scientific computing. Fortran may be approaching retirement age, but that doesn’t mean it’s about to stop working. This year marks the 60th anniversary of the first Fortran (then styled “FORTRAN,” for “FORmula TRANslation”) release.

Source: [WayBack] Happy 60th birthday, Fortran.

Via [Archive.is] Happy 60th birthday, Fortran – ThisIsWhyICode – Google+

Historic references:

–jeroen

Read the rest of this entry »

Posted in Development, Fortran, Software Development | 1 Comment »

FastMM4 + Delphi – Recompiling application with 10.2.1 causes memory leaks?

Posted by jpluimers on 2017/11/15

This is why you should always test your Delphi apps with FastMM4 and FullDebugMode enabled: [WayBack] Delphi – Recompiling application with 10.2.1 causes memory leaks?

A workaround is to add the below code in either of these places:

  • end of your .dpr file right before the end.
  • in the finalization section of a new unit

CheckSynchronize();

It calls the [WayBack] System.Classes.CheckSynchronize method to ensure the background thread performs the needed cleanup.

Thanks Stefan Glienke for solving this.

–jeroen

Read the rest of this entry »

Posted in Delphi, Delphi 10.2 Tokyo (Godzilla), Development, Software Development | Leave a Comment »

immediate “Too many authentication failures” – check your authentication methods

Posted by jpluimers on 2017/11/15

If you ever ssh into something and immediately get the immediate Too many authentication failures message, then you’ve probably mixed your authentication methods.

Follow the steps in [WayBack] ssh – Too many authentication failures for username – Super User (thanks [WayBack] John T and [WayBack] Ben West).

First check out whats wrong by slowly increasing the number of -v parameters to make output more verbose:

ssh -v
ssh -v -v
ssh -v -v -v

Then try to find out which authentication method fails: usually it’s a private key that’s wrong.

I’ve had success in various cases where I screwed up with these ssh parameters:

-o PubkeyAuthentication=no
-i some_id_rsa -o IdentitiesOnly=yes

–jeroen

 

Posted in *nix, Communications Development, Development, Internet protocol suite, Power User, Software Development, SSH, TCP | Leave a Comment »

Changing a commit message – User Documentation

Posted by jpluimers on 2017/11/15

When you haven’t pushed yet, git rebase --interactive HEAD~# where # is the number of commits to view is your friend: [WayBack] Changing a commit message – User Documentation.

At the first screen, replace aa with reword then change the commit message for each commit and copy the message.

Then in each following screen, if you changed the commit message for that commit, change it there as well.

Similar answers are at [WayBack] git – How to modify existing, unpushed commits? – Stack Overflow

–jeroen

Posted in Development, DVCS - Distributed Version Control, git, Source Code Management | Leave a Comment »

 
%d bloggers like this: