Re: Plagiarism

"Noons" <wizofoz2k_at_yahoo.com.au.nospam> wrote in message news:<3eef3b89$1$9355$afc38c87_at_news.optusnet.com.au>...
> "Mark D Powell" <Mark.Powell_at_eds.com> wrote in message
> news:2687bb95.0306170542.5259bb9a_at_posting.google.com...
> >
> > Nuno, but how else do you get Oracle to recognize that the SQL is
> > identical and get code sharing unless you cut and paste? 8-D
>
> :D
> Does that cover PL/SQL as well?
>
> >
> > I think that it all depends on the circumstances of the code use.
>
>
> Well, it can't be more circumstantial
> than a PL/SQL procedure where even the comments
> are mine...

Is this code "written" by someone you work with or was it out in the world, perhaps posted? Within a job site code reuse is a valid use. Rewritting what has already been written is wasteful. Documenting where code is common to other programs/modules is good practice. Crediting the original programmer is courteous but not necessarily required after all the employer owns the code.

I have seen entire programs basically copied with just a few minor modifications made and no mention of the original programmer. This was not considered improper, but was considered good practice as the program was written quicker and if it failed the copying progammer got the call, not the original source of the code.

How fair "stealing" code is depends on the circumstances which you have not filled in. At least they recognized good code.

• Mark D Powell --

When I find good examples I usually record where I found them, but Received on Tue Jun 17 2003 - 19:11:46 CDT