• (cs) in reply to Martin
    Martin:
    I have always thought that this "Lets us read userinput, and see if we in some wierd way can handle the input as a date" is a big wtf.
    So you admit that you're completely inappropriate to be a member of the Microsoft Excel development team.
  • (cs)

    What disturbs me is the parameter name: "datas". Since "data" is already the plural of "datum", what is datas? Some kind of fourth dimensional measurement?

  • (cs)

    Come on guys... I suspect most of the syntax stuff re Ben's solution stems from annonymization (just guessing here, but Jake is not a Java programmer, so some inconsistencies might have crept in?)

  • anon (unregistered) in reply to vt_mruhlin
    vt_mruhlin:
    Those pres in there are part of the comments, and I'm not sure why they're in there.

    You've really never heard of javadocs?

    Alex, have you hired TopCod3r?

  • morry (unregistered)

    As a computer programmer, trained to write code, it pisses me off when EEs are writing code. I pull out resistors and start getting all stabby with them.

  • Anonymous (unregistered) in reply to Chris
    Chris:
    jethr0:
    TRWTF is the empty catch block in Ben's solution.

    not only that, but a try and catch without a finally.

    my boss goes completely nuts if he finds a try / catch without a finally.

    the result: I have an entire army of empty finally blocks. (he doesn't like that either, but it's far less likely to send him into a condescending mini-lecture about good coding standards)

    Wow, that really is... insane. How is an empty finally block an example of good coding practice? It is functionally useless, it increases the complexity (and filesize) of the code and reduces readability. I'm pretty sure our coding standards explicitly forbid such cruft. I'd sure like to read this guy's coding standards, sounds like a treasure trove of WTFs.

  • (cs) in reply to Code Dependent
    Code Dependent:
    What disturbs me is the parameter name: "datas". Since "data" is already the plural of "datum", what is datas? Some kind of fourth dimensional measurement?
    Not a native speaker. It jumped out at me, too, but I've seen it before. There are certain languages whose speakers tend to do English like that when they're almost fluent in it.
  • (cs) in reply to Code Dependent
    Code Dependent:
    What disturbs me is the parameter name: "datas". Since "data" is already the plural of "datum", what is datas? Some kind of fourth dimensional measurement?

    If you have a form that collects user data and a form that collects financial data, then you must be collecting datas.

  • Mizchief (unregistered) in reply to Cindy Dalfovo
    Cindy Dalfovo:
    What's with the programmers vs engineers? I'm an engineer and I like to use parsers and to use the simple solution. Then again, I'm just an engineer STUDENT, so maybe I still haven't learned how to do things the hard way...

    I actually have a B.S in Software Engineering. It pisses me off that now anyone that codes is called a "Software Engineer" when they have no training in engineering princepals. My job for the last few years is to take an organic developer-loved application and turn it into a engineered product by using methodical development processes and keeping track of the project using metrics.

    If your trying to build hardware than a EE degree is probably a good idea, but your wasting time if you want to build software, you would be better off with regular CS, Software Engineering, or Systems Engineering.

    I've thought about going back to school to get my masters in either Systems Engineering or Industrial Engineering have any of you WTFers' gone this route?

  • ShatteredArm (unregistered) in reply to ...
    ...:
    There's nothing wrong about not using a finally block when you don't have open resources to close or similar stuff (and that's the case, there's nothing to be done in a finally block there). If your boss doesn't understand what finally is meant to, but loves preaching about it, he's stupid.

    +1

    No reason to have a finally block if you're just parsing a string. I guess a good rule of thumb is, if your finally block is empty, your finally block is unnecessary.

  • Mizchief (unregistered) in reply to ShatteredArm
    ShatteredArm:
    ...:
    There's nothing wrong about not using a finally block when you don't have open resources to close or similar stuff (and that's the case, there's nothing to be done in a finally block there). If your boss doesn't understand what finally is meant to, but loves preaching about it, he's stupid.

    +1

    No reason to have a finally block if you're just parsing a string. I guess a good rule of thumb is, if your finally block is empty, your finally block is unnecessary.

    It drives me nuts to see someone use a try-catch to figure out if a string is formatted correctly before parsing.

    I can't remember how many times i've have to modify people's code from:

    try { DateTime parasedDate = DateTime.Parse(someString); } catch { return null; // Or Give some specific message }

    To:

    DateTime parsedDate; if(! DateTime.TryParse(someString, out parsedDate)) { return null; // Or Give some specific message }

    Try the TryParse. It's you efficent friend.

  • (cs) in reply to ShatteredArm

    I agree with some of the points in the discussion, but however, when it comes to parsing only in one locale, there might be a good reason for it. For example, if you have many devices deployed in the field, and they always generated english xml files, you can still use your english xml files while having an international friendly visual interface. I'm not saying I condone the no error checking, etc, but there is actually several cases I can think of to force parsing in one locale.

  • (cs) in reply to anon

    [quote user="anon"][quote user="PAG"]Computers run on electricity, so anyone who is an electrical engineer should understand how computers work.[/quote]

    Yah, they're called COMPUTER engineers. Not all electrical engineers work on computers. DOH!

  • Mizchief (unregistered) in reply to pitchingchris
    pitchingchris:
    I agree with some of the points in the discussion, but however, when it comes to parsing only in one locale, there might be a good reason for it. For example, if you have many devices deployed in the field, and they always generated english xml files, you can still use your english xml files while having an international friendly visual interface. I'm not saying I condone the no error checking, etc, but there is actually several cases I can think of to force parsing in one locale.

    I agree. I've run into some serious problems with not even local-specific but time zone specific data. The programmer before me on a project wanted to display some times relative to the client, so he took the time from the client vs. using the server's time or sticking to GMT for db storage.

    Which was fine untill people started to show up to events hours before or after they started, then there was no way to programatically figure out the correct timezone for events already in the system.

    Not to mention that the "Time" field in the DB was a nvarchar with values such as 3:00, 3pm, 3:00 PM, 12 noon, midnight, etc.

  • (cs) in reply to JamesQMurphy
    JamesQMurphy:
    JD:
    Professionals treat all warnings as errors. Amateurs ignore warnings. Idiots suppress warnings.
    Nice. That's going on my wall.
    Both of you are idiots. What if you are using Java 1.5 or higher, and for some reason you cannot use Generics for a data type. So you're an idiot for suppressing the warnings for this? lrn2Java nubs
  • TekniCal (unregistered) in reply to Mizchief
    Mizchief:
    princepals. ?

    WTF are 'princepals'?

  • JZ (unregistered) in reply to rumpelstiltskin

    Yes, and before toilet paper was invented, using grass was a typical way of wiping your ass.

  • (cs) in reply to amischiefr
    amischiefr:
    JamesQMurphy:
    JD:
    Professionals treat all warnings as errors. Amateurs ignore warnings. Idiots suppress warnings.
    Nice. That's going on my wall.
    Both of you are idiots. What if you are using Java 1.5 or higher, and for some reason you cannot use Generics for a data type. So you're an idiot for suppressing the warnings for this? lrn2Java nubs

    We were talking about the times where an (idiot) developer looks at a warning, doesn't know what it means, and then suppresses it away into the cornfield, then wonders why months later the code mysteriously fails.

    Duh.

  • (cs) in reply to Mizchief
    Mizchief:
    ShatteredArm:
    ...:
    There's nothing wrong about not using a finally block when you don't have open resources to close or similar stuff (and that's the case, there's nothing to be done in a finally block there). If your boss doesn't understand what finally is meant to, but loves preaching about it, he's stupid.

    +1

    No reason to have a finally block if you're just parsing a string. I guess a good rule of thumb is, if your finally block is empty, your finally block is unnecessary.

    It drives me nuts to see someone use a try-catch to figure out if a string is formatted correctly before parsing.

    I can't remember how many times i've have to modify people's code from:

    try { DateTime parasedDate = DateTime.Parse(someString); } catch { return null; // Or Give some specific message }

    To:

    DateTime parsedDate; if(! DateTime.TryParse(someString, out parsedDate)) { return null; // Or Give some specific message }

    Try the TryParse. It's you efficent friend.

    Try parsing the fact that this is Java, not C#.

    :)

  • addice (unregistered) in reply to Delve

    and social, and economic, and foreign policy relations, and etc etc etc etc <ad naseum>

  • diaphanein (unregistered) in reply to MindChild
    MindChild:
    I don't think this is necessarily a WTF at all. I think it is pretty apparent that this is likely a C++ programmer thrown into Java. If you have ever been in such a situation, you KNOW that you don't know all of the cool little language features... so you use what is good practice elsewhere. This is how you would break a loop in C/C++, without a goto. And it is clear what and why you are trying to do it.

    The WTF would be any self respecting C/C++ introducing an unnecessary local variable to avoid a valid use case for goto. goto is not evil, it can just be used to do evil things.

  • Not the real WTF (unregistered) in reply to Bappi
    Bappi:
    Code Dependent:
    What disturbs me is the parameter name: "datas". Since "data" is already the plural of "datum", what is datas? Some kind of fourth dimensional measurement?
    Not a native speaker. It jumped out at me, too, but I've seen it before. There are certain languages whose speakers tend to do English like that when they're almost fluent in it.
    Wrong and wrong. There are certain languages (namely spanish and portuguese, maybe some other latin languages too) where the translation of "date" is "data", its plural is "datas" and it has nothing to do with the english "data" that translates as "dados".

    The guy probably has some sort of latin background.

  • James (unregistered) in reply to operagost
    operagost:
    Jythie:
    Reminds me of all those anti-ivory-tower-elite types that america seems so proud of.. people with less education thinking that they MUST know more then people with more education because education is worthless.
    [citation needed]

    I offer as the citation the election results of 2004.

  • JD (unregistered) in reply to amischiefr
    amischiefr:
    JamesQMurphy:
    JD:
    Professionals treat all warnings as errors. Amateurs ignore warnings. Idiots suppress warnings.
    Nice. That's going on my wall.
    Both of you are idiots. What if you are using Java 1.5 or higher, and for some reason you cannot use Generics for a data type. So you're an idiot for suppressing the warnings for this? lrn2Java nubs
    Don't be a retard. There will always be a limited number of legitimate reasons to suppress certain warnings and these should be judged on a case by case basis. But suppressing a deprecation warning because your solution "works incredibly well" is completely idiotic and, for someone in my position, completely unacceptable. It is perfectly obvious that the developer suppressed this warning just to make it disappear, since that is easier than fixing it. I'm sorry, but professionals treat all warnings as errors. You may not fall into the category of "professional" but maybe one day...
  • Befuddled (unregistered) in reply to JavaJaap
    JavaJaap:
    TRWTF is the current Java date and time implementation. But of coarse all our problems will be solved by JSR-310 :)

    Hallelujah. In the mean time use JODA.

    And the given solution is shit.

    Some general points:

    1. Never return nulls, instead throw an exception (checked if you're able to tell the user what they did wrong, otherwise unchecked)
    2. No need to initialise date to null if you code to 1)
    3. Make the patterns configurable (use a defaulted system property if you have nothing else at your disposal)
    • Don't force the locale, just run the JVM in the right locale in the first place.
  • (cs) in reply to JD
    JD:
    I'm sorry, but professionals treat all warnings as errors.
    Repetition does not equal credibility. Do you have any justification for this statement or is it just some rhetorical platitude that you pulled out of your ass?

    There is a reason that warnings are warnings and not errors. You admit yourself that there are cases when warnings should legitimately be suppressed, and yet in the next breath you go back to your inane generalization that they should all be treated as errors (unless you're not "professional"). You sound like a middle manager somewhere enforcing a company policy.

  • (cs) in reply to Not the real WTF
    Not the real WTF:
    Bappi:
    Code Dependent:
    What disturbs me is the parameter name: "datas". Since "data" is already the plural of "datum", what is datas? Some kind of fourth dimensional measurement?
    Not a native speaker. It jumped out at me, too, but I've seen it before. There are certain languages whose speakers tend to do English like that when they're almost fluent in it.
    Wrong and wrong. There are certain languages (namely spanish and portuguese, maybe some other latin languages too) where the translation of "date" is "data", its plural is "datas" and it has nothing to do with the english "data" that translates as "dados".

    The guy probably has some sort of latin background.

    I hear 'informations' and 'advices' every day as plurals of 'information' and 'advice'... why not 'datas', or 'dices' for that matter? For someone who hasn't spoken English their whole life (and possibly learnt English from someone who doesn't know some of the finer details), 'datas' could very well make as much sense as 'bicycles'...

  • (cs) in reply to jethr0
    jethr0:
    TRWTF is the empty catch block in Ben's solution.

    Nothing wrong with that - if you're trying a bunch of formats (sort of dodgy to begin with), you expect a fair number of parse exceptions. If we're going to return the first hit, though, just return from the inner loop.

  • (cs) in reply to Aaron
    Aaron:
    JD:
    I'm sorry, but professionals treat all warnings as errors.
    Repetition does not equal credibility. Do you have any justification for this statement or is it just some rhetorical platitude that you pulled out of your ass?

    There is a reason that warnings are warnings and not errors. You admit yourself that there are cases when warnings should legitimately be suppressed, and yet in the next breath you go back to your inane generalization that they should all be treated as errors (unless you're not "professional"). You sound like a middle manager somewhere enforcing a company policy.

    Justification? Sure - warnings are usually errors, so treat them as such until proven otherwise. The fact that you can't deal with the concept of a rule of thumb and need in spelled out explicitly implies that you're sort of deficient on the soft side of things.

  • (cs)

    Honestly, sometimes this kind of problem is a documentation problem. It might be that DateFormat.parse() is well documented -- but someone wanting to create a Date is looking in the Date class. If the Date class documentation (especially the deprecated Date(string) constructor) contains a comment to look at DateFormat.parse(), and DateFormat.parse() contains suitable sample code, then chances are that this kind of code doesn't get written.

    Although in this case, the documentation actually does the right thing, so this particular WTF is still WTF-worthy :-)

  • (cs) in reply to Franz_Kafka
    Repetition does not equal credibility. Do you have any justification for this statement

    Just do a literature search. Most good literature books on how to write good software (including that classic, "Writing Solid Code") recommends to treat warnings as errors, and only when you can't write warning-free code (but you've convinced yourself that the warning is unavoidable) should you suppress it in that particular instance.

  • (cs) in reply to Why Too What?
    Why Too What?:
    Date This:
    I think there are some date formats missing in the original code... lots of them.

    Which reminds me, we need some special kind of torture for people who represent dates such as 07/08/09.

    I dunno, on my first job (at a COBOL shop) I saw a lot of 99/99/99 and that didn't seem to cause any problems. At the time.

    Ah, yes, the infamous Y2K/M2K/D2K problem (or Y2K/D2K/M2K as it was known in some parts of the world)

  • (cs) in reply to Mizchief
    Mizchief:
    ShatteredArm:
    ...:
    There's nothing wrong about not using a finally block when you don't have open resources to close or similar stuff (and that's the case, there's nothing to be done in a finally block there). If your boss doesn't understand what finally is meant to, but loves preaching about it, he's stupid.

    +1

    No reason to have a finally block if you're just parsing a string. I guess a good rule of thumb is, if your finally block is empty, your finally block is unnecessary.

    It drives me nuts to see someone use a try-catch to figure out if a string is formatted correctly before parsing.

    I can't remember how many times i've have to modify people's code from:

    try { DateTime parasedDate = DateTime.Parse(someString); } catch { return null; // Or Give some specific message }

    To:

    DateTime parsedDate; if(! DateTime.TryParse(someString, out parsedDate)) { return null; // Or Give some specific message }

    Try the TryParse. It's you efficent friend.

    TryParse did not exist in .NET 1.1 and earlier. I'd love to use TryParse but we still haven't upgraded here.

    Of course, TryParse basically just wraps your parse call in a try/catch, meaning you're still paying the exception cost, you just don't ever see it.

    --Benanov

  • diaphanein (unregistered) in reply to Benanov
    Benanov:
    Of course, TryParse basically just wraps your parse call in a try/catch, meaning you're still paying the exception cost, you just don't ever see it.

    --Benanov

    Actually, you're incorrect. TryParse does not wrap Parse in a try/catch block. The reverse is actually the case. DateTime.Parse wraps DateTime.TryParse with a check to see if the parse failed, throwing if the TryParse failed.

  • Art (unregistered) in reply to xalor

    I second that. As Einstein said, "Everything should be made as simple as possible, but not simpler."

  • (cs) in reply to operagost
    operagost:
    Jythie:
    Reminds me of all those anti-ivory-tower-elite types that america seems so proud of.. people with less education thinking that they MUST know more then people with more education because education is worthless.
    [citation needed]

    Have you never heard of SpectateSwamp?

  • ShatteredArm (unregistered) in reply to JD
    JD:
    amischiefr:
    JamesQMurphy:
    JD:
    Professionals treat all warnings as errors. Amateurs ignore warnings. Idiots suppress warnings.
    Nice. That's going on my wall.
    Both of you are idiots. What if you are using Java 1.5 or higher, and for some reason you cannot use Generics for a data type. So you're an idiot for suppressing the warnings for this? lrn2Java nubs
    Don't be a retard. There will always be a limited number of legitimate reasons to suppress certain warnings and these should be judged on a case by case basis. But suppressing a deprecation warning because your solution "works incredibly well" is completely idiotic and, for someone in my position, completely unacceptable. It is perfectly obvious that the developer suppressed this warning just to make it disappear, since that is easier than fixing it. I'm sorry, but professionals treat all warnings as errors. You may not fall into the category of "professional" but maybe one day...

    If you're doing some revenue-generating operation, why would you throw out the whole thing if you retrieved the information you want, but with a warning? Sorry, you're wrong, professionals don't treat all warnings as errors. They log all warnings, and then handle specific warnings on a case-by-case basis, depending on whether it's a show-stopping situation. And then they make a business decision on whether previously unencountered warning situations should break the entire operation, or if they too should simply be logged. Then, they monitor the logs, especially during the test and beta phases. That's what professionals do. They don't naively throw out any and every result because there was a non-critical warning.

  • Herohtar (unregistered) in reply to vt_mruhlin
    vt_mruhlin:
    Those pres in there are part of the comments, and I'm not sure why they're in there.

    You've really never heard of javadocs?

    Seriously. That's got to be TRWTF of today.

  • Percy the Pedant (unregistered) in reply to Mizchief
    Mizchief:
    I actually have a B.S in Software Engineering. It pisses me off that now anyone that codes is called a "Software Engineer" when they have no training in engineering princepals. My job for the last few years is to take an organic developer-loved application and turn it into a engineered product by using methodical development processes and keeping track of the project using metrics.

    If your trying to build hardware than a EE degree is probably a good idea, but your wasting time if you want to build software, you would be better off with regular CS, Software Engineering, or Systems Engineering.

    I've thought about going back to school to get my masters in either Systems Engineering or Industrial Engineering have any of you WTFers' gone this route?

    When you do, please sign up for a remedial English class. . . it's "principles", not "princepals", "you're", not "your" (it's a contraction of "you are", not a possessive), and "then", not "than".

    I know a couple of EEs and a chemist or two, as well, who can not only program but can actually compose a grammatically correct sentence.

    Sheesh.

  • Tom (unregistered)

    Give the kid a break. Why do you need to create a date format object every time the method is called? I guess your code has it's own WTF, but I have to say, I really appreciate the fact that you showed your fix. Most are afraid of doing that and I understand why - their code probably has ten times more WTFs than the original.

    Captcha: transverbero Aare we still posting captchas?

  • ML (unregistered) in reply to TekniCal
    TekniCal:
    Mizchief:
    princepals. ?

    WTF are 'princepals'?

    Friends of the son of a monarch. DUUUUUUUUH......

  • jonny five (unregistered) in reply to Not the real WTF
    Not the real WTF:
    Bappi:
    Code Dependent:
    What disturbs me is the parameter name: "datas". Since "data" is already the plural of "datum", what is datas? Some kind of fourth dimensional measurement?
    Not a native speaker. It jumped out at me, too, but I've seen it before. There are certain languages whose speakers tend to do English like that when they're almost fluent in it.
    Wrong and wrong. There are certain languages (namely spanish and portuguese, maybe some other latin languages too) where the translation of "date" is "data", its plural is "datas" and it has nothing to do with the english "data" that translates as "dados".

    The guy probably has some sort of latin background.

    no no no no. This is obviously a Star Trek: The Next Generation reference! Remember the time that Data tried to interface directly with the Enterprise computer systems and then Worf and Troi get stuck in the Holodeck and all the bad guys look like Data? (Oh come on, don't act like you don't. You know exactly what I'm talking about.) That episode was titled "A Fistful of Datas."

    Come on, I know I'm not the only one who had that episode pop into their head when they saw "datas." Right? ...right?

  • (cs) in reply to akatherder
    akatherder:
    Code Dependent:
    What disturbs me is the parameter name: "datas". Since "data" is already the plural of "datum", what is datas? Some kind of fourth dimensional measurement?

    If you have a form that collects user data and a form that collects financial data, then you must be collecting Datas.

    Collecting Datas sound very borgish, even tough I just know of a single Data. But maybe I'm wrong.

  • (cs) in reply to ShatteredArm
    ShatteredArm:
    JD:
    amischiefr:
    JamesQMurphy:
    JD:
    Professionals treat all warnings as errors. Amateurs ignore warnings. Idiots suppress warnings.
    Nice. That's going on my wall.
    Both of you are idiots. What if you are using Java 1.5 or higher, and for some reason you cannot use Generics for a data type. So you're an idiot for suppressing the warnings for this? lrn2Java nubs
    Don't be a retard. There will always be a limited number of legitimate reasons to suppress certain warnings and these should be judged on a case by case basis. But suppressing a deprecation warning because your solution "works incredibly well" is completely idiotic and, for someone in my position, completely unacceptable. It is perfectly obvious that the developer suppressed this warning just to make it disappear, since that is easier than fixing it. I'm sorry, but professionals treat all warnings as errors. You may not fall into the category of "professional" but maybe one day...

    If you're doing some revenue-generating operation, why would you throw out the whole thing if you retrieved the information you want, but with a warning? Sorry, you're wrong, professionals don't treat all warnings as errors. They log all warnings, and then handle specific warnings on a case-by-case basis, depending on whether it's a show-stopping situation. And then they make a business decision on whether previously unencountered warning situations should break the entire operation, or if they too should simply be logged. Then, they monitor the logs, especially during the test and beta phases. That's what professionals do. They don't naively throw out any and every result because there was a non-critical warning.

    Revenue generating compile cycles? What are you on and where can I get some?

  • (cs) in reply to Tom
    Tom:
    Give the kid a break. Why do you need to create a date format object every time the method is called? I guess your code has it's own WTF, but I have to say, I really appreciate the fact that you showed your fix. Most are afraid of doing that and I understand why - their code probably has ten times more WTFs than the original.

    Captcha: transverbero Aare we still posting captchas?

    This is java - you probably create one DF per format (that's what the class is for) the first time, then reference them on subsequent calls.

  • Dirk Diggler (unregistered) in reply to Percy the Pedant
    Percy the Pedant:
    Mizchief:
    I actually have a B.S in Software Engineering. It pisses me off that now anyone that codes is called a "Software Engineer" when they have no training in engineering princepals. My job for the last few years is to take an organic developer-loved application and turn it into a engineered product by using methodical development processes and keeping track of the project using metrics.

    If your trying to build hardware than a EE degree is probably a good idea, but your wasting time if you want to build software, you would be better off with regular CS, Software Engineering, or Systems Engineering.

    I've thought about going back to school to get my masters in either Systems Engineering or Industrial Engineering have any of you WTFers' gone this route?

    When you do, please sign up for a remedial English class. . . it's "principles", not "princepals", "you're", not "your" (it's a contraction of "you are", not a possessive), and "then", not "than".

    I know a couple of EEs and a chemist or two, as well, who can not only program but can actually compose a grammatically correct sentence.

    Sheesh.

    Hold on, I read those same grammatical errors and assumed that they were intentional. 'Mizchief' were you trolling for grammar pedants?

  • Tom (unregistered) in reply to Percy the Pedant

    Have you ever considered that some people might not be native English speakers? Does the fact that someone types "your" instead of "you're" change the logic of their statement in any way? If you can't figure out what someone means because of a few simple mistakes, you need some flexibility in your way of thinking and shit-loads of common sense. I'm sure you're an awful and lonely person because it must be incredibly difficult for someone to be near you as you keep correcting everything they say and you always pay attention to the contents of their message instead of the actual meaning. Regarding your "friends" (sorry, but imaginary ones don't count, so we need the quotes around that word) I'd like to say that if something is possible it's not also necessary. I don't need a degree in English to be able to do my job properly. I'm a fat and lazy programmer which means that you MUST also become like that, just because it's possible. Forget everything else that you're doing, throw your children in the trash can, eat your dog and kill your spouse with a corkscrew so that they can leave you alone enough time to become fat and lazy. Some people actually have something better to do than just get another degree so they can bitch to everyone about how lame their English sk1llz0rz are. I'm sure that word hurt you. I'm sure it hurt bad and you will feel it for the rest of your life.

    We don't have a language compiler and I really don't see why everyone MUST be able to type perfect English in order to stop being considered The Idiot of The Universe by some dumb ass nazi. </troll>

    Sorry about this, but a bit of rant is necessary from time to time, in order to put people back in their cages and make them remember what this place is all about - turning the worst mistakes in the world in something a bit more pleasurable by having a few laughs with other peoples from around the world. (The last one was intentional because I know that to language-obsessed freaks it REALLY hurts to read that word typed like that)

  • Mike5 (unregistered) in reply to Code Dependent
    Code Dependent:
    What disturbs me is the parameter name: "datas". Since "data" is already the plural of "datum", what is datas? Some kind of fourth dimensional measurement?

    Well, clearly you are NOT an engineer...

    Br,Mike5

  • WTF (unregistered)

    TRWTF is that "deprecation" is the correct spelling.

  • James Schend (unregistered) in reply to MindChild
    MindChild:
    I don't think this is necessarily a WTF at all. I think it is pretty apparent that this is likely a C++ programmer thrown into Java. If you have ever been in such a situation, you KNOW that you don't know all of the cool little language features... so you use what is good practice elsewhere. This is how you would break a loop in C/C++, without a goto. And it is clear what and why you are trying to do it.

    But that's the only time left you GET to use a GOTO in C++. When those situations come up, I happily embrace my GOTO friend to solve the problem.

Leave a comment on “Extensive Date Parsing”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article