Talk:structural pattern

From Wiktionary, the free dictionary
Latest comment: 11 years ago by Liliana-60 in topic Deletion discussion
Jump to navigation Jump to search

Deletion discussion

[edit]

"A design pattern that eases the design by identifying a simple way to realize relationships between entities" i.e. a pattern which provides structure. Furius (talk) 00:36, 2 December 2012 (UTC)Reply

Not any pattern, a design pattern. Keep. DAVilla 12:28, 2 December 2012 (UTC)Reply
Then that meaning ought to be stored at pattern (an extension of meaning one point one, perhaps). Because anything at all can have a design pattern behind it - w:Category:Software_design_patterns contains 83 different types of software pattern, so far. The meanings of all of them are deductable from their first component - and when one can't do so from that component's wiktionary entry, that reflects the need for a more technical definition at the entry for the first term. All of them have the same meaning in computer science regardless of whether they are a pattern or not. Furius (talk) 21:23, 2 December 2012 (UTC)Reply
Keep this, as it is a term of a special kind of design pattern. --Sae1962 (talk) 12:55, 7 January 2013 (UTC)Reply
Delete. Clearly not a term, but a two-word phrase. Note that structural patterns are also called structural design patterns. —RuakhTALK 04:21, 3 February 2013 (UTC)Reply
Also, deleted as copyvio, but that's neither here nor there, since of course this discussion could conclude that the entry can be recreated without the copyvio. —RuakhTALK 04:34, 3 February 2013 (UTC)Reply
Discussion restored. This was archived as having failed by a non-admin; clearly it has not, as the entry was deleted for reasons unrelated to the merits of the term, and a clear consensus on the merits of the term has not been reached. bd2412 T 16:28, 24 February 2013 (UTC)Reply
Keep per Sae1962: it’s the name of a specific class of design patterns. — Ungoliant (Falai) 02:18, 1 March 2013 (UTC)Reply

closed. The entry is gone, there's no use in discussing whether it should be kept. First create the entry, then RFD - not the other way around. -- Liliana 16:09, 29 April 2013 (UTC)Reply