Why point to your scratchpad, if you can just copy the relevant contents?

Because I use my scratchpad as a categorized index that I change at will so it is up to date. Why litter nodes with reference lists that will be out of date the next time I update my index? :-)

But, since you asked so nicely...

Object-Oriented Perl - Inside-Out Technique

• Re: Where/When is OO useful?
• Re: Tutorial: Introduction to Object-Oriented Programming
• A different OO approach
• Yet Another Perl Object Model (Inside Out Objects)
• Class::InsideOut - yet another riff on inside out objects.
• Threads and fork and CLONE, oh my!
• inside-out objects using arrays?
• Array-based Inside-out Objects with Object::InsideOut
• How to use Inheritance with Inside-Out Classes and Hash Based Classes
• Inside-out objects inheriting from hash-based classes
• Seeking inside-out object implementations
• Anti-inside-out-object-ism
• Overriding bless for inside-out object safety
• Introducing Class::InsideOut

Then why not post it somewhere in a regular node and commit to keeping that updated? (Like my Sites like PerlMonks list.) If you really really don’t want to make a new one for it, keep the list on your home node. Sure, you can update any of your nodes, so technically they’re all equivalent; it’s site-social convention though that the scratchpad is a place where you can stick things intermittently, basically an on-site pastebin for the chatterbox.

Makeshifts last the longest.

Wow, we're way off topic here. Thanks for the title change.

I got started doing it that way because of the "add to pad" function of the personal nodelet. When I read a post that I want to remember for later, I add it to the pad and later go through the pad and categorize them. It never occured to me to go to the trouble of sticking them somewhere else or that people might take issue with it.

Is there a "private" node type that can be created that isn't a new post or a reply to another post (as yours appears to be)? Or maybe I'll just move them to my home node.

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.