JaroslavTulach at 19:12, 24 April 2009

JaroslavTulach — Fri, 24 Apr 2009 19:12:51 GMT

←Older revision		Revision as of 19:12, 24 April 2009
Line 3:		Line 3:
	I almost want a list of things I have to be on guard against, then check each design option against them. I almost want a flowchart. I must be a programmer.		I almost want a list of things I have to be on guard against, then check each design option against them. I almost want a flowchart. I must be a programmer.
	--[[Special:Contributions/68.57.243.125\|68.57.243.125]] 11:36, 21 April 2009 (UTC)bassy bassy good dog!		--[[Special:Contributions/68.57.243.125\|68.57.243.125]] 11:36, 21 April 2009 (UTC)bassy bassy good dog!
		+
		+	Thanks for your comment. As regards the checklist, I've just created [[APIAntiPatterns]] category. But it will take a while until it is filled.
		+
		+	There is nothing bad on using [[Java]] interfaces in certain situations. Their biggest advantage is [[ClearDefinitionOfVersion]]. Their biggest restriction is inability to evolve and add new methods into them. As such I don't recommend common use of interfaces for [[ClientAPI]], but I use them a lot in [[ProviderAPI]].
		+
		+	--[[User:JaroslavTulach\|JaroslavTulach]] 19:12, 24 April 2009 (UTC)

68.57.243.125: New page: This is great, thanks for taking the time to write it ! I will study it and reply if I can think of anything constructive to contribute.
One thing that has tended to confuse me in ...

68.57.243.125 — Tue, 21 Apr 2009 11:36:16 GMT

New page: This is great, thanks for taking the time to write it ! I will study it and reply if I can think of anything constructive to contribute. One thing that has tended to confuse me in ...

New page

This is great, thanks for taking the time to write it ! I will study it and reply if I can think of anything constructive to contribute. 
One thing that has tended to confuse me in the book is there are multiple reasons, as you point out, why interfaces might cause API writer's headaches, and I tend to mix them up. Are interfaces trouble because they are public and therefore become stars? That's an evolution problem. What bad things can happen when you use interfaces from an evolutionary standpoint again? Are they trouble because the API writer's intent is not clear? That's a communication problem. What are my other options again? 
I almost want a list of things I have to be on guard against, then check each design option against them. I almost want a flowchart. I must be a programmer.
--[[Special:Contributions/68.57.243.125|68.57.243.125]] 11:36, 21 April 2009 (UTC)bassy bassy good dog!

Talk:ImplementOnlyInterface - Revision history

JaroslavTulach at 19:12, 24 April 2009

68.57.243.125: New page: This is great, thanks for taking the time to write it ! I will study it and reply if I can think of anything constructive to contribute. One thing that has tended to confuse me in ...

68.57.243.125: New page: This is great, thanks for taking the time to write it ! I will study it and reply if I can think of anything constructive to contribute.
One thing that has tended to confuse me in ...