Issue 5029 in pharo: Add a support for quitting to OS with exit code

Status: Accepted
Owner: [hidden email]
CC: [hidden email]
Labels: Milestone-1.4 Type-Feature

New issue 5029 by [hidden email]: Add a support for quitting to OS with  
exit code
http://code.google.com/p/pharo/issues/detail?id=5029

The work to do is as little as following:

SmalltalkImage >> quit: exitCode
        "Primitive. Exit to another operating system on the host machine, if one
        exists. All state changes in the object space since the last snapshot are  
lost.
        Essential. See Object documentation whatIsAPrimitive."

        <primitive: 113>
        self primitiveFailed


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #1 on issue 5029 by [hidden email]: Add a support for  
quitting to OS with exit code
http://code.google.com/p/pharo/issues/detail?id=5029

Yes, that is great.

But don't we have to integrate this somehow with  
SmalltalkImage>>#snapshot:andQuit: ?


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Closed

Comment #2 on issue 5029 by [hidden email]: Add a support for  
quitting to OS with exit code
http://code.google.com/p/pharo/issues/detail?id=5029

Camillo added it... not yet integrated, but soon with another batch


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #3 on issue 5029 by [hidden email]: Add a support for  
quitting to OS with exit code
http://code.google.com/p/pharo/issues/detail?id=5029

@sven

you can always just do a snapshot and then an exit with the status code you  
want.
otherwise you directly exit without bothering about snapshots (I think this  
is the default behavior for me)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #4 on issue 5029 by [hidden email]: Add a support for  
quitting to OS with exit code
http://code.google.com/p/pharo/issues/detail?id=5029

Camillo,

I thought this ( #quit: ) was already integrated, but I can't find it

What do you mean exactly with 'you can always just do a snapshot and then  
an exit with the status code you want', what method are you talking about ?

Sven


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #5 on issue 5029 by [hidden email]: Add a support for  
quitting to OS with exit code
http://code.google.com/p/pharo/issues/detail?id=5029

most of the code is avail in

http://code.google.com/p/pharo/issues/detail?id=5290

Brilliant sentences of mine :D, here the translation:

- if you need to create a snapshot before exiting
    Smalltalk snapshot: true andQuit: false.
    Smalltalk exitFailure.

- if don't need a snapshot before exiting
    Smalltalk exitFailure.

so we can keep the snapshot:andQuit: as is... (though  I don't like it  
particularly)



_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker