|
Munkeymon posted:Do yourself a favor and don't look into the intermediate code the C# compiler generates to support all the neat language features that have been bolted on since 2.0 You could say the same thing about machine code generated by literally any compiler in existence. It doesn't matter what the code gets turned into, just what the actual behavior is. (And yes, IL is machine code.)
|
# ? Mar 29, 2011 21:25 |
|
|
# ? May 29, 2024 15:11 |
|
code:
|
# ? Mar 29, 2011 22:31 |
|
What's the horror?
|
# ? Mar 29, 2011 23:04 |
|
Scaevolus posted:What's the horror? Putting semicolons on the next line.
|
# ? Mar 29, 2011 23:06 |
|
Scaevolus posted:What's the horror?
|
# ? Mar 29, 2011 23:14 |
|
Janin posted:It's standards-compliant code that has different output depending on whether the compiler is in C89 or C99 mode. That's not a horror, it's a specification check at runtime.
|
# ? Mar 30, 2011 00:06 |
|
king_kilr posted:If you think about how += should be implemented on immutable objects for about a quarter of a second you'd figure it out. Eric Lippert posted about this exact problem today.
|
# ? Mar 30, 2011 06:55 |
|
HORATIO HORNBLOWER posted:Eric Lippert posted about this exact problem today. For once I think C++ has the right idea here. += is not the same operator as +. You can create a correct + from +=, you cannot create += from +. So the solution is simply for everyone to define the mutable operator (+=) to defined the non-mutable operator. If the object is immutable, simply don't define +=.
|
# ? Mar 30, 2011 07:03 |
|
Ryouga Inverse posted:You could say the same thing about machine code generated by literally any compiler in existence. It doesn't matter what the code gets turned into, just what the actual behavior is. I wasn't talking about IL.
|
# ? Mar 30, 2011 14:16 |
|
So my boss comes into my office the other day and says that we've sold some Canadian group on our display system. They only have one request, that we change all Imperial units to SI. This is a nightmare because there's no structure or coherence to any of the GUIs we write. Each display and each dialog window is the pet project of someone, some single person, who works on it alone with no peer review, and no standards to guide them. But I shouldn't fear because my boss has the solution! He picked up a dry erase marker and wrote this on my white board: ENV_VAR_UNITS_CONVERSION_FACTOR="0.9144" The solution is so obvious!
|
# ? Mar 31, 2011 02:51 |
|
Lexical Unit posted:So my boss comes into my office the other day and says that we've sold some Canadian group on our display system. They only have one request, that we change all Imperial units to SI. This is a nightmare because there's no structure or coherence to any of the GUIs we write. Each display and each dialog window is the pet project of someone, some single person, who works on it alone with no peer review, and no standards to guide them. I... what? What the gently caress does that even convert?
|
# ? Mar 31, 2011 03:21 |
|
ENV_VAR_UNITS, duh.
|
# ? Mar 31, 2011 03:41 |
|
Lexical Unit posted:So my boss comes into my office the other day and says that we've sold some Canadian group on our display system. They only have one request, that we change all Imperial units to SI. This is a nightmare because there's no structure or coherence to any of the GUIs we write. Each display and each dialog window is the pet project of someone, some single person, who works on it alone with no peer review, and no standards to guide them. Sorry about your floating point future hell.
|
# ? Mar 31, 2011 03:42 |
|
Lexical Unit posted:So my boss comes into my office the other day and says that we've sold some Canadian group on our display system. They only have one request, that we change all Imperial units to SI. This is a nightmare because there's no structure or coherence to any of the GUIs we write. Each display and each dialog window is the pet project of someone, some single person, who works on it alone with no peer review, and no standards to guide them. Oh god. Your life just went to hell in a handbasket. (also, it's 1 yard = 0.9144 metres.)
|
# ? Mar 31, 2011 03:49 |
|
code:
|
# ? Mar 31, 2011 03:57 |
|
Thel posted:Oh god. Your life just went to hell in a handbasket.
|
# ? Mar 31, 2011 04:08 |
|
NotShadowStar posted:Sorry about your floating point future hell. Thank gord my boss doesn't work in finances, because I'm sure he'd use floats to store money. Instead he works in the defense industry where things like "quality" and "corectness" are of no real concern.
|
# ? Mar 31, 2011 04:10 |
|
BigRedDot posted:I work down the hall, I can assure you that we've already been trundled off to hell, and in much less pleasant accommodations, long long ago. Judged on a scale calibrated to the usual bright ideas at our workplace, this one barely moves the needle. I ... just .... what? Anyway, I only just noticed that that "conversion factor" was written up as a string also.
|
# ? Mar 31, 2011 04:19 |
|
http://jtcfrost.svn.sourceforge.net...in&pathrev=2865 I'd better comment this out in case anyone needs it later! *Commits code to SVN repo*
|
# ? Mar 31, 2011 04:21 |
|
Munkeymon posted:I wasn't talking about IL. Well, the intermediate C# code generated to support lambdas and stuff is still generated code. Just another pass of the compiler. Generated code isn't a horror if you don't ever have to edit it. Frontpage did not follow this rule.
|
# ? Mar 31, 2011 05:35 |
|
Lexical Unit posted:This wouldn't be a problem if you used SI to begin with like all right-thinking people do. Seriously though, I'm so sorry.
|
# ? Mar 31, 2011 15:55 |
|
Lexical Unit posted:They only have one request, that we change all Imperial units to SI. This is a nightmare... Calmly explain to your boss or the customer that this is how spacecraft explode.
|
# ? Mar 31, 2011 16:46 |
|
pokeyman posted:Calmly explain to your boss or the customer that this is how spacecraft explode.
|
# ? Mar 31, 2011 16:55 |
|
Ryouga Inverse posted:Well, the intermediate C# code generated to support lambdas and stuff is still generated code. Just another pass of the compiler. Generated code isn't a horror if you don't ever have to edit it. I thought he was complaining about the Python pseudocode that explained the weird behavior being ugly, which it was, but it wasn't exactly something people would normally see or even write.
|
# ? Mar 31, 2011 17:36 |
|
I just had a web dev interview where the guy spent 5+ mins insulting my work and portfolio. He said it didn't have any CSS at all. This is a huge company that you're all familiar with. Just for kicks I ran the W3C validator on the subsection of the site he is responsible for: quote:132 Errors, 77 warning(s) On XHTML 1.0 Transitional doctype. And these are basic, obvious mistakes, not kludges but downright fuckups. (I don't release a site to a client until it validates XHTML 1.0 Strict)
|
# ? Mar 31, 2011 17:48 |
|
revmoo posted:
Why are you still using that DOCTYPE?
|
# ? Mar 31, 2011 18:17 |
|
What in the world is wrong with that doctype?
|
# ? Mar 31, 2011 18:35 |
|
revmoo posted:What in the world is wrong with that doctype? It's depreciated, and if you want to actually use any feature of HTML5, your stuff won't validate any more? What features of XHTML Strict do you actually need? Lumpy fucked around with this message at 18:44 on Mar 31, 2011 |
# ? Mar 31, 2011 18:42 |
|
Lumpy posted:It's depreciated, and if you want to actually use any feature of HTML5, your stuff won't validate any more? What features of XHTML Strict do you actually need? Deprecated in favor of HTML5? I'm not switching to HTML5 until IE catches up.
|
# ? Mar 31, 2011 18:47 |
Also the HTML 5 doctype is so much easier to remember: <!DOCTYPE html>
|
|
# ? Mar 31, 2011 18:48 |
|
revmoo posted:Deprecated in favor of HTML5? I'm not switching to HTML5 until IE catches up. "catches up" with what? IE6 renders pages perfectly fine using the HTML5 doctype. I suspect you are a little unsure on what a Doctype is and does. <!DOCTYPE html> puts IE6 into standards mode exactly like XHTML 1.0 strict. A note on IE6 and HTML5: http://ejohn.org/blog/html5-doctype/ EDIT: and another: http://diveintohtml5.org/semantics.html
|
# ? Mar 31, 2011 18:52 |
|
Fair enough, I just don't really like the idea of declaring html5 if I'm not using any of its features. I see your points though.
|
# ? Mar 31, 2011 19:01 |
|
revmoo posted:132 Errors, 77 warning(s) To be fair, one unclosed paragraph tag can result in 1 error for every following paragraph, so you can cause 100 errors with one mistake quite easily. Also, since when is XHTML 1.0 Strict deprecated?
|
# ? Mar 31, 2011 20:21 |
|
Lumpy posted:"catches up" with what? IE6 renders pages perfectly fine using the HTML5 doctype. I suspect you are a little unsure on what a Doctype is and does. <!DOCTYPE html> puts IE6 into standards mode exactly like XHTML 1.0 strict. quote:A note on IE6 and HTML5: http://ejohn.org/blog/html5-doctype/ And MS will be backporting support for html 5 from IE8 to IE6 when exactly? EDIT: Also just wanting to reiterate the question, when did XHTML get deprecated?
|
# ? Mar 31, 2011 21:34 |
|
Zombywuf posted:EDIT: Also just wanting to reiterate the question, when did XHTML get deprecated? When the working group for XHTML2 got disbanded and HTML5 was declared the successor to XHTML 1.1
|
# ? Mar 31, 2011 21:41 |
|
Otto Skorzeny posted:When the working group for XHTML2 got disbanded and HTML5 was declared the successor to XHTML 1.1 And XHTML was deprecated when? You seem to be claiming the iPhone has been deprecated because of the iPad.
|
# ? Mar 31, 2011 21:44 |
|
Zombywuf posted:And XHTML was deprecated when? You seem to be claiming the iPhone has been deprecated because of the iPad. No, I'm claiming something analagous to the iphone 3gs being deprecated in favor of the iphone 4.
|
# ? Mar 31, 2011 21:51 |
|
I don't like HTML5 because it's a living standard.
|
# ? Mar 31, 2011 22:08 |
|
There's no reason not to use pre:<!DOCTYPE html> Hell even the new HTML semantic elements (time, article, section etc) work perfectly fine all the way back to IE6 if you do document.createElement for IE and display: block; for Firefox.
|
# ? Mar 31, 2011 22:25 |
|
|
# ? May 29, 2024 15:11 |
|
NotShadowStar posted:Hell even the new HTML semantic elements (time, article, section etc) work perfectly fine all the way back to IE6 if you do document.createElement for IE and display: block; for Firefox. That is the very definition of not working perfectly fine.
|
# ? Mar 31, 2011 22:32 |