« first day (456 days earlier)      last day (3563 days later) » 
00:00 - 20:0020:00 - 00:00

8:00 PM
long long ago; // in a far away galaxy
3
 
@Morwenn started a new job 3 weeks ago, and haven't had nearly as much time since :(
i still creep a lot, but i don't get to post much
(well really I could fairly easily find time, but... :/)
 
@nhgrif How would I create a private array in the interface?
 
@syb0rg I don't know what language it's about, but private/protected and interface usually don't go together
 
0
Q: How can this autoloader be improved?

CONtextI don't understand the concept of autoloaders, other than the bare minimum, which is that to load a class file when the class is being called. Or as the php manual cite's it, to avoid having to require multiple time. I get that, but what I don't understand is the complexity behind almost all th...

 
> in a far away galaxy
Really?
“A long time ago in a galaxy far, far away....”
2
 
8:21 PM
@kleinfreund Close enough. :P But thanks.
 
Speaking of Star Wars, I just posted this answer.
 
Just recently watched all three of ’em.
And you know what I mean by all three.
 
Surely that includes The Phantom Menace, right?
=)
 
And the two successors, you are right.
 
I enjoyed all of them.
 
8:30 PM
Time for me to go to work, bye @all!
 
See you @syb0rg
 
@syb0rg SELECT * FROM MyTable; -- selects all columns from my table
 
8:46 PM
This new user could use one more vote.
 
UV. He/she could also use a user name ;)
But yeah it is a pretty thorough post
 
He/she also hasn't been here ever since the question was posted. It's a good thing important clarifications weren't needed.
 
0
Q: Phrase extraction algorithm for statistical machine translation

alvasI have written the following code with the phrase extraction algorithm for SMT. GitHub # -*- coding: utf-8 -*- def phrase_extraction(srctext, trgtext, alignment): """ Phrase extraction algorithm. """ def extract(f_start, f_end, e_start, e_end): phrases = set() ...

0
Q: Searching a char in a "2D" list in Haskell

CraniumI have this working function circuitFind that I really don't find nice because I feel there is a better and simpler way to accomplish what it does. circuitFind :: Circuit -> Tile -> Maybe Position circuitFind c t = unpack . find (\ p -> fst p /= Nothing) . enumerate . map findTile $ c where...

 
What is Visual C++ CPT120?
 
No idea
 
8:57 PM
If the OP means Visual Studio 2012, then deleted functions and type alias advice isn't going to be useful for them.
 
