'. '

Talk:Blogs

From APIDesign

(Difference between revisions)
Jump to: navigation, search
(Comment provided by buy anabolics online - via ArticleComments extension)
(Comment provided by DrarCrumn - via ArticleComments extension)
Line 44: Line 44:
--[http://anabolmarket.net/ buy anabolics online] 01:02, 8 April 2011 (CEST)
--[http://anabolmarket.net/ buy anabolics online] 01:02, 8 April 2011 (CEST)
 +
</div>
 +
== DrarCrumn said ... ==
 +
 +
<div class='commentBlock'>
 +
hi, visit my soft blog http://danakern.blog.com/
 +
 +
--[http://qufecoup.blog.com/ DrarCrumn] 13:35, 10 April 2011 (CEST)
</div>
</div>

Revision as of 11:35, 10 April 2011

Comments on Blogs


Contents

Casper Bang said ...

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)

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>

virginiabeachroofing said ...

This is a very interesting site. The content is very informative and I am so glad that I dropped by. Thanks! _________________________________ http://www.aquashieldroofingcorpsite.com

--virginiabeachroofing 03:40, 5 April 2011 (CEST)

siresoobe said ...

cialis without prescription http://trust-pharmacy.com/

--siresoobe 12:45, 5 April 2011 (CEST)

buy anabolics online said ...

Nice info;) Díky za váš čas ...;)

--buy anabolics online 01:02, 8 April 2011 (CEST)

DrarCrumn said ...

hi, visit my soft blog http://danakern.blog.com/

--DrarCrumn 13:35, 10 April 2011 (CEST)

Personal tools
buy