Sponsored Content
The Lounge What is on Your Mind? Should We Disable User Profile Visitor Messages? Post 302484659 by Corona688 on Sunday 2nd of January 2011 12:54:50 PM
Old 01-02-2011
I'm still waiting for an example of the mysterious "proper" use of profile comments. Even the benign ones I get would've been better off posted in the thread that provoked them.
 

5 More Discussions You Might Find Interesting

1. AIX

How to disable cd to other folder for a user

How to disable user for cd to some another folders other than his folders. AIX 5L 5.2 Thanks Dilip. (1 Reply)
Discussion started by: Dilippatel
1 Replies

2. Shell Programming and Scripting

User profile

Sorry to I am not familiar with script writing , attach is the /etc/profile in my system , we have limit each user can only have one login in the system . When the user login , if the system found the user have a dead process in the system , the system will confirm the user to kill the previous... (1 Reply)
Discussion started by: ust
1 Replies

3. UNIX for Dummies Questions & Answers

User Profile

Hi Guys, Im really new with this stuff...could anybody help to guide me ...how do i change/edit user profiile ? (2 Replies)
Discussion started by: gagasan_makmur
2 Replies

4. Infrastructure Monitoring

trap in etc/profile and user .profile

Hello I really wonder what's trap in etc/profile and in each user .profile. I try to google for it but I think I have no luck. Mostly hit is SNMP traps which I think it is not the same thing. I want to know ... 1. What's a "trap 2 3" means and are there any other value I can set... (4 Replies)
Discussion started by: Smith
4 Replies

5. Solaris

Disable telnet for a particular user

On Solaris 8 is there anyway to disable telnet for a particular user and not for entire system altogether? I would like the user to retain a shell and so creating a noshell like ftp account is not an option. (14 Replies)
Discussion started by: boshyd
14 Replies
Data::Grove::Visitor(3pm)				User Contributed Perl Documentation				 Data::Grove::Visitor(3pm)

NAME
Data::Grove::Visitor - add visitor/callback methods to Data::Grove objects SYNOPSIS
use Data::Grove::Visitor; @results = $object->accept ($visitor, ...); @results = $object->accept_name ($visitor, ...); @results = $object->children_accept ($visitor, ...); @results = $object->children_accept_name ($visitor, ...); DESCRIPTION
Data::Grove::Visitor adds visitor methods (callbacks) to Data::Grove objects. A ``visitor'' is a class (a package) you write that has methods (subs) corresponding to the objects in the classes being visited. You use the visitor methods by creating an instance of your visitor class, and then calling `"accept($my_visitor)"' on the top-most object you want to visit, that object will in turn call your visitor back with `"visit_OBJECT"', where OBJECT is the type of object. There are several forms of `"accept"'. Simply calling `"accept"' calls your package back using the object type of the object you are visiting. Calling `"accept_name"' on an element object calls you back with `"visit_name_NAME"' where NAME is the tag name of the element, on all other objects it's as if you called `"accept"'. All of the forms of `"accept"' return a concatenated list of the result of all `"visit"' methods. `"children_accept"' calls `"accept"' on each of the children of the element. This is generally used in element callbacks to recurse down into the element's children, you don't need to get the element's contents and call `"accept"' on each item. `"children_accept_name"' does the same but calling `"accept_name"' on each of the children. `"attr_accept"' calls `"accept"' on each of the objects in the named attribute. Refer to the documentation of the classes you are visiting (XML::Grove, etc.) for the type names (`"element"', `"document"', etc.) of the objects it implements. RESERVED NAMES
The hash keys `"Contents"' and `"Name"' are used to indicate objects with children (for `"children_accept"') and named objects (for `"accept_name"'). NOTES
These are random ideas that haven't been implemented yet: o Several objects fall into subclasses, or you may want to be able to subclass a visited object and still be able to tell the difference. In SGML::Grove I had used the package name in the callback (`"visit_SGML_Element"') instead of a generic name (`"visit_element"'). The idea here would be to try calling `"visit_PACKAGE"' with the most specific class first, then try superclasses, and lastly to try the generic. AUTHOR
Ken MacLeod, ken@bitsko.slc.ut.us SEE ALSO
perl(1), Data::Grove Extensible Markup Language (XML) <http://www.w3c.org/XML> perl v5.10.1 2003-10-21 Data::Grove::Visitor(3pm)
All times are GMT -4. The time now is 08:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy