Ivan Jozsef Balazs

"I was studying Humanistics: History, Hungarian,"

The three great H's !
Nice és üdvözlet!

You might want to look up records:
https://dzone.com/articles/a-first-look-at-records-in-java-14

The genuine path separator in Windows is \ as opposed to / which might or might not work.

Remember to write is as "\\" inside a string literal signs.

Campbell Ritchie wrote:I thought all encryption would be broken by any quantum computations.

Well, maybe not forcibly *all* encryption would be broken by *any* quantum computation.

This is very fishy:
   Public Void setAgeint inAge;    {        // Set the age instance variable to the parameter        this.age = inAge;    }


Try something like this instead: - also note the capitalization (or the lack thereof):
   public void setAge(int inAge)    {        // Set the age instance variable to the parameter        this.age = inAge;    }

"equals" is inherited from Object. The other methods of Comparator are static or default.  

java.util Interface Comparator<T>

Functional Interface:
This is a functional interface and can therefore be used as the assignment target for a lambda expression or method reference.

Mike London wrote:
                 String utfString = new String(stringToConvert.getBytes("UTF-8")) ;

You have the string stringToConvert, encode it into a sequence of bytes using the UTF-8 encoding, then create a string from this sequence assuming it is a sequence of bytes using the platform's default charset. Don't we smell some fish around here?

Tim Holloway wrote:__FILE__ and __LINE__

Nobody prevents us from running Java (pre-) code through a C(++) precompiler :-)

The try-with-resources construct is useful for resource management.

By the way constructors and destructors are useful, even though you could argue against them saying "there are design principles for proper initialization and deinitialization".

/dev/random Wikipedia

Tim Holloway wrote:
And Linux tries to support NTFS, despite the fact that Microsoft hasn't always been transparent about how it works.

I saw on some Microsoft programming forums discussions on NTFS which were based on the Linux NTFS driver: it happened to be the available source for information.

Tim Holloway wrote: Unix/linux are always sensitive to upper/lower case in filenames.

I heard Linux supporting file systems like VFAT...

Campbell Ritchie wrote:But what is going to happen if you return null and try to use it? If you do more than simply print it out, you are risking an Exception.

Well, if you return something only seemingly useful, then you risk using that non-sensical value and this might be even worse than having an indication that something went wrong via the NPException.

If you search for something then in some way or other you have to cope with the case when it is not found: let it be through examinig for null, for a nonsensical sentintel value, a return code, whatnot.

Tim Holloway wrote:
That wasn't a CDC, was it?

It was a Bull DPSx where x=8 or so... It was int, long, maybe even long long ago :-)
I programmed it in Fortran and I accidentally came across the bytes' bit width: it did not really matter on this level.