From: JamesBritt <james@...>
Date: 2002-08-06T15:57:18+09:00
Subject: RE: Question about Marshal.dump behavior

> Yes.  It's to avoid (almost) inifinite dump loop.  I didn't want
> "dump" to dump incomplete object.  If someone come up with a better
> idea, I'd like to hear.

Oh, OK; so, code to pass an expected value for the object depth, and if dump
blows up, the app can decide (for example) if it should be retry the call
with no limit, or do something else because the object is deeper than
expected (and so all bets are off).

To provide for partial serialization, then, I would have to write my own
_dump method and logic for what to do if the depth limit is greater than the
actual object depth.


Thanks,


James



>
> 							matz.
>
>