• (nodebb)

    Looks to me like a long forgotten backdoor; someone abused the production environment for testing. Obviously there could be a lot less legal reasons to for this code to exist, or it had not real purpose at all.

    Who knows.

    If it doesn't serve a purpose delete it. If someone is complaining there might be a better solution around the corner or in a worst case scenario just rollback the commit. First rule is always to keep technical debt in check or an application ends up like that: Wanted dead by everyone.

  • (nodebb)

    The correct name would be WtF7q2.

  • TheCPUWizard (unregistered)

    Clearly it is a helper to extract a query string value from a Uri... and query strings are often obfuscated in an attempt as security (by obscurity) so nothing to see here...move along...

  • Scragar (unregistered)

    Seen similar magic names used for features we didn't want regular people using, but IT would occasionally use for internal applications(think clearing caches, forcing debug info to be displayed, or controlling logging level per request). Very little reason to name the variable so weirdly though, normally it'd be called something like "debugState" or similar internally.

  • Registered (unregistered)

    Clearly, this stands for The First Seven Weeks of Quarter Two.

  • (nodebb) in reply to Registered

    ITYM The Frist Seven Weeks

  • (nodebb)

    Shakespeare was wrong. A rose by any other name.... Names are hard.

  • Noadle (unregistered)

    Reminds me of the names of functions from NAG or LINPACK. It's been nearly 30 years since I saw them in use, so I don't know what it could be if it was.

  • (nodebb)

    Reminds me of a ... web bureau (?) I once worked at, where we were designing the Stockholm OS bid site. Ahead of the final verdict, we prepared two pages with statements on the verdict. yes.html and no.html. Guess if journalists had fun with that one :D

    /E

  • Appalled (unregistered)

    Just search the code base and change all CODE references from"TF7Q2" to "OBS??". If nothing breaks and you feel like it, go back in a month and remove all the code and delete the row from the database.

  • (nodebb) in reply to Noadle

    From back when linkers only paid attention to the first 5 or 6 characters of a function name, and library authors tended to try to leave most of the "good" space of names to customer code.

  • Vilx- (unregistered)

    My guess:

    "t" = "text" (Hungarian notation) "F7" = "Form 7" "q2" = "Question 2"

    Also, how TF do you log on in these comments? Neither the "Forum Account" nor the "Google" options work.

  • someone (unregistered)

    My theory: There was an Excel File and in the cell F7 and Q2 is the description of this method.

  • Sauron (unregistered)

    I suppose tF7q2() is just the function after tF7q1() and before tF7q3() ...

  • TroyR (unregistered)
    Comment held for moderation.
  • (nodebb)

    Reminds me of the names of functions from NAG or LINPACK. It's been nearly 30 years since I saw them in use, so I don't know what it could be if it was.

    https://www.netlib.org/linpack/

    I think all functions have 5-letter names, no numbers.

  • (nodebb) in reply to Scragar

    Very little reason to name the variable so weirdly though

    It's not a variable. The assignment at the end is Visual Basic's way of setting a return value for the function of the same name.

Leave a comment on “Article tF7q2”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article