Thanks, On Oct 28, 2013, at 4:36 PM, Martin Dias <tinchodias@gmail.com> wrote:
Currently there is no such option.
Maybe it is something which is needed, what do you think?
You might want to customize how your "development session" objects are encoded. Like in DateAndTime... you can look at these methods:
#fuelAccept: #serializeOn: #materializeFrom: (at class-side)
Or you can tell fuel to ignore some instance variables, if you override #fuelIgnoredInstanceVariableNames at class-side.
Both alternatives are covered in the documentation
http://rmod.lille.inria.fr/web/pier/software/Fuel
(which is sadly down in this moment, but will be up again soon)
MartÃn
On Mon, Oct 28, 2013 at 4:10 PM, roberto.minelli@usi.ch <roberto.minelli@usi.ch> wrote: Hi Martin,
Thanks for the answer, I have another question. Is there any way to tell Fuel to serialize only the object with its instance variables and thatâs it?
I donât want Fuel to traverse any reference, just the object with its fields.
Thanks, Roberto
On Oct 28, 2013, at 4:00 PM, Martin Dias <tinchodias@gmail.com> wrote:
I don't remember the previous discussion. When you tell fuel to serialize an object, it traverses the references of that object *to* other objects. By default, it uses some criteria to prune the traversal. For example, when the traversed object is a class, then it encodes the name of that class. Similar for a method.
So I think in some way your object is referencing that problematic block closure.
Maybe it can give you a clue if you put a halt in FLAnalysis>>trace:
Maybe a "self haltIf: anObject isClosure"
HTH, MartÃn
On Mon, Oct 28, 2013 at 8:16 AM, roberto.minelli@usi.ch <roberto.minelli@usi.ch> wrote: Hi,
Iâm struggling with Fuel and I probably discovered my problem.
When trying to serialize an object (that represents a development session, i.e., contains some meta-data (title, author, etc.) and some objects representing actions of the developer) I often encounter problem with some BlockClosureâs which are somewhat corrupt and Fuel crashes and cannot serialize them. We already discussed this issue in this mailing list a while ago with Max.
I do not ask directly Fuel to serialize some BlockClosures, so my intuition is that Fuel serializes all the references to the objects I am trying to serialize. Am I right? Is there any way to tell Fuel not to do so?
Cheers and thanks for the help, Roberto