Talk:Blogs
From APIDesign
(Comment provided by iststghw - via ArticleComments extension) |
(Comment provided by hstbbedn - via ArticleComments extension) |
||
| Line 43: | Line 43: | ||
--[http://rrsoti.com/ iststghw] 01:34, 29 October 2011 (CEST) | --[http://rrsoti.com/ iststghw] 01:34, 29 October 2011 (CEST) | ||
| + | </div> | ||
| + | == hstbbedn said ... == | ||
| + | |||
| + | <div class='commentBlock'> | ||
| + | hstbbedn | ||
| + | |||
| + | --[http://giptgi.com/ hstbbedn] 01:35, 29 October 2011 (CEST) | ||
</div> | </div> | ||
Revision as of 23:35, 28 October 2011
Comments on Blogs
Contents |
Casper Bang said ...
Interesting question. My guess is that I never had problems following suggestions related to usage of exceptions provided by others. I used exceptions in many ways in my APIs and as far as I can tell they evolve like other classes. The other area is usage of exceptions in own method definitions and here one needs to optimize for the understanding of users of the API. That is vague statement, but I do not have any practical advices ready now. I'll think about it in future. Thanks for your comment.
--JaroslavTulach 14:48, 5 September 2008 (UTC)
"yet it seems that there is no language in the world that would make this easy" Is this really a language problem? I think it's a tool and communication problem. You want a tool that communicates to you that the change you're about to make will result in incompatibilities with your previous consumers. We can even imagine that they could be notified that you are doing this, which might permit them to notify their own consumers in some way. The gnarliest problem here is illustrated in this scenario- imagine you used this tool and it notified the distributed developers and happily enough they all got the memo. How are they supposed to communicate anything so technical as "you can't download the latest version of such and such library because your program that you bought from us (remember us?) will stop working properly".
A lot of interesting programming problems aren't really programming problems, they're user interface problems. Almost all of the API book is an attempt to deal with limitations on our ability to process information. The reason that's germane is because a lot of problems that have information processing limitations as their root cause, as opposed to say limitations in our ability to measure the position of a particle or limitations in the strength of materials, can be dealt with through the magic of user interface engineering.
Continued on.... <a href="http://lambda-the-ultimate.org/node/2950"> Lambda the Ultimate </a>
Ornabeame said ...
Hello I do not agree with all of you! http://soundcloud.com/groups/buy-doxycycline-1 Buy Doxycycline, , http://en.gravatar.com/mdfedorova Buy Plan B Online, http://mdfedorova.webgarden.com/ Buy Cheap Amoxil Online
--Ornabeame 15:35, 15 October 2011 (CEST)
nandrolone said ...
I admit, I have not been on this webpage in a long time… however it was another joy to see It is such an important topic and ignored by so many, even professionals. I thank you to help making people more aware of possible issues.
--nandrolone 12:56, 18 October 2011 (CEST)
iststghw said ...
iststghw
--iststghw 01:34, 29 October 2011 (CEST)
hstbbedn said ...
hstbbedn
--hstbbedn 01:35, 29 October 2011 (CEST)
Follow
I was curious as to know how come, in a book strictly about API design in Java, you do not mention exceptions (particular checked exceptions) and the role they play in documenting assertions vs. hampering versionability. Did you simply think this to be too controversial an issue I wonder?
--Casper Bang 05:17, 5 September 2008 (CEST)