avatar
I know C :P
avatar
I know C. These really aren't that hard. I would argue that a modern programming language shouldn't require you to memorize such trivia (and I avoid C wherever possible), but it's very much possible.
avatar
Well, just as i suspected. I do not know c.
avatar
Could you show the result of those question? I couldn't believe that. so crazy.!!!
avatar
I don't even know what ECM stands for… And I'm not having luck googling it, any hints?
avatar
wrongs
avatar
uh, gave a few wrongs answers…
avatar
I don't know C!
avatar
Hi,
interesting project and good work.
Actually, I tried to compile the AdMob example with Qt5.3 under Win8.1 and got the following build error:
BUILD FAILED
C:\Android\sdk\tools\ant\build.xml:577: google-play-services_lib resolve to a path with no project.properties file for project C:\projects\build-AdMobQtSample-Android_for_armeabi_v7a_GCC_4_9_Qt_5_4_0-Release\android-build

Do you have any idea, what the system is expecting here? What kind of «project.properties» am I supposed to supply?

Any help is greatly appreciated!

Best,
CBA
avatar
Thank you, John! Checking it out now.
avatar
devnull Joseph Albahari has a series on threading/concurrency (http://www.albahari.com/threading/). It's a wonderfully detailed and laid out series that really goes in-depth. These lock-free/wait-free data structures they are anything but high-level and generally require that you understand a bit about the memory model that's being used.
avatar
Thanks. It makes it a little bit more clear now. You should write an article for newbies like me. Are there any good books (articles?) which would describe lock-free/wait-free concepts on a higher level, without diving into details too much? Most of the blog posts suppose that you already know a lot of low-level stuff. Or maybe I should just start from reading something completely different.
avatar
I don't think the original author is around.
But why would we use 60 bytes for padding?
avatar
should the padding be char[60] instead of 64, since cache line length is 64?
avatar
devnull In this case, lock-free implies that we never block/suspend the execution of the thread/process doing the work. The basic premise is that lock acquisition is expensive. Let's assume you're doing work on a modern OS. That OS will use preemptive multithreading. In that situation a thread may enter a wait state. Effectively going into hibernation. This is not free but generally and probably not your average performance bottleneck. Lock-free/wait-free attempts to minimize this overhead.
avatar
Can someone explain me, what are lock-free data structures? I don't get it.
avatar
Just downloaded your app on 3G, hurray for small app size!
BRL is falling too, so thanks for the app.
avatar
Thanks for the post, it made me realize the importance of a simple fact that I have been ignoring so far.
avatar
Definitely. Devaluation has «helped» the app. I'm sure the author did not try to make any predictions related to the reduction in the value of a currency. At the same time, it's a good lesson to learn — predictions can help you a lot, but they should never be considered as the only way to reach the goal, as any prediction may not come true. As a brief summary, I think it does always make sense to spend at least a little time on analysis, but never expect them to be 100% accurate.
avatar
Thanks. That's not too bad I guess, although it could have taken a long time to get into profit if the app hadn't have reached the top.