[Pharo-dev] Debugging in Production Servers

Esteban A. Maringolo emaringolo at gmail.com
Fri Apr 25 16:40:59 EDT 2014


What I found useful is the ability to patch (compile code) in a
running server. That's really a plus when you can't shutdown the
server.

To me... an interactive debugger in the production environment is not
a requirement.
Esteban A. Maringolo


2014-04-25 17:38 GMT-03:00 Sebastian Sastre <sebastian at flowingconcept.com>:
>
>
> On Apr 25, 2014, at 7:01 AM, askoh <askoh at askoh.com> wrote:
>
> Thanks for all the comments. Let me distilled what I have learned. Correct
> me
> if I am wrong.
>
> In Smalltalk:
> Production environment and development environment are very similar if not
> identical.
> Runtime and debug modes are identical. So, debugging is instantaneous
> available.
> Debugging occurs at the context of the exception itself - not in a handler
> or somewhere else.
> Debugger, nah, the whole environment allows doit's, code changes and resumes
> always.
> Reflection is constantly available for debugging and logging.
>
> Can we coin a term for these capabilities/properties? Can we define a
> standard to gauge programming environments?
>
>
> great question, yeah I can validate that for airflowing.
>
> Those features allowed us to do hot maintenance more than once
>
> At least a couple of times we did it live with a real customer on the other
> side, it was really great but don’t get too excited, managing a real bug and
> a real customer's perception both at the same time requires a lot of muscle
>
> sebastian
>
> o/
>
>




More information about the Pharo-dev mailing list