eswangren's comments

eswangren | 13 years ago | on: Sorry Dan Shipper and other coders, you are wrong.

You don't think that some people are simply better suited to tasks that require a high degree of logic than others? Really? I would think that day to day interactions would teach you that much... We're not all born as blank slates with near unlimited potential.

eswangren | 13 years ago | on: The 5-minute Guide to C Pointers

And it is actually somewhat dangerous to cast the return value of malloc. Aside from being redundant it can hide an error on compilers which implement an older version of the standard (not uncommon. Anything pre-C99).

If you forget to include stdlib.h the cast hides the error and malloc will be assume to be a function which returns int. makes for interesting runtime errors.

Never cast the return value of malloc in C, and don't write redundant code. C is not C++.

eswangren | 13 years ago | on: The 5-minute Guide to C Pointers

Just as with pointer arithmetic (because that's what this actually is) you don't multiply by the size of its elements. This:

  array[2]
is the same as this:

  *(array + 2)
The compiler knows what the type of data the pointer refers to and can produce the byte offset itself. Also:

  "...it's always pointing at the first element of the the array"
Eh... an array can degrade into a pointer when needed, but what does the following produce?

  char arr[10];
  ??? x = &arr;
Is "x" a pointer to pointer to char? From your assessment it would seem so, but in reality the type of "x" is

  char (*)[10]
i.e., pointer to array of char 10. An array is an array, and arrays can degrade into pointer types.

eswangren | 13 years ago | on: Anic - Faster than C, Safer than Java, Simpler than *sh

It's not a good idea from any perspective. In my experience, the only people who cram as much logic into as few characters as they possibly can are beginner to intermediate level programmers who are in that awful phase where they think they know a lot more than they do.

eswangren | 13 years ago | on: "Computer Science" is Not Science and "Software Engineering" is Not Engineering

I am first and foremost a software guy, but I work in a systems group. I write hardware device interfaces. I solve problems in the physical world. Motion control, digital imaging, electronics. Many of the problems I solve on a daily basis are problems of physics, yet I solve them (mostly) in software. I think the term "software engineer" applies here. Let's not forget that there are many, many engineers just like me who do not write CRUD and web apps every day.

eswangren | 13 years ago | on: Lessons From Netflix

+1 that was a horrible, horrible UI change. So much so that I wrote them an email just to complain about it. I don't know what they were thinking with that one.

eswangren | 13 years ago | on: Lessons From Netflix

NetflIx doesn't get new releases. I don't care why they don't, but the fact remains that they do not. I cancelled because of this. I really like NetFlix as a company, but the lack of selection kills it for me.

eswangren | 13 years ago

Why did you wrap the word "stealing" in quotes? It's exactly what you would be doing. If you think you'll get away with it then you're too dumb for me to hire anyway.
page 1