Talk:Abstraction inversion

message: What about the Facade pattern? (Originally asked by Wlievens on  2004-05-16 12:12:29, linked by PJTraill 01:04, 6 December 2005 (UTC)
thread_title:  Facade pattern? 

message: The enthymeme (syllogism with an unstated premise - PJTraill 23:50, 26 February 2006 (UTC)
replies: text: I agree that the whole thing is dubious, and I hope that the remarks on difficulties recognising it suggest as much, but I have a feeling there is something in it, and it would be useful to disentangle the whole thing. Other articles I have found on the internet have not been any clearer. PJTraill 23:45, 26 February 2006 (UTC)
thread_title:  Abstraction, and what constitutes abstraction inversion 

message: I hope that my latest series of edits to this article is useful:
it is the result of a fair amount of googling, but it may need some restructuring.
I feel at any rate that it is becoming clearer what abstraction inversion is really about,
in particular the problem of exposing too weak interfaces makes much more sense to me
than too simple interfaces.
It also seems to me that we should try to develop a standard structure for anti-pattern articles, something like:
* description
* symptoms / recognition
* ill-effects
* cure
* examples from the real world
* a worked example, with code
* links
PJTraill 02:42, 27 February 2006 (UTC)
thread_title:  I hope usefully extended, standard anti-pattern structure 

message: Some of the examples in the "Examples" section are debatable at best, just plain wrong at worst.
* I'm not really sure why the author thinks that Java's Runnable.run interface is an abstraction inversion. 
* The point about functors in the STL in C++ is wrong, assuming I'm understanding it properly.  The STL specifically allows function pointers to be used as functors, so there's generally no need to create a new class (unless you need multiple instances for some reason).
* The microkernel argument is a bit controversial, and the description does not explain the reason it is thought to be an abstraction inversion (the reader would have to actually read the cited sources to find that out).
* The Scheme example is useless to any reader that is not intimately familiar with Scheme.
* Likewise, the Subversion example does not provide any value to a reader that is not familiar with the implementation details of Subversion, since none are provided.
The other examples seem relatively reasonable.  However, I think a more concrete example (perhaps including actual code or at least pseudo-code) for this would be extremely helpful to readers.
REggert (talk) 20:59, 17 January 2008 (UTC)
thread_title:  Bad Examples 

message: Most examples are still bad as of 2015-01-27. They seem opinionated and poorly supported. It's very hard to understand, from this article and its examples, exactly what Abstraction Inversion is, and how it differs from plain Abstraction. This is a very poor article. 200.0.230.235 (talk) 15:48, 27 January 2015 (UTC)
thread_title:  Examples still bad 

message: Along the lines of the example regarding relational databases with weak query interfaces, it might be interesting to cite the Wikipedia itself as a similar case in point.  — Preceding unsigned comment added by 129.89.10.146 (talk) 00:35, 27 February 2014 (UTC)
thread_title:  Ironic Examples 

message: At work we use the Eclipse platform. Often when I have the wish to implement the same functionality in my plugin, i run into the problem that the available code cannot be reused because a required methods is marked as private. If it were, one could simply overwritten or call it from a subclass. This leads to copy & paste programming. The interessting thing on that is that this is mentioned in the book "Contributing to Eclipse: Principles, Patterns, and Plug-Ins: Principles, Patterns and Plugins (Eclipse Series)" as normal. I suggest to add Eclipse as an example.  —Preceding unsigned comment added by 84.159.57.133 (talk) 04:59, 14 May 2008 (UTC)
thread_title:  Using Private-Access-Modifier instead of Protected