Yeah, I'm absolutely unfamiliar with the Xcode environment, I'm afraid. It could be that one of their header files includes <string>, and so they get away with not explicitly including it. Perhaps someone else more familiar with Mac dev can comment?
Xcode targets have a prefix header (a header specified in the build settings that gets magically #included before any other header and which can optionally be precompiled). If you see some code using something it hasn't explicitly #included, it's likely from a file that's already been #included by the prefix header.
Who are these jokers to be asking you about program synthesis with types? You should be the one asking them questions. :P
You may be kidding but I had to do 2 years more work on my PhD because I failed to call out my external examiner for totally misunderstanding my thesis and for claiming that worked existed that did not which he claimed my thesis duplicated.
If I had just said "You are totally wrong, what are you talking about you crazy person" in the opening 5 mins my life would have been a lot better
In the early iPhone/iPad era when you went to go program an app with Apple's libraries, the libraries would very frequently communicate with you about things such as, for example, trying to set the property of a property of a framework object.
Had someAppleObjectProperty been nil, I would have gotten a log warning stating as such, and could correct my code. Often times especially with user interface controls, it would have actually thrown a runtime exception which would just kill the app. This was a good thing. It makes it less likely for you to ship buggy code.
now it seems par for the course for them to just tell you nothing, and you get to run that code 30 times wondering why the result of that line does absolutely nothing
because Objective-C is supposed to accept that code and silently fail even if someAppleObjectPoperty is nil
The documentation no longer tells you anything about what the value of that property is upon initialization. Here's the documentation preamble for the object in question
A [Redacted] object displays [redacted].
That's it. That's the whole thing. The subsection dedicated to someAppleObjectProperty has no entry for its default value.
You just have to be inspecting everything in the framework at runtime all the time to figure what you can and cannot do
this is actually worse than javascript, and I hate javascript
My hardest class was Radio Systems Engineering (yeah, yeah, did a EEE degree, not a CS degree, but I thought it might be fun to contribute).
You know that moment in your life when you learn F=ma, and you're like, "Wow, this is pretty cool."
And then later, you learn about relativity, how Newton's laws were just an approximation (but very accurate at low velocities), and then your mind is blown at the implications? And then there's some higher order physics beyond that which I'm sure exists, but I'm unaware how to adequately describe, and then your mind is so exploded that you just start drooling at the mouth when you start hearing about it?
Radio Systems engineering is like that, but for electrical signals.
You know how in high school, you're taught V=IR, and how the voltage at both ends of an ideal wire is the same? Then in an electronics degree, you get taught V=IZ, the generalised form of Ohm's Law for steady state AC circuits (which simplifies back to V=IR for DC circuits), then you get introduced to transient analysis (a whole other ball game, Laplace transforms etc). So all this is building on high school physics, which is nice and all, and everything makes sense.
So for everyday purposes, you can assume that the voltage on both ends of a wire is the same.
This is a lie an approximation which Radio Systems Engineering exposes.
All wires are actually transmission lines - even your ideal wire. This ends up having to be considered in any form of medium/high speed electronic design (rule of thumb: > 100MHz). The higher the frequency, the more concerned with it you have to be.
I mock those digital designs who thought they would never have to deal with anything analogue ever again. Digital is just saturated analogue signals, after all. :P
My EMag class wasn't too terrible, but you better remember your 3D calculus before going in or you're going to fall behind pretty fast.
My worst class was either the sophomore circuits lab(s) (15+ hours/week of work for 2 hours of credit) or the intro to microelectronics class (semiconductor physics to full op-amp design in 15 weeks, lol ok).
Protip:
If you're writing a query and you need to join a table inside a nested join that you've already joined earlier in the query, remember to give it a new alias!
Turned a 10 second query with 544 rows returned to a 70 second query with 194k returned.
Whoops!
0
gavindelThe reason all your softwareis brokenRegistered Userregular
I can't log into my new development environment until I get cleared. Clearance is waiting on my manager...who is on vacation.
Welp, this here documentation is riveting. At least I got building access today so I don't require an escort to get in.
Angels, innovations, and the hubris of tiny things: my book now free on Royal Road! Seraphim
I can't log into my new development environment until I get cleared. Clearance is waiting on my manager...who is on vacation.
Welp, this here documentation is riveting. At least I got building access today so I don't require an escort to get in.
Whenever I got hired at Lockheed it took a full 3-4 weeks until I could actually work on something. Waiting for network access, base access, clearance, etc.
Protip:
If you're writing a query and you need to join a table inside a nested join that you've already joined earlier in the query, remember to give it a new alias!
Turned a 10 second query with 544 rows returned to a 70 second query with 194k returned.
Whoops!
Anything more than a 1 line SQL statement if you're not in the practice of aliasing everything, what are you doing with your life?
The table name on this one is very short, and 99% of the time I only ever use it once. Most of my other tables get aliased, this one just slipped through.
You just have to be inspecting everything in the framework at runtime all the time to figure what you can and cannot do
this is actually worse than javascript, and I hate javascript
It's a lot better in the next rev of their tools. All the OS-provided Obj-C classes are marked up with annotations to indicate whether properties can ever be nil and the compiler will warn you (but not error) accordingly if you violate those expectations. Essentially, they're fiddling with Obj-C in order to make it play nicer with Swift.
So, if you're not required to use a "stable" toolchain, you ought to consider switching to Xcode 7.
You could also try out Swift. Swift 2.0, which is part of the Xcode 7 distribution, is super-nice.
Took me about 3 days to get started on my current job, and most of that was getting local admin on my laptop so I could run anything.
The other part was learning about the system we're monitoring.
so ask me anything about ALOHAnet
(actually I don't know that much about the protocol itself, but instead about certain devices that use it)
End on
I wish that someway, somehow, that I could save every one of us
0
KakodaimonosCode fondlerHelping the 1% get richerRegistered Userregular
It's time for more WTF moments in specs
Revised timestamp will represent the number of microseconds since midnight EST. The value will be a 6-byte string of ASCII-displayable characters relative to ASCII space (" ") representative of a base95 number.
Revised timestamp will represent the number of microseconds since midnight EST. The value will be a 6-byte string of ASCII-displayable characters relative to ASCII space (" ") representative of a base95 number.
That's weird, usually when people write standards they intend for others to use them.
I mean they could feasibly have just used, like, numbers. Longs are not that expensive.
Or if you just have the biggest boner ever for character encoding, send it in base64, you know, an encoding that people actually use regularly.
You only need a single more digit. And the difference between 6 bytes and 7 is absolutely negligible.
I mean they could feasibly have just used, like, numbers. Longs are not that expensive.
Or if you just have the biggest boner ever for character encoding, send it in base64, you know, an encoding that people actually use regularly.
You only need a single more digit. And the difference between 6 bytes and 7 is absolutely negligible.
I assume this is to deal with x-platform serialization, because why would you ever do it that way?
bowen on
not a doctor, not a lawyer, examples I use may not be fully researched so don't take out of context plz, don't @ me
I mean they could feasibly have just used, like, numbers. Longs are not that expensive.
Or if you just have the biggest boner ever for character encoding, send it in base64, you know, an encoding that people actually use regularly.
You only need a single more digit. And the difference between 6 bytes and 7 is absolutely negligible.
I assume this is to deal with x-platform serialization, because why would you ever do it that way?
Like, how?
"Numbers are hard to serialize, better use a string!" ?
I mean they could feasibly have just used, like, numbers. Longs are not that expensive.
Or if you just have the biggest boner ever for character encoding, send it in base64, you know, an encoding that people actually use regularly.
You only need a single more digit. And the difference between 6 bytes and 7 is absolutely negligible.
I assume this is to deal with x-platform serialization, because why would you ever do it that way?
Like, how?
"Numbers are hard to serialize, better use a string!" ?
I didn't say it made sense!
if it were me and I was required to make a system it'd be straight up something like:
yyyyMMddhhmmssxxyy....
not a doctor, not a lawyer, examples I use may not be fully researched so don't take out of context plz, don't @ me
Semiconductors just by themselves are pretty mindblowing. Let alone actually designing stuff with them.
For me General Relativity was the grand motherfucker of all modules. I still have no idea how I passed that one.
I used to work in a semiconductor fab. Everything going on there was really impressive (and I had almost nothing to do with any of it). I wish I could go back and re-read all of the documentation and stuff now that I'm about 10000x more educated in math.
Holy shit. Creating a simple HTML page without javascript is painful as fuck.
<html>
<head>
<title>Simple HTML Page W/O JavaScript</title>
</head>
<body>This is a simple HTML page without JavaScript. It doesn't seem very painful.</body>
</html>
Bah, you know what I mean.
Look at this: HOW AM I SUPPOSED TO CENTER THIS?!
Text is in a span. I have tried vertical-align, padding-top, margin-top... nothing has an effect.
The answer is not to vertically center stuff in HTML. Use a padding instead. Vertical center isn't something HTML copes with very well at all. Horizontal center, sure. Vertical? Not so much.
Today's just one of those days where I am *super duper pissed* and I ended up leaving early just to not tell my boss' boss to go fuck himself with a goddamned steel pipe.
I mean they could feasibly have just used, like, numbers. Longs are not that expensive.
Or if you just have the biggest boner ever for character encoding, send it in base64, you know, an encoding that people actually use regularly.
You only need a single more digit. And the difference between 6 bytes and 7 is absolutely negligible.
I assume this is to deal with x-platform serialization, because why would you ever do it that way?
Like, how?
"Numbers are hard to serialize, better use a string!" ?
I didn't say it made sense!
if it were me and I was required to make a system it'd be straight up something like:
yyyyMMddhhmmssxxyy....
But... a long expressing milliseconds since Unix epoch is already a standard for times...
Today's just one of those days where I am *super duper pissed* and I ended up leaving early just to not tell my boss' boss to go fuck himself with a goddamned steel pipe.
You could probably vent here if you anonymize it enough.
Posts
Xcode targets have a prefix header (a header specified in the build settings that gets magically #included before any other header and which can optionally be precompiled). If you see some code using something it hasn't explicitly #included, it's likely from a file that's already been #included by the prefix header.
Already defended! That picture was the last time I'll ever see the hard copy of the thesis that's going into the library. =D
You may be kidding but I had to do 2 years more work on my PhD because I failed to call out my external examiner for totally misunderstanding my thesis and for claiming that worked existed that did not which he claimed my thesis duplicated.
If I had just said "You are totally wrong, what are you talking about you crazy person" in the opening 5 mins my life would have been a lot better
I made a game, it has penguins in it. It's pay what you like on Gumroad.
Currently Ebaying Nothing at all but I might do in the future.
So are you officially Dr Kambing?
Either way, much respect.
3DS: 0473-8507-2652
Switch: SW-5185-4991-5118
PSN: AbEntropy
In the early iPhone/iPad era when you went to go program an app with Apple's libraries, the libraries would very frequently communicate with you about things such as, for example, trying to set the property of a property of a framework object.
Consider the following:
[[myView someAppleObjectProperty] setSomeValue:foo];
Had someAppleObjectProperty been nil, I would have gotten a log warning stating as such, and could correct my code. Often times especially with user interface controls, it would have actually thrown a runtime exception which would just kill the app. This was a good thing. It makes it less likely for you to ship buggy code.
now it seems par for the course for them to just tell you nothing, and you get to run that code 30 times wondering why the result of that line does absolutely nothing
because Objective-C is supposed to accept that code and silently fail even if someAppleObjectPoperty is nil
The documentation no longer tells you anything about what the value of that property is upon initialization. Here's the documentation preamble for the object in question
That's it. That's the whole thing. The subsection dedicated to someAppleObjectProperty has no entry for its default value.
You just have to be inspecting everything in the framework at runtime all the time to figure what you can and cannot do
this is actually worse than javascript, and I hate javascript
tl;dr im quitting and switching to C++
My EMag class wasn't too terrible, but you better remember your 3D calculus before going in or you're going to fall behind pretty fast.
My worst class was either the sophomore circuits lab(s) (15+ hours/week of work for 2 hours of credit) or the intro to microelectronics class (semiconductor physics to full op-amp design in 15 weeks, lol ok).
For me General Relativity was the grand motherfucker of all modules. I still have no idea how I passed that one.
http://steamcommunity.com/id/pablocampy
If you're writing a query and you need to join a table inside a nested join that you've already joined earlier in the query, remember to give it a new alias!
Turned a 10 second query with 544 rows returned to a 70 second query with 194k returned.
Whoops!
Welp, this here documentation is riveting. At least I got building access today so I don't require an escort to get in.
Whenever I got hired at Lockheed it took a full 3-4 weeks until I could actually work on something. Waiting for network access, base access, clearance, etc.
Anything more than a 1 line SQL statement if you're not in the practice of aliasing everything, what are you doing with your life?
It's a lot better in the next rev of their tools. All the OS-provided Obj-C classes are marked up with annotations to indicate whether properties can ever be nil and the compiler will warn you (but not error) accordingly if you violate those expectations. Essentially, they're fiddling with Obj-C in order to make it play nicer with Swift.
So, if you're not required to use a "stable" toolchain, you ought to consider switching to Xcode 7.
You could also try out Swift. Swift 2.0, which is part of the Xcode 7 distribution, is super-nice.
I don't know if that means I've leveled up or if I've sold my soul to an eldritch being from the angled bracket dimensions.
Wow.
The other part was learning about the system we're monitoring.
so ask me anything about ALOHAnet
(actually I don't know that much about the protocol itself, but instead about certain devices that use it)
Time sucks enough to deal with period, let alone making it the most obtuse thing ever...
That's weird, usually when people write standards they intend for others to use them.
3DS: 0473-8507-2652
Switch: SW-5185-4991-5118
PSN: AbEntropy
One-off error in their spec!
just use unix timestamps, I promise they're OK!
Or if you just have the biggest boner ever for character encoding, send it in base64, you know, an encoding that people actually use regularly.
You only need a single more digit. And the difference between 6 bytes and 7 is absolutely negligible.
I assume this is to deal with x-platform serialization, because why would you ever do it that way?
Like, how?
"Numbers are hard to serialize, better use a string!" ?
I didn't say it made sense!
if it were me and I was required to make a system it'd be straight up something like:
yyyyMMddhhmmssxxyy....
yumm daaahhhmm ssexxxxyyy?
Oo\ Ironsizide
Y'all motherfuckers need flexbox. https://css-tricks.com/snippets/css/a-guide-to-flexbox/
Fuck.
Discretion is the better part of not-getting-fired.
But... a long expressing milliseconds since Unix epoch is already a standard for times...
3DS: 0473-8507-2652
Switch: SW-5185-4991-5118
PSN: AbEntropy
Geth, activate protection protocol 7.
You could probably vent here if you anonymize it enough.