|
It's quite nice to have the source code of the api available too.
|
|
|
|
|
ed welch wrote: source code of the api
Looks like two entities got merged in this phrase.
(1) Source Code
(2) API and Heterogeneous Application Interoperability
Wouldn't the division make your stand clear?
Vasudevan Deepak Kumar
Personal Homepage Tech Gossips
A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis Levinson
|
|
|
|
|
Open Source is good. Without that, no progress in the programming world would be possible.
However, the way I see it is that: you don't have time and resources to do everything. So you choose: You either become a programming language developer (in that case having the source code is...neccessary!) or you develop applications based on that language (in that case having the source code is nice, but not so neccessary...).
I belong in the second category. I like to know how things work, so yes - I would look at the source code to learn the inner workings of C++ for example. But wouldn't spend days on that...
|
|
|
|
|
Doesn't matter weither you are an application developer, or not, having the source code is always an advantage.
Sometimes understand to what a function is doing it's easier seeing the code than reading the documentation
Also when debugging you can step into the api functions and see what's going on (that was a part of MFC that I liked)
Extending api functionality is easier too. You can modify the existing source code.
|
|
|
|
|
Vasudevan Deepak K wrote: Heterogeneous Application Interoperability
Holy crap!
|
|
|
|
|
This survey seems to be multiple choice one but there has been no option for 'Text Answers' (Optional Text Answers).
BTW, I was looking out for this to bring in the classic omnipotent and omnipresent CListCtrl .
Vasudevan Deepak Kumar
Personal Homepage Tech Gossips
A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis Levinson
|
|
|
|
|
Multiple choice does not imply free text answer.
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
Wouldn't the following points very much Paradoxical?
1) Compile to native code [no intermediate or byte code]
2) Cross Platform Support
Or if the SDK has to give this feature, its toolset should be really very versatile and rich collection.
Vasudevan Deepak Kumar
Personal Homepage Tech Gossips
A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis Levinson
|
|
|
|
|
Not at all. Programming language features are attributes of the source code after all. For the purposes of this discussion, I don't think the compile/link requirements or target environment are the primary concerns.
For example, look at C++. It satisfies both of the requirements of native code compilation and supporting cross platform development. Compare that to assembly language, which obviously meets the native code constraint, but isn't cross platform capable.
Software Zen: delete this;
|
|
|
|
|
Apart from what Gary says, Eiffel also satisfies both 1 and 2.
Kevin
|
|
|
|
|
Nope, not paradoxical, but rather dependant on industry support (making compilers).
|
|
|
|