Knuckle Cracker Wiki

User Tools

Site Tools

Trace: • getmousescreenpixelposition
prpl:copy_vs_deep_copy

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
prpl:copy_vs_deep_copy [2017/08/30 19:08] – created kajacxprpl:copy_vs_deep_copy [2025/02/14 14:57] (current) – external edit 127.0.0.1
Line 1: Line 1:
 <- [[.:prplreference| PRPL reference]] <- [[.:prplreference#lists|Lists]] <- [[.:prplreference| PRPL reference]] <- [[.:prplreference#lists|Lists]]
  
-=====  CopyList vs DeepCopyList vs "just passing the list"  =====+=====  CopyList vs DeepCopyList vs dup / just passing the list  =====
  
 When you have a list in a variable for example, and you need to use the list in a function for example, you might not know whether to just pass the list into the funtion (<-myList @myFunction), use CopyList (<-myList CopyList @myFunction) or whether to use DeepCopyList (<-myList DeepCopyList @myFunction). In this article, you will learn the benefits and dangers of each. When you have a list in a variable for example, and you need to use the list in a function for example, you might not know whether to just pass the list into the funtion (<-myList @myFunction), use CopyList (<-myList CopyList @myFunction) or whether to use DeepCopyList (<-myList DeepCopyList @myFunction). In this article, you will learn the benefits and dangers of each.
Line 14: Line 14:
 === Sharing list in multiple variables (or on stack) === === Sharing list in multiple variables (or on stack) ===
 Let's start by a quick example with 3 lists and 4 variables: (I have named the lists ListA,B,C so that we can keep track of which variable has which list stored in it) Let's start by a quick example with 3 lists and 4 variables: (I have named the lists ListA,B,C so that we can keep track of which variable has which list stored in it)
-<code>+<code prpl>
 "a,b,c" "," Split ->list1 #ListA "a,b,c" "," Split ->list1 #ListA
 "a,b,c" "," Split ->list2 #ListB "a,b,c" "," Split ->list2 #ListB
Line 28: Line 28:
  
 If we change list1, list3 will be change as well, because it is the same list, just stored inside 2 different variables: If we change list1, list3 will be change as well, because it is the same list, just stored inside 2 different variables:
-<code>+<code prpl>
 <-list1 2 "foo" SetListElement    #ListA <-list1 2 "foo" SetListElement    #ListA
 <-list1 Trace # ["a", "b", "foo"] #ListA <-list1 Trace # ["a", "b", "foo"] #ListA
Line 37: Line 37:
  
 However, if we change //which// list is stored inside the list1 variable, list3 will remain the same: However, if we change //which// list is stored inside the list1 variable, list3 will remain the same:
-<code>+<code prpl>
 <-list4 ->list1                   #ListC <-list4 ->list1                   #ListC
 <-list1 Trace # ["x", "y", "z"]   #ListC <-list1 Trace # ["x", "y", "z"]   #ListC
Line 50: Line 50:
  
 So, what if we didn't want 2 variables sharing the same list, but instead wanted to copy the list from one variable into another so that we can then change eighter list without affecting the other one? Well, that's //exactly// what CopyList is for. It creates a new list, but with the same contents. So, what if we didn't want 2 variables sharing the same list, but instead wanted to copy the list from one variable into another so that we can then change eighter list without affecting the other one? Well, that's //exactly// what CopyList is for. It creates a new list, but with the same contents.
-<code>+<code prpl>
 "x,y,z" "," Split ->list1 "x,y,z" "," Split ->list1
 <-list1 CopyList ->list2 <-list1 CopyList ->list2
prpl/copy_vs_deep_copy.1504120133.txt.gz · Last modified: 2025/02/14 14:56 (external edit)

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki