I'm simply asking for the same information cgminer provides, you could can just cut & paste -ck's code to save time. The difficulty of the shares found and the difficulty of best share found is absolutely invaluable information when mining.
edit:
Let me give you an example, I mine RANDOM_DAGGER_COIN on a pool for 24 hours. The pool says I found 0 blocks but the miner says my best share just fell short (300G but I needed 305G). I now know that I'll be able solo mine a block within 24 hours if the network hashrate drops just a bit.
The thing is you see blocks come in groups though, not only will I mine at least 2 blocks in 48 hours (with slightly lower network hashrate) I'll mine 3 then I'll jump back on the pool. If the blocks didn't come in groups then they would be evenly spaced out at predictable intervals i.e. not random.
Ok I understand your point of view. Instead of correct calculations based on target diff and miner speed, you take best share for 24 hours and think that you can reach this target for next 24 hours. It's wrong in general, but I won't argue, your approach can work with some probability. I can add the info you need, but I will have to change all GPU kernels because they don't return share diff, so I won't do it just for you, sorry. Also I think ccminer will not show the best share until you find at least one share, if so, in solo mining it will not show the info you want too. I can make GPU compare diffs of all hashes to find the best and return best value even if this value is less than share target, but I will not do it because it's additional and useless work for GPU.