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.
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?
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.
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.
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.
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.
sinteresting project and good work.
Actually, I tried to compile the AdMob example with Qt5.3 under Win8.1 and got the following build error:
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
But why would we use 60 bytes for padding?
BRL is falling too, so thanks for the app.