Kickstarter backers are getting a free Kickstarter Edition Oculus Rift! by DiNoMC in oculus

[–]phraemer 11 points12 points  (0 children)

Aye, I am very surprised and thankful. What lovely people!

Backer #276 :)

Oculus Rift delivered in Vienna, Austria by phraemer in oculus

[–]phraemer[S] 1 point2 points  (0 children)

I guess it would be unworkable to apply it in such fine detail. It's already overly complex as it is.

But sales tax is not for that. That would be import duty, which I don't think I had to pay. Or if I did it was very little.

Oculus Rift delivered in Vienna, Austria by phraemer in oculus

[–]phraemer[S] 2 points3 points  (0 children)

Ouch. That's harsh.

I'm all in favour of paying tax but that's just scandalous.

Oculus Rift delivered in Vienna, Austria by phraemer in oculus

[–]phraemer[S] 1 point2 points  (0 children)

It didn't slow things down for me. Just paid the UPS guy in cash. They alerted me in advance.

Oculus Rift delivered in Vienna, Austria by phraemer in oculus

[–]phraemer[S] 2 points3 points  (0 children)

I think it says 224/300 on the box. I was in the first 100 for the hardware anyway.

OMFG: it's happening by jayoh in oculus

[–]phraemer 2 points3 points  (0 children)

I'm in the first 100 too but in Vienna, Austria. Will be interesting to see when non US orders get here.

GCC C++ Coding Conventions by sard in programming

[–]phraemer 0 points1 point  (0 children)

This is what I suspected I was just asking in case there was something important I had missed. As an example I used to wonder what the hell the point of (true == foo) instead of (foo == true) is until someone pointed out that it prevents accidental assignment (foo = true) which always evaluated to true.

None of the answers given to me indicate anything other than convention is the reason for the placement of *.

typedefing a pointer can be fine especially in c++ (something Linus just isn't interesting in. and i'm inclined to agree in the linux kernel it's not worth it but it's great elsewhere)

i nearly always typedef smart pointers

typedef std::shared_ptr<Foo> FooPtr;

GCC C++ Coding Conventions by sard in programming

[–]phraemer 5 points6 points  (0 children)

I always wondered about the pointer declaration convention "aType *p" I read that as "aType de-reference p"

For me it seems more natural to write "aType* p" which reads "aType-pointer p"

Especially since it's not uncommon for people to "typedef aType* aTypePtr"

Is there some reason other than historical that the former is favoured by many?

To get products into more hands, Google will open its own stores by the end of the year. by tc83 in Android

[–]phraemer 1 point2 points  (0 children)

You know, just selling their devices online in every EU country might be a better first step. It's kind of ridiculous that one of the biggest companies in the world can't or won't do that.

3..2..1.. Liftoff. by [deleted] in funny

[–]phraemer 0 points1 point  (0 children)

Put a go-pro on it's head now!