Jump to content

Sherlock

Moderators
  • Content Count

    1301
  • Joined

  • Last visited

  • Days Won

    28

Everything posted by Sherlock

  1. Sherlock

    Rounding issue

    And for this reason floating point numbers should not be checked for equality without an 𝛆. So in (our) Delphi world: https://docwiki.embarcadero.com/RADStudio/Alexandria/en/Floating-Point_Comparison_Routines
  2. Sherlock

    Delphi job req I just got

    That is actually not as horrible as you might think. In fact the exact opposite, once you work with more than two folks on a project AND need to save time on discussions about who changed what and why. On a side note: ISO 9001 is a joke, try ISO 13485 and IEC 62304 for a less fun time.
  3. Sherlock

    Splitting up quotes doesn't work anymore

    Perhaps @Daniel has a solution?
  4. Sherlock

    Splitting up quotes doesn't work anymore

    Quoting is indeed rather tedious. But a workaround for this might be the possibility to write an answer and select blocks from the original post and then click quote selection. Works pretty good, and will give you the result you wanted, without all the Copypasta.
  5. Sherlock

    [Delphi] Looking for a Delphi Profiler in 2023

    Well, this thread is from 2020, but it still might give you some pointers:
  6. And that is what the WSUS is for.
  7. Sherlock

    Trap TFDConnection error on data module create etc?

    Is there no "DesignConnection" property? I recall using DOA components from AllroundAutomation 20 years ago that had this nifty feature.
  8. At least you don't have to throw out a 6k$ scanner/printer because it can only scan to folders via SMB1. And it is not just someone that deems SMB1 insecure, it is the majority of users.
  9. To be fair, Microsoft has declared SMBV1 deprecated as early as 2014 And recent installations of Wins 10 and 11 have SMBV1 deactivated by default. Finally killing it now altogether seems logic and overdue. And if you ask Ned Pyle (Microsofts guy in charge of this) you should have gotten rid of it years ago: https://techcommunity.microsoft.com/t5/storage-at-microsoft/stop-using-smb1/ba-p/425858 https://learn.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/smbv1-not-installed-by-default-in-windows
  10. So...I'm guessing the person you are looking for needs to speak french?
  11. Or Jira and Zephyr Scale.
  12. Sherlock

    Replacement for TBits?

    @Rollo62Consider the amount of data processed at CERN according to https://home.web.cern.ch/science/computing they process more than 30PB a year. Another example may come from Astrophysics' EHT with enormous data https://eventhorizontelescope.org/technology gathered simultaneously all over the world and then correlated in Bonn and at MIT. Off the top of my head just two examples with really high volume data. I learned not to question the why...the who might be interesting though, if the OP may reveal it. In the end 300 Billion Bits are a mere 37,5 Gigabytes, BTW.
  13. Sherlock

    iOS 17

    Just out of curiosity: What kind of software are you developing and what kind of customers do you have, that causes them to check if your software runs on a more or less early beta of iOS? Most customers I know of, don't care about the installed iOS version and aren't even aware of impending new ones.
  14. Considering most of the installers known to me don't care about this particular issue, I would weigh cost against benefit and end up letting it go. But then again, I'm not nearly as ambitious as I used to be 10 years ago.
  15. Sherlock

    System.Net.Sockets

    It does support POSIX and macOS, so perhaps iOS as well. I am afraid Android is not officially supported though. So perhaps for mobile devices you could go Indy.
  16. Sherlock

    iOS 17

    Well, usually a new iOS version strangely precedes a new Delphi release. I would not count on anything other than the beta of said release to maybe fix that issue beforehand.
  17. Sherlock

    System.Net.Sockets

    On the other hand, it is a rather low level component and implementing asynchronous communication involves a lot of ground work. May I suggest moving on to the more powerful components like the Indy or the ICS components. And from the sound of it I think you might want to go with the ICS.
  18. Sherlock

    System.Net.Sockets

    Hi 😉 So over here I found one thread concerning System.Net.Socket. Sadly there is no use of AsyncCallback in there: But it looks pretty straight forward to me: implement either callback event handler or method and use that as a parameter for BeginReceive. What is your code so far, and where do you get errors/are you stuck?
  19. I wonder what Embarcadero would call a procedure with a return type... Has anyone created a ticket yet?
  20. It's a shame this thread slipped into a gender debate unnoticed. Sorry about that. BTT: https://meta.stackexchange.com/questions/390106/moderation-strike-update-data-dumps-choosing-representatives-gpt-data-and-wh
  21. Sherlock

    Trouble with testing dates

    As the title says, I'm having trouble with running a unit test to test dates. So here is my test: [TestFixture] TMyTestClass = class public [Test] // Test with TestCase Attribute to supply parameters. [Test] [TestCase('Test Thu-Sat', '2023-06-22 17:44:23.456, 2023-06-24 17:44:23.456, 0')] [TestCase('Test Thu-Sun', '2023-06-22 17:44:23.456, 2023-06-25 17:44:23.456, 1')] procedure Test(const AValue1: TDateTime; const AValue2: TDateTime; const AExp: Integer); end; procedure TMyTestClass.Test(const AValue1, AValue2: TDateTime; const AExp: Integer); begin Assert.IsTrue(Unit34.CheckForDates(AValue1, AValue2) = AExp); end; Now when I run this it alwas behaves as though the dates are not translated correctly. And sure enough the debugger says both AValues are 1899. When I run DUnitXs own Test - specifically the DUnitX.Tests.Example.pas the date there gets translated just fine. And the keen eye might notice the same time in my code as in DUnitXs...I copied and only changed the date. What am I doing wrong?
  22. Sherlock

    Trouble with testing dates

    Not to be "that guy" but, um... it would seem my initial dates where indeed ISO 8601 formatted. So my guess now is that the DUnitX used in D11.3 is more than two years old?
  23. Sherlock

    Trouble with testing dates

    OK, so it's a locale settings issue. Apparently the DUnitX tests do something to the date format, that catch this. As soon as I use my native german date format, it works. Hrmpf [TestCase('Test Do-Sa', '22.06.2023 17:44:23.456, 24.06.2023 17:44:23.456, 0')] And @Der schöne Günther I will do just that then. Thank you!
×