comment on

1) I'm not sure what you mean by 'class data'. Every SPOPS class stores its configuration in a hashref accessible with $class->CONFIG, and the values in that hashref can be any normal Perl scalar (hashref, arrayref, etc.)

If you mean 'instance data', then that's a different matter. Serializing hashrefs and arrayrefs to a database is nontrivial, although the SPOPS::LDAP implementation does this fairly well.

2) You can define one or more classes in 'code class' whose methods get read into the generated class at initialization.

3) If you've downloaded the SPOPS source, check out the 'eg/' directory for a number of examples (see the README file there for pointers). The documentation (also web accessible) has a number of examples scattered throughout as well.

Also, feel free to post questions to the openinteract-help mailing list (that's where SPOPS is supported).

Chris
M-x auto-bs-mode

In reply to Re: SPOPS Question by lachoy
in thread SPOPS Question by set_uk

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


P is for Practical
	PerlMonks