Sadly, that is true (that's what I use now).
 
@Jamal What's a ? A pointer that nils itself when the memory it points to is deallocated?
@syb0rg Put it in the class extension, in the .m file. Or put it in curly braces like this:
@implementation MyClass {
    NSArray *myArray;
}
 
Yes, pretty much.
 
With "class extension" being the @interface section in the .m file.
360
Q: What is the best comment in source code you have ever encountered?

Thomas BrattWhat is the best comment in source code you have ever encountered?

 
@nhgrif Well in C++, the smart pointer is responsible for deallocating the memory. The user doesn't have to worry about it. It doesn't NULL the pointer unless you provide your own custom deleter.
 
9:12 PM
So, it's ARC.
 
ARC?
Reference Count?
 
Automatic Reference Counting, which is what Objective-C has.
And in ARC, you have strong pointers and weak pointers.
Strong pointers increase the reference count. Weak pointers do not, but weak pointers nil themselves when the memory is deallocated.
Unless you've manually adjusted the reference count, memory can never be deallocated out from under a strong pointer, because memory isn't deallocated unless the reference count drops to 0.
...
 
I believe std::shared_ptr uses reference counting. std::unique_ptr assumes sole ownership of the object. and std::weak_ptr can point to an std::shared_ptr but does not increase or decrease the reference count.
 
#define if(x) if(!(x))
#define if while
592
A: What is the best comment in source code you have ever encountered?

Draemon/* This is O(scary), but seems quick enough in practice. */ followed by four nested for-loops

 
948
A: What is the best comment in source code you have ever encountered?

Sergey Kornilov// sometimes I believe compiler ignores all my comments

 
9:20 PM
187
A: What is the best comment in source code you have ever encountered?

Neil Kodner// no comments for you // it was hard to write // so it should be hard to read

172
A: What is the best comment in source code you have ever encountered?

proudgeekdadOur DBA found this in the middle of a 3000 line stored procedure written by a third party. /* IF DOLPHINS ARE SO SMART, HOW COME THEY LIVE IN IGLOOS? */

126
A: What is the best comment in source code you have ever encountered?

samoz/* This isn't the right way to deal with this, but today is my last day, Ron just spilled coffee on my desk, and I'm hungry, so this will have to do... */ return 12; // 12 is my lucky number

 
110
A: What is the best comment in source code you have ever encountered?

ealfFrom the 2004 Windows leak, __inline BOOL SearchOneDirectory( IN LPSTR Directory, IN LPSTR FileToFind, IN LPSTR SourceFullName, IN LPSTR SourceFilePart, OUT PBOOL FoundInTree ) { /...

^^This one is great.
 
Yeah.
101
A: What is the best comment in source code you have ever encountered?

Lyudmilpublic boolean isDirty() { //Why do you always go out and return dirty; }

whoops
66
A: What is the best comment in source code you have ever encountered?

Not JeK// //3.4 JeK My manager promised me a lap dance if I can fix this release //3.5 JeK Still waiting for that dance from my manager //3.6 JeK My manager got changed, the new manager is hairy, dont want the dance anymore //3.7 Jek Got that dance, yuck! //

 
@nhgrif does if(!!(true)) compile?
 
0
Q: Is that a fast implementation of reversing a string?

trueI thought of this algorithm today. It seems fast. But how can I know? #include <string.h> #include <stdlib.h> #include <stdio.h> #include <assert.h> /* * Reverse a string * the caller has to free dynamic memory allocated */ char *mon_string_rev(char *string) { char *out = malloc ( strlen...

 
I don't know.
But that doesn't actually matter.
Given #define if(x) if(!(x)) then...
if(!someBool) would be replaced with if(!(!someBool)) which should compile
 
9:36 PM
at least a proper compiler will warn you about usage of uninitialized objects
 
What's uninitialized?
54
A: What is the best comment in source code you have ever encountered?

vobjectI always liked what Paul DiLascia wrote in his file headers: // If this code works, it was written by Paul DiLascia. If not, I don't know // who wrote it

 
default value pointers
Object object;
 
I thought that it was considered bad practice (if not undefined behavior) to assume an implicit return value from main(). Also, std::endl is a better idea than "\n" because it will handle line endings correctly on the unfortunate systems that use "\r\n" instead. I'd also recommend #includes being grouped by system, then library, then local, then sorted within each group. — fluffy 6 mins ago
 
Are you continuing a conversation from somewhere?
 
Yeah, yours
 
9:37 PM
From where?
 
@nhgrif that line
 
It's not an object though.
Not necessarily anyway.
 
you could have a null check
 
You could.
 
then the preprocessor inverts it
and then the ultra-strict warnings level on the compiler shuts the build down
 
9:39 PM
But not all IDEs will warn about uninitialized objects.
 
because you verify null, then use the object
which is guaranteed to break
 
In Objective-C, it doesn't matter if the object is nil.
You can call methods on nil.
And it won't break.
 
and then it does what?
 
Returns 0
or NO or false or whatever.
 
yay, silent failures!
 
9:41 PM
Because you're not really calling a method on an object.
You're sending a message.
 
I am so glad I took 3D and not iOS mobile development
 
If there's an object at that memory location, the object will receive the message.
 
what
it's nil
there's nothing there
 
In the case that we send the message to nil, then there's not an object there.
But if it's not nil
you're not just "calling a method on an object"
You're sending a message to a memory location through the ObjC runtime.
 
the end result is code that doesn't work and doesn't crash
 
9:43 PM
If that memory location is an Objective-C object, the object handles the message.
 
that sounds abstract and false
they can't be constructed as such to be self-aware
 
@Jamal 1) The C++ standard guarantees that zero would be returned by default for the main function if you leave that out. 2) Completely false. Even on windows systems, std::endl appends a '\n'. The compiler is responsible for sorting out the line endings on its own. 3) Bad advice once again. Local headers, then libraries, and then platform-specific headers. Each group should then be sorted alphabetically.
 
or logically self-aware
the runtime handles that
 
You don't see \r\n coming up too often? You realize that Windows still has the largest desktop OS install base in the world, right? Not to mention that most textual network protocols use \r\n for their line endings... — fluffy 2 mins ago
I didn't know I would be getting into this debate.
 
I'm getting some of the specifics wrong, but I know the gist of it. If you're interested in the specifics of what Objective-C does at run time in this regard, this is a decent read
In computer science, dynamic dispatch is the process of selecting which implementation of a polymorphic operation (method or function) to call at runtime. Dynamic dispatch contrasts with static dispatch in which the implementation of a polymorphic operation is selected at compile-time. The purpose of dynamic dispatch is to support cases where the appropriate implementation of a polymorphic operation can't be determined at compile time because it depends on the runtime type of one or more actual parameters to the operation. Dynamic dispatch is different from late binding (also known as dynamic binding...
 
9:47 PM
And you may post that as a comment if you'd like.
 
@Jamal Just did.
 
> The language allows you to add methods to a object (or even more specifically to an object's class) at run time.
 
@jliv902 Cool. He seems to mostly be a Java person (based on SO tag scores).
 
64
Q: Sending a message to nil?

Ryan DelucchiAs a Java developer who is reading Apple's Objective-C 2.0 documentation: I wonder as to what sending a message to nil means - let alone how it is actually useful. Taking an excerpt from the documentation: There are several patterns in Cocoa that take advantage of this fact. The value re...

> The reason for this is to eliminate monkey code that doesn't do anything except keep the compiler happy. Yes, you get the overhead of one more method call, but you save programmer time, which is a far more expensive resource than CPU time. In addition, you're eliminating more code and more conditional complexity from your application.
One of the best examples in the answers to that question is working with an array returned from a function where the array could be nil
 
I hate things that I have to keep in mind, I'd rather be more explicit than perform clever hax
 
9:54 PM
In Java, you have to first check whether the array is nil or not. In Objective-C, you can just immediately foreach it, because the behavior of nil and an empty array in a foreach loop is going to be identical.
@Pimgd This isn't a clever hack. This is actually ELIMINATING something you have to keep in mind.
In Objective-C, you only ever do a nil check if it's important that the object isn't nil.
If you're going to iterate through objects in an array, it doesn't matter if the array is nil or not, because there's no difference between an empty array and nil.
 
or for comparing strings, or for object identity, or for any case where you actually NEED to do anything with an object
 
You don't have to nil check when comparing strings.
 
nil and nil is false
 
[@"Hello World" isEqualToString:nil]; returns the same thing as [@"foo" isEqualToString:@"bar"]
It doesn't matter if either string is nil, it only matters whether they're the same.
 
and if they're both nil you get false
 
9:57 PM
In this case, yes. But if they're both nil, something else is probably wrong.
But your program won't crash. Worse case scenario, your program is behaving incorrectly. And that's a better worse case scenario than a program that crashes.
 
that is a mighty dangerous statement
hiding faulty behavior is one of the best ways to break things
3
 
But if both of them being nil is a real scenario, then you should nil check them probably.
 
programming is hard enough as it is
 
But the fact of the matter is, realistically, most of the time it doesn't matter if the object is nil, and the fact that sending a message to nil doesn't crash your program ends up saving a TON of developer time.
 
why should I? I'm just doing an equals test
 
10:00 PM
In Java, you'd have to nil check them or risk Null Pointer Exception.
 
Okay maybe nil might not matter but 0 does
 
What?
 
if you do stuff with nil you get 0 back, right?
 
You get back an appropriate value based on what the method is supposed to return.
 
that 0 gets propagated through your code. It's a good way to wreck things, values that look legitimate but aren't
 
10:01 PM
[nil message] always returns nil if that's what you mean
(and nil is just an id typed 0 value)
 
It doesn't.
> If the method returns an object, any pointer type, any integer scalar of size less than or equal to sizeof(void*), a float, a double, a long double, or a long long, then a message sent to nil returns 0.
If the method returns a struct, as defined by the Mac OS X ABI Function Call Guide to be returned in registers, then a message sent to nil returns 0.0 for every field in the data structure. Other struct data types will not be filled with zeros.
If the method returns anything other than the aforementioned value types the return value of a message sent to nil is undefined.
 
so far, all languages I have worked with that allowed code to keep running after something went wrong have caused debug issues
that'd be PHP and AS2
what makes Obj-c different
 
You've never seen debug issues in Java?
You've never seen debug issues in C++?
 
@nhgrif ah interesting. Not sure why I thought it always returned nil.
 
Or any other language?
 
10:05 PM
ah I have, but those tend to point to the line where I fucked up
or, better yet, indicate that I have fucked up at all
 
And again, even if I spend slightly more time debugging, you're completely discounting the massive amount of time saved by almost never spending time nil checking... which affords me some extra time to find these nil issues.
 
if there's one thing I've learned from Java that I think also applies to ObjC: if you're explicitly checking for null, there's likely an interface problem somewhere :/
 
... what if I didn't nil check and just waited for the null pointer exception to come crashing through?
It'd be pretty obvious what went wrong
rather than getting some arithmetic error
 
Good to see you answering again, @Corbin. :-) I have added some additional things.
 
@nhgrif - by all accounts (especially yours), it seems that error handling in Obj-C requires discipline and procedure.... In Java, it sort of just happens....
 
10:10 PM
@Jamal :) hopefully I shall continue to do so
 
I have to say I prefer the system where it is done for you, and you have to explicitly ignore the problem, rather than explicitly handle it.
Corbin, we all hope so. ... ;p
 
:D
My work does code reviews, and I think I'm the only person who doesn't hate them..... lol
5
 
Maybe I'll leave more questions for you once I get my goldie. ;-)
 
:p
 
I may even be able to get it before I go back to school.
 
10:12 PM
@rolfl This is a relatively fair assessment. There are still exceptions in Objective-C.
But exceptions are reserved for truly exceptional behavior--behavior for which the program can not recover from.
You might use try-catches deep in a library, but at the higher levels of Objective-C programming, they're highly discouraged against, because if something is throwing an exception, you need to change the source code to fix the problem.
Instead, expected but uncommon problems are handled with NSError objects, which do not cause the program to crash.
 
Yeah, Jav has three levels.... Exceptions that are almost certainly programming bugs (Runtime Exceptions), Exceptions that are environmental problems that are things a decent program can recover from (IO Exceptions, permission exceptions), and then Errors, which are System failures that the program will likely never be able to handle
 
In a lot of cases, you really don't care what the error is, you only care whether or not it happened. In still other cases, you might not even care that an error occurred.
Your program will never crash because you hit a bump in the road trying to do file IO.
 
^^^ thats just a very worrying thing to hear from a programmer
 
Your file IO may not do what it's supposed to do and you'll get an NSError object.
Well, let's say I'm writing a backup to file every 5 minutes.
I'm doing it every 5 minutes.
 
and you have to check each IO explicitly... to make sure each IO succeeded?
 
10:16 PM
If one of them broke and didn't write, I don't care.
It'll try again in 5 minutes anyway.
 
What if you are writing a log record?
or hundreds of them?
 
Then I might care, and I can check the error.
 
@rolfl Indeed, that's the general paradigm of ObjC with regards to errors. It's a lot more C than objective with that regard :/.
 
And do something.
 
Or reading data from a socket?
 
10:17 PM
Any time I care, I just check the error object.
Methods that can have an error will take an NSError **
 
So, to create a robust program in Obj-C, you have to follow each statement with a success-check?
 
And as soon as an error is encountered, the error object is built, the pointer is pointed to, and the method returns.
So you have:
[someObject doStuff:stuff error:error];
if (error) { // handle error
 
This, for the record, is why I like programming in Java, because you can spend your time programming, not error handling.
 
Where Java would have:
try {
    someObject.doStuff(stuff);
} catch (Exception ex) {
    // handle exception
}
You spend the same amount of time handling the error...
It's just done differently.
And if you don't catch it in Java, your program crashes.
 
It was crashing anyway
 
10:20 PM
If you don't check the error variable in ObjC, the program still runs.
 
(if you did not catch it).
 
Right.
It's the same amount of error handling.
 
rolfl's point is that it's very hard in Java for an error to sneak through unnoticed.
 
No, it's not.
 
The only difference is whether or not it crashes if you don't do anything about it.
 
10:20 PM
If you forget an error check in ObjC you can (will) have a hidden error.
that's never discovered
that's rather difficult to do in Java
 
How is it not the same amount of error handling?
 
For a start, in Java, you can centralize your error handling.
you can do thousands of calls/statements,e tc, and have just one catch.
 
You can do that in ObjC too.
 
or, even better, you can just tell people that this code may fail, and that they have to handle it.
 
That's what an error: argument in a method does.
 
10:22 PM
Except, in your code, you have to handle that error and pass it back.
 
No...
If you're taking an error argument in, you don't handle the error.
When the error occurs, you create an NSError object, set the value, and stop the method.
 
I guess there's something I am missing, but it's not that important to me to understand.
 
It's the same you'd do in Java for a method that throws an exception. When the exception behavior occurs, you create the exception object and throw it.
 
@nhgrif But, you have to check that the error happened before you can: When the error occurs, you create an NSError object, set the value, and stop the method. ... right?
 
I don't understand how you can do something like this in ObjC: gist.github.com/nibroc/fc99e8ef6586cb08b196
At least how you can do it without a cascade of error checking or some goto hackery.
 
10:24 PM
@nhgrif No, you don't have to create the exxcepion object for errors happening in called methods
 
...
NSError *error;
[someObject doStuff:stuff error:&error];
That's all you do. You're creating a memory address to check later.
 
0
Q: Ways to express proc inside a method

James Gibson WeberInterested in seeing different ways the proc can be expressed inside a method that takes args. This method is meant to be a sort of FizzBuzz that will dynamically replace "Fizz" or "Buzz" as well as the traditional divisors 3 & 5. def fizz_buzz_custom(string_1="Fizz", string_2="Buzz", num_1=3, ...

 
And if you forget it once you can corrupt weeks worth of data
 
So don't write Objective-C as if it were Java and write it as if it's Objective-C?
It's a different approach to error handling.
 
Or well, however long it takes to notice something is off
 
10:28 PM
You guys are used to something different and that's fine.
That doesn't make Objective-C's approach worse--just different.
 
I've done Objective C for 9 months. Maybe I just never grokked ObjC error handling, but in my opinion, it's error handling truly is inferior. As a language over all, I love it. It's a great language. Like all languages though, it has weak points. Error handling is one of them.
It's very C-esque with it's error handling.
And if there's anything 30 years has taught us, C style error handling is terrible.
 
You can still use try-catch blocks in Objective-C.
 
And.... dinner time.
 
But most objective-C stuff doesn't throw exceptions that you should be catching.
 
Right, which is part of the problem. It means that you have to explicitly check for errors rather than it be a rather automatic process. If you forget to check for errors from a statement, you can end up with unnoticed errors that can do damage. I'd rather unnoticed errors cause something noticeable.
 
10:31 PM
Also, in a lot of cases, errors are handled via delegate methods.
Which is how errors are handled in my SQL library for Objective-C.
 
That makes sense with async stuff -- not sure if there's really any other way to do it
 
It can be done with sync stuff too.
Not all delegate stuff is async.
For example, tableviews, the most common delegate stuff.
 
Hrmm, yeah.
 
0
Q: Is this a sensible way to throttle duplicate requests in a httpmodule

James SouthI'm writing a method to throttle duplicate requests taking place within multiple HttpModule instances within a web application. Currently I have the following setup: // Container for semaphores private static readonly ConcurrentDictionary<string, SemaphoreSlim> SemaphoreSlims = new ConcurrentD...

 
I've just reviewed one of Loki's old questions. :-P
(I know it won't help him, but reviews are for everyone to benefit from.)
 
10:44 PM
@Corbin I know what you mean. Sometimes, you just want to take a small break :)
 
Yeah. It just becomes an issue of where certain things rank in the relatively small amount of free time I do have. Unfortunately, CR swings between ranked #1 and very last. Burnout and breaks tend to dictate that :p.
 
I'm actually procrastinating to play games, with CR right in front of me. O_O
 
Nobody's perfect.
 
lol
 
Good thing you're not a moderator, then. ;-) Burnout will eventually happen, but luckily it takes much longer on CR.
 
10:56 PM
3
Q: Accelerate OpenGL 2D on Python3

user2286564I used OpenGL to draw about 20 circles. Each circle has 2 lines, ~10 segments, and all of them have different colors and lenght. FPS ~=4. How can I do this faster? I am using Python 3 on Ubuntu. class ScreenOpenGL(Screen): def __init__(self,layers,layers_lock): """ Инициализирует экран и з...

Accelerating OpenGL does sound a little bit tough.
Also, I can't read cyrillic.
 
I don't really get burnt out in the sense "omg I can't do anymore CR ever again!"; I just have interest come and go.
But yeah, I could never maintain a high enough baseline interest to be a mod haha
Nor do I have the people skills :p.
 
That's more or less why I wasn't active for some months.
 
I think CR tends to be a fairly burnout-y site :/. I'm glad you're back though. I'd noticed you around when I've been creeping the past few weeks, and it's always nice to see lots of high quality C++ activity :D.
 
I mostly post the same things though. I can help improving the style, but not really the rest. I am impressed that @Jamal still manages to give the same advice several times a week without being bored.
 
Idk how anyone does it. Sometimes it's what I fear may be the downfall of CR. Nothing is really new content. It's just different incarnations of the same 10 problems over and over again.
Then again, that's all SO is, and it does very well.... :p
 
11:03 PM
But SO can "close as duplicate" while each review here is a little bit different.
 
@Morwenn Trust me, it bothers me a bit, but I just can't review anything too advanced yet. Plus, this is different from SO in that reviewing "easy" code is not quite considered rep-whoring.
 
Yeah. I hate that 99% of reviews here can really be summed up as "go read Effective C++"
but such is the nature of the site I suppose
 
... I should really read that book.
 
I still need to finish my copy.
 
If you follow blogs for any of the C++ people, you probably already know most of it
I got it recently
and was shocked how much of it is already on Meyer's blog
or Herb Sutter's
But i suppose it is quite old at this point
 
11:05 PM
I'm still not sure if I should also get Effective STL.
 
Considering that I read the articles shared by isocpp.org, I guess that I already know what I should know?
 
Hrmmm.... I don't know for sure, but yeah, probably.
 
Well, Scott Meyers summed up the contents of Effective C++11, and it seems that I already know most of the idioms.
 
Yeah, I got the early version of Effective Modern C++ since I was curious and wanted to have a centralized reference rather than searching around for blog posts.
So far I've been through about 3/4 of it and learned nothing new :/
But, there have been a few things that have been enlightening.
 
@Morwenn Ooooooo... bookmarked.
 
11:08 PM
Just not new.
 
I have a lot to learn about threading though.
 
that's actually the part of the book i haven't gotten to yet :)
hopefully i pick up a few things
I actually picked up a few things in the universal references stuff too. It was nice to have one coherent explanation from beginning to end of rvalue references and all of their implications, uses and pitfalls instead of jumping from blog post to blog post across 6 months in time.
 
There was one good blog post if I remember well...
The first one when I google "c++ rvalue references" actually...
But I learnt them by making mistakes first. There are really some tricky things.
 
Hrmm, that actually looks vaguely familiar now... But not sure if I've read the whole thing before.
And yeah, some of the rvalue reference stuff is really non-intuitive.
It's unfortunate that rvalue references made C++ much, much more powerful but also added a very large mental overhead to truly knowing the language.
 
Especially the difference between rvalue references and universal references.
 
11:13 PM
(And C++ is already pretty damn hard)
 
I have to agree.
 
It's a bit weird to me how many people think they know C++ when really they know maybe 5% of it. I don't think many other languages have the same problem, at least not to the same extent.
 
The more you learn about C++, the more you realize you know nothing.
 
And rvalue references moved everyone's knowledge back about 30%
Yeah, definitely.
 
XD
 
11:16 PM
I go through weird stages where I start to think I'm getting pretty good with C++, then I realize there's like a dozen more things I've never even heard of or used.
lol
 
And the subtle trickery of auto&& was a pain to remember.
 
yeah
i have to always remind myself that auto is type deduction
which sounds absurd... but... makes a huge difference
 
And that day were you realize that you have no idea what a facet is and how the streams library works.
 
and for some reason it doesnt naturally click in my head
Hah. I currently have no idea on either of those two :p
 
Actually, I know that I don't know. That's already good enough.
 
11:19 PM
That's true. It's an infinitely better start than someone who thinks they know things they don't (which once again is incredibly, disturbingly common with C++).
 
Anyway, I am getting sleepy. See you later! :)
 
Night :p
 
Many C++ beginners are actually using C and one or two C++ features.
6
 
0
Q: How does this code even work?

Taylah GrayI noticed this very interesting entry on IOCCC (implementing a 8086 compatible PC in a few lines of C code) and I'm struggling to wrap my head around how it works: http://ioccc.org/2013/cable3/cable3.c From the description it says: This entry weighs in at a magical 4043 bytes (8086 nibbles, 28...

 
That has to do with how C++ is taught in schools: mainly as an extension of C.
 
11:21 PM
Yeah :/.
 
I think this could make a good site blog entry as well. SE, especially CR, has helped me realize this.
 
@CaptainObvious off topic?
 
Yup
 
But she's cute!
 
But this is the Internet, so she may just be a dog. :P
 
11:27 PM
She could be a cute dog. =)
 
lol
Or it could be Bjarne Stroustrup.
 
Bjarnicles hates C, so he wouldn't ask questions about it.
 
Oh yeah. Why was I thinking it was C++...
 
Did any of you by an chance check out the C file that she/he/dog attached? Pretty crazy golf code.
 
It was also cross-posted on SO and Code Golf, with an answer accepted on SO.
Interesting. I did not know that you can earn Mortarboard on a Meta site.
 
11:56 PM
Well, if you were paying attention a couple of days ago .....
 
To what?
 
2 days ago, by rolfl
and.... You've earned the "Mortarboard" badge (Earned at least 200 reputation (the daily maximum) in a single day). (on Code Review Meta).
 
00:00 - 20:0020:00 - 00:00

« first day (456 days earlier)      last day (3563 days later) »