comment on

Are you going to call your fork DBIx::Simple::CircularReferences or DBIx::Simple::NeverDestroys?

and tye tried it and saw the problem

What I "saw" was that you should simply stop writing code that destroys the container object if you want to keep using one of the contained objects. But you insist on making a simplistic change to the DBIx::Simple module and not making a trivial change to how you use that module, even after I made it quite clear that your proposed change breaks the lifecycle management of the module.

Unless you proposed a patch that fixed your "bug" without creating circular references, I would make the next "movement on the RT" to close it as "working as designed".

- tye

In reply to Re^5: How should a fork of DBIx::Simple be handled? (selective comprehension) by tye
in thread How should a fork of DBIx::Simple be handled? by metaperl

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.


Come for the quick hacks, stay for the epiphanies.
	PerlMonks