Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when serilizing class with FuelMetalevel #200

Open
GoogleCodeExporter opened this issue Mar 24, 2015 · 6 comments
Open

Error when serilizing class with FuelMetalevel #200

GoogleCodeExporter opened this issue Mar 24, 2015 · 6 comments

Comments

@GoogleCodeExporter
Copy link


needs FuelMetalevel loaded:

(ConfigurationOfFuel project version: '1.9') load: #(FuelMetalevel).


Code to reproduce:

aClass := Object subclass: #A category: 'Temporary'.
aSerializer := FLSerializer newDefault.
aSerializer analyzer considerInternalAllBehaviors: {aClass}.
aSerializer serialize: { aClass new } on: ByteArray new writeStream.




Max, you were right: It is because of FLAnalysis>>run:

    objectStack push: root.
    [ objectStack isEmpty ] 
        whileFalse: [ self mapAndTrace: objectStack pop ].
    [ privateObjectStack isEmpty ] 
        whileFalse: [ self privateMapAndTrace: privateObjectStack pop ].


reason:
classes go to the privateObjectStack, but they add objects to the objectStack, 
which is never never consumed.



a workaround is to reference the class directly from the graph. In the example:

aSerializer serialize: { aClass. aClass new } on: ByteArray new writeStream.


Original issue reported on code.google.com by tinchod...@gmail.com on 15 Apr 2013 at 2:11

@stale
Copy link

stale bot commented May 18, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will remain open but will probably not come into focus. If you still think this should receive some attention, leave a comment. Thank you for your contributions.

@stale stale bot added the stale label May 18, 2021
@theseion theseion added the tests label Oct 30, 2021
@stale stale bot removed the stale label Oct 30, 2021
@theseion
Copy link
Owner

Write a test for this.

@stale
Copy link

stale bot commented Dec 29, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will remain open but will probably not come into focus. If you still think this should receive some attention, leave a comment. Thank you for your contributions.

@stale stale bot added the stale label Dec 29, 2021
@theseion
Copy link
Owner

theseion commented Jan 2, 2022

Not stale.

@stale stale bot removed the stale label Jan 2, 2022
@stale
Copy link

stale bot commented Mar 3, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will remain open but will probably not come into focus. If you still think this should receive some attention, leave a comment. Thank you for your contributions.

@stale stale bot added the stale label Mar 3, 2022
@theseion
Copy link
Owner

theseion commented Mar 4, 2022

Not stale

@theseion theseion added the pinned Never mark this issue stale label Mar 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants