> Prove it.
That's the hardest thing, it's impossible to prove that something
doesn't contain somewhat. You couldn't prove that the God doesn't exist,
but if you find him - you can prove that. You can't prove that linux
kernel, mojolicious etc.. have no bugs, but if you find a bug - you can
prove that it contains it. You event can't prove that you don't have 55
cents right now (maybe you're hiding it in the pocket), but if you have
55 cent coin - you can prove it just showing it.
So ask yourself can you write some code where IOC prevents leaks, while
a simple attribute doesn't with the same code? Because I'm telling that
you can't do that and using IOC just a wasting of lines of code.
But give me a few minutes. Maybe now I know why Dan Book misunderstand
the definition if circ.refs and show him an example he is expecting for
>Because a circular reference is when a reference to an object is
stored in itself. When they are stored outside the object it is
impossible for that to happen by definition.
Now UR talking about the subject. That's good. You didn't provide a code
but at least I can assume where you are mistaken. Give me a little time
I'll write an example just for you
Because a circular reference is when a reference to an object is
stored in itself. When they are stored outside the object it is
impossible for that to happen by definition.
On Sat, Mar 14, 2015 at 12:55 AM, [email protected] <mailto:[email protected]>
<[email protected] <mailto:[email protected]>> wrote:
"by storing the callbacks outside of the delay object, we avoid
circular references entirely"
I'm talking about this is not true. So you're wrong about that.
Storing callbacks outside of the delay object changes nothing at
all and has no effects. Could you try to explain, why do you thing
that it does that? Because other participants said something that
"I don't have explain anything to you" so I had no chances to
prove that they are wrong without having that wrong stuff
At least I've heard something that makes sense: you test your
code with the help of Devel::Cycle and want hide leaks
outside an object.
You seem to be misunderstanding a few things, by storing the
callbacks outside of the delay object, we avoid circular
references entirely, they are not just hidden. And there never
were any leaks in the first place, just circular references that
get resolved later on automatically.
--
sebastian
--
You received this message because you are subscribed to the
Google Groups "Mojolicious" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
Visit this group at http://groups.google.com/group/mojolicious.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "Mojolicious" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
Visit this group at http://groups.google.com/group/mojolicious.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "Mojolicious" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
Visit this group at http://groups.google.com/group/mojolicious.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"Mojolicious" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/mojolicious.
For more options, visit https://groups.google.com/d/optout.
