Talk:Copy-and-paste programming
oi! I like package Util. where else do you stick stalwarts like MakeStringBlankIfNull() and AddPI() ??
this page contains too many perl specific references. the code examples should be rewritten in pseudo-code and the perl package references should be dropped
sweeping changes
While the Perl Design Patterns Books is a great resource, this article reproduced from it is not encyclopaedic. The article is very well written and well suited for a book on Perl Design Patterns, but it's next to useless as an encyclopaedia entry on a programming phenomenon. A fine example of cut and paste article writing!
I have replaced the article with a basic start on actually describing cut and paste programming, rather the in depth discussion of why it it's wrong to do it in Perl (which is what this article used to be).
Still wrong?
"However, adherents of object oriented methodologies claim that this form of programming is still wrong."
It may be wrong and that all code should be always completely different from something else, but most languages have certain things built into them that force you to use the same line of code as a previous situation, such as: public void actionPerformed(ActionEvent e)
You cannot avoid writing this line of code in Java in certain situations. 2 cents.
also known as: "bug & Paste" or "copy bug"
merge recommendation
Recommend Plug and Play modding content be merged into this article, provided adequate referencing is provided. Doesn't seem to be a distinctive enough practice for its own article Bwithh Join Up! See the World! 03:52, 11 February 2007 (UTC)