• LongTimeLurker (unregistered)

    this.TraceOutput(string.Concat("\n\n\n", "Frist", "\n\n\n"));

  • (nodebb)

    I cannot help but admire the vast amount of code in the last method --- devoted to looping through a string which is guaranteed to be exactly one character. Bravo!

  • (nodebb)

    Microsoft's inclusion of Convert.ToX was a horrible mistake. It caused a massive amount of developers to use them, unaware of the better X.TryParse methods.

  • Ben (unregistered)

    Looks like that mail variable is a global too, so once it is set it will always be set

  • (nodebb)

    ´´´this.´´´

    This is pretty much always a dead giveaway that code was written by a Java dev.

    Addendum 2025-03-06 09:52: And obviously the complete lack of understanding of the Dispose pattern makes it pretty likely that we are no talking about a c/C++ dev here, because it's a bread and butter COM pattern.

  • TheCPUWizard (unregistered)
    Comment held for moderation.
  • Rob (unregistered)
    Comment held for moderation.
  • (nodebb)

    @colejohnson66** ref

    Microsoft's inclusion of Convert.ToX was a horrible mistake. It caused a massive amount of developers to use them, unaware of the better X.TryParse methods.

    The Convert.ToX methods were in .Net from the original Framework 1.0. The Tryparse methods were a later addition, Framework 2.1 IIRC. MS would have needed a time machine to do it the other way.

    But yes, once the TryParse. methods exist, there begins to be an argument for deprecating the Convert methods. Without delving into the source code details to assess performance, it may well be that the Convert methods are significantly faster for the happy path. Which would be reason enough not to deprecate them.

Leave a comment on “An Argument With QA”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article