Anonymous user
Talk:Deepcopy: Difference between revisions
→Provide reference and source: candidate description changes
(→Tcl) |
(→Provide reference and source: candidate description changes) |
||
Line 5:
: As a general rule, I think it is better not to specify in such detail, and let the example authors document their examples as they see fit. (Or perhaps for this case, “Explain how the deep copy works, such as by showing its source.” — make it into another point-that-must-be-covered.) —[[User:Kevin Reid|Kevin Reid]] 14:10, 18 July 2011 (UTC)
Mod Candidate#1
: Original text: "This can be via a built-in procedure or operator, a function from a common library (provide reference and source if it is written in the language), or a procedure (show source)."
: Updated text: This can be via a built-in procedure or operator, a function from a common library (provide reference/link), or a procedure written in the language itself.
:* If this is written in the language, describe or show how this works (possibly by including source if copyrights allow or by other means).
: --[[User:Dgamey|Dgamey]] 01:28, 19 July 2011 (UTC)
Mod Candidate#2 (per Kevin Reed's comments below):
: Original text: Demonstrate how your language handles complete copying, often referred to as deep copying, of complex data structures.
: Updated text (append to above): Deepcopying is normally required where structures are mutable and to ensure that independent copies can be manipulated without side-effect.
: --[[User:Dgamey|Dgamey]] 01:28, 19 July 2011 (UTC)
==Tcl==
| |||