Hi José, you are getting a very good Karma ;)
That's the way i choosed to tell you "thank you" for the time you spend helping people here and there...
And to express my gratitude for all the hard work you are doing in this forum.
Muchos gracias !
...
Thank you. It has increased quickly after making the editor, the browser and the headers more visible, and also after posting the headers for Cairo.
I'm also going to make available a reference guide to GDI, showing both the C and PB syntaxes. Hope that these reference guides will help to lose the fear to the Windows API.
You got 10 applaud from me ;D
QuoteThe fear to the Windows API
this is the result of desinformation ::)
Ah! That explains it :)
Quote from: Patrice Terrier on April 11, 2009, 07:46:13 PM
You got 10 applaud from me ;D
QuoteThe fear to the Windows API
this is the result of desinformation ::)
This is my mission for 2009. I am sick and tired of the spreading of fear regarding the Windows API. Once FireFly 3 is released, all efforts will be centred on teaching users to finally move to Windows API and drop all of the other hacks that are nothing but crutches for them. Why people use DDT and other libraries is beyond me. They are missing out on so much freedom. :)
Microsoft is also 90% responsible of this situation with DotNET.
For example, let see the word "Unmanaged" code, is not that funny?
In my case i would say: i manage "MYSELF" 100% of my code, because I AM the programmer!
Or speaking of UNSAFE code...
Bad programmers have always been unsafe, trying to hide them what is going on under the hood, doesn't make them SAFE programmers.
And learning how to use pointers is the core meat of good programming when using the "flat" API.
History teach us, that keeping the mass in the ignorance has always been used to protect privileges ;)
...
>They are missing out on so much freedom.
*A lot* simply don't care, they don't not much more.
PB is *simple* since it produces something they understand, a single exe.
Currently i find the PB compiler lacks IEnum, native support for visual ActiveX, OLE container and static linking.
For the rest it would be ok (a better IDE as VS IDE maybe??).
M$ does not care about you "the programmer".
You (the programmer) are just a necessary companion that need to jump on the car of .Net
And the car ( .Net ) will bring your where M$ wants you to go: 360 degree "managed"
And when all the world will be "managed", M$ will also remove the "car" because at that time we (or our nephew) will be inside a bubble whose horizons will be undefined and unknown.
End of the story (till the next Matrix reborn)
Eros.
PS: I know, I know, you are asking: what f* has smoked this one? Nothing! ;D That's the problem!
100% quoted and even more.Quote from: Patrice Terrier on April 11, 2009, 06:31:27 PM
Hi José, you are getting a very good Karma ;)
That's the way i choosed to tell you "thank you" for the time you spend helping people here and there...
And to express my gratitude for all the hard work you are doing in this forum.
Muchos gracias !
...
Quote
For example, let see the word "Unmanaged" code, is not that funny?
A better word would be "mismanaged" code :)
Quote
Or speaking of UNSAFE code...
What could be more unsafe that letting M$ to generate the code for you?
Quote
Currently i find the PB compiler lacks IEnum, native support for visual ActiveX, OLE container and static linking.
To enumerate collections, you can use the IEnumVARIANT interface, that is what FOR...EACH uses.
My wish number one is native unicode support.