There is not much more that I am thinking that hasn't already been said, so I am going to make this short and simple. Nathan, in regards to georger.araujo's reply,
you state "You quoted me on what i've learnt on c++ but yet you ask me questions on what i havent' learnt." Plain and simple -- if you cannot understand any of these basic questions (especially the one about the destructor, which you should be able to guesstimate an answer to), you need to go back and review "basic" concepts again. I don't mean to discourage you but the cold reality is that this field takes a lot of time and dedication (which you have not/are not putting in) and problem solving skills (which based on your other posts about Google, you show a lack of).
yet to say that later it will be harder, really when you learn language and are ready to do some more graphics and other
teh api details etc, more code - it is harder not easier
(though some things are easier, for example most of the compiler or linker errors stops to be scary ;/ this is an advantage, but other things came harder)
(htc wildfire) it seems slow, I used iphone 3gs years ago
(it seem faster, but both are too small.
Note that the Wildfire was a low end phone when it was released. The nice thing now though is that even the low end Android phones are looking good enough for most people (e.g., Moto G).
yes i know i build a cheaper phone avaliable and it was worth the prize imo, (as a music player and internet checker if need) it is also lookink ok, but never saw a pleasurable dynamic app on this - all aps (though i was not testing to much ) have something i can call (maybe wrong) 'java feeling' - even 8bit machines was responsive etc and here it is more sluggish (esp input seem to have a delay) (but do not matter, - maybe im even wrong a bit - i am not writing apps for that (yet, maybe i will but prefer just windows programming) so i does not doing test and it does not matter a crucial point for me