• (nodebb)

    At least the folks writing bugs using Utils.Utils.Whatever can have their bugs fixed in one place. The "fun" ones are when folks copypasta the functions out of Utils.Utils into their own app's Utils class while using the Using directive to mask which Utils is being ... Utilized. ;)

  • Jason Stringify (unregistered)

    on *its own

  • Sebastian E (unregistered)

    Only thing I could imagine where this would be (at least a little) reasonable:

    Porting very old code from old language to .net, and the old language did not have such a nice function (and others) as .net. Old code used "Utils.Utils". Instead of changing occurence everywhere, you just change your "Utils.Utils". And whenever you have new code, someone uses the direct way...

    Still WTF.

  • Loren Pechtel (unregistered)

    Two things come to mind:

    1. Occasionally one refers to something often enough that creating a shorter form of it makes the code more readable.

    2. More like, Sebastion is right and this is a port.

  • Twan (unregistered)

    That happens if your programming language doesn’t provide a convenient way to abbreviate overly long references or the programmer doesn’t know how to use it. I guess the latter one

Leave a comment on “The Utils”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article