Error in errormessage



  • While trying to compile some code with Visual Studio 2008 I got the following error:

    fatal error LNK1169: one or more multiply defined symbols found

     



  •  It's the adverb of multiple, so it may not be the best wording ever, but it's correct.



  • @Neuromancer said:

    one or more multiply defined symbols found

    It would be a dozen times less confusing if they removed the "one or more":

    Fatal error: multiply defined symbols found



  • This is why we need editors who care about little things like why a hyphen is different to a dash.

    "multiply-defined symbols" is much easier to understand.  The hyphen joins together the two words which form one conceptual unit. 

    Not a WTF.



  •  not a wtf.. but clumbsy.. you could email MSFT about it.. from my understanding customer feedback does it forewarded to the appropriate team.  so you might get it changed by just suggesting the hyphen form instead



  • @blakeyrat said:

    Fatal error: multiply defined symbols found
     

    Possible interpretation:

    Fatal error: Please multiply all of these symbols that I found.



  • @Kazan said:

     not a wtf.. but clumbsy.. you could email MSFT about it.. from my understanding customer feedback does it forewarded to the appropriate team.  so you might get it changed by just suggesting the hyphen form instead

    Your understanding is incorrect. Since Ballmer took over, feature requests (even critical ones, like Drive Extender in WHS 2) are ignored and the only bugs that get fixed are those that are show-stoppers. If you don't believe me, try filing a feature request on Connect and see how long it takes before it gets closed with a generic message.



  • @The_Assimilator said:

    If you don't believe me, try filing a feature request on Connect and see how long it takes before it gets closed with a generic message.

    I was successful in getting a SQL Server Management Studio bug fixed that way-- the hard part was convincing them the bug existed! "Our program doesn't open windows off screen." "Uh, yes it does, here's repro directions." "No our program can't do it." "Here's a fucking screenshot." "Ok... well it's fixed in the next version anyway." "GEE WHY'D YOU NEED TO FIX IT IF YOUR PROGRAM NEVER HAD THE PROBLEM? EH? EH?" ... anyway.

    Considering most other products I submit bugs to completely ignore them for months on end... well, I'd say Microsoft is above average. But the whole industry stinks to high heaven.


Log in to reply