Theory and Justification
From APIDesign
(Difference between revisions)
(New page: "In that case, developers using it will create a feeling way different that conflicts with the architect's intentions." does not make such sense. --~~~~) |
|||
| Line 4: | Line 4: | ||
--[[User:JesseGlick|JesseGlick]] 03:44, 25 March 2008 (UTC) | --[[User:JesseGlick|JesseGlick]] 03:44, 25 March 2008 (UTC) | ||
| + | |||
| + | * There are no page numbers on this section | ||
| + | * Punc: Para 2: Delete comma after API - it's not necessary | ||
| + | * Content: Para 2: This is the perfect place to hint at some counter-examples of consistency in Java... unfortunately, I'm having some trouble coming up with examples right now! | ||
| + | * Spacing: Para "A Stable API" - is there an extra space before "API is stable" in italics? | ||
| + | * References: Para "If you believe" - "Part __" missing Part numbers (twice). | ||
| + | --[[User:Dmkoelle|Dmkoelle]] 20:50, 26 March 2008 (UTC) | ||
Revision as of 20:50, 26 March 2008
"In that case, developers using it will create a feeling way different that conflicts with the architect's intentions." does not make such sense.
--JesseGlick 03:44, 25 March 2008 (UTC)
- There are no page numbers on this section
- Punc: Para 2: Delete comma after API - it's not necessary
- Content: Para 2: This is the perfect place to hint at some counter-examples of consistency in Java... unfortunately, I'm having some trouble coming up with examples right now!
- Spacing: Para "A Stable API" - is there an extra space before "API is stable" in italics?
- References: Para "If you believe" - "Part __" missing Part numbers (twice).
--Dmkoelle 20:50, 26 March 2008 (UTC)
Follow
