<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Aug 2, 2016 at 5:03 PM, Joseph Alotta <span dir="ltr"><<a href="mailto:joseph.alotta@gmail.com" target="_blank">joseph.alotta@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Greetings,<br>
<br>
I want to add a method to the Array class.<br>
<br>
#(‘abc’ ‘def’) join => ‘abcdef’<br>
<br>
#(‘abc’ ‘def’) join: $/ => ‘abc/def’<br>
<br>
I am afraid that if I add it to Array directly, it will get lost in a new update. I want to keep it in my project area.<br>
<br>
In ruby, this is called a “mix in”.<br>
<br>
How can I do this?<br></blockquote><div> </div><div>Firstly, these methods exist already. They are defined in SequencableCollection, a superclass of Array, so Array inherits them:</div><div><br></div><div><div>#('abc' 'def') join => 'abcdef'</div><div><br></div><div>#('abc' 'def') joinSeparatedBy: '/' => 'abc/def'</div></div><div><br></div><div>Secondly, if you wanted to add these (or other methods), they would not be lost by updating. That is, unless the update specifically includes a method of the same name in the same class. Updating only adds and removes methods, it doesn't "reset" the whole class.</div><div><br></div><div>Thirdly, to keep these "extension methods" in your own package, put them in a method category that starts with an asterisk followed by your package name. That is, if your Monticello package is named "Foo-Bar", then put your "mix in" Array methods into the category "*foo-bar" which will mark them as belonging to your package, not the package the Array class is in. The extension methods will be stored and loaded with your package.</div><div><br></div><div>Have fun!</div><div><br></div><div>- Bert -</div><div><br></div></div></div></div>