Daily Commit Log

Changes to Trunk (http://source.squeak.org/trunk.html) in the last 24 hours:

http://lists.squeakfoundation.org/pipermail/packages/2015-July/008772.html

Name: Morphic-eem.990
Ancestors: Morphic-cmm.989

Update the CurvierMorph's drawCurvier preference
to the recommended style., eliminating the only send of addPreference:category:default:balloonHelp:
in trunk outside of Preferences.

=============================================

http://lists.squeakfoundation.org/pipermail/packages/2015-July/008773.html

Name: Kernel-eem.930
Ancestors: Kernel-eem.929

Fix the bug with the Debugger's through such that the Debugger would appear to freeze when encountering an MNU.  The example is Debug It on:

        Object flushDependents do: [ : e | ]

followed by Over, Through.  But in fact one can see the same issue doing Debug It and then Through on

        nil zork

What was happening is that Through was stepping through the uncaught and looping MNUs (of do: or zork in the above examples) since the Debugger did not catch unhandled errors during Through, and sicne doesNotUnderstand:'s default if uncaught is to resend.  The fix is merely to catch unhandled errors when doing Through to the same effect as runUntilErrorOrReturnFrom: caching errors for Over.

Also speed up Through.  The changes made in Kernel-eem.857 through Kernel-eem.896 to provide process-faithful debugging slowed down Process>>step a lot.  These changes restore the performance by using evaluate:onBehalfOf: once for each Through, rather than once for each step within Through.

=============================================

http://lists.squeakfoundation.org/pipermail/packages/2015-July/008774.html

Name: System-eem.750
Ancestors: System-eem.749

Provide a defaultAction for Warning that gives the user the option of debugging, ignoring or terminating when a Warning is raised in normal execution, or allows the Debugger to handle it if a Warning is raised during debugging.

=============================================

http://lists.squeakfoundation.org/pipermail/packages/2015-July/008775.html

Name: Kernel-eem.931
Ancestors: Kernel-eem.930

When an error occurs during complete:, which is used by the Debugger, raise a Notification to allow the Debugger to learn of the error's description.

=============================================

http://lists.squeakfoundation.org/pipermail/packages/2015-July/008776.html

Name: Tools-eem.627
Ancestors: Tools-eem.626

Use Kernel-eem.931 to have the debugger update its label to the description of an exception raised while debugging.

=============================================

http://lists.squeakfoundation.org/pipermail/packages/2015-July/008777.html

Name: Kernel-eem.932
Ancestors: Kernel-eem.931

Provide the same Debugger label support as complete: for the step into block support.

=============================================

http://lists.squeakfoundation.org/pipermail/packages/2015-July/008778.html

Name: Tools-eem.628
Ancestors: Tools-eem.627

Debugger: Extract the exception notification handler into its own method and use it for Through support also.

=============================================

http://lists.squeakfoundation.org/pipermail/packages/2015-July/008779.html

Name: Collections.spur-topa.637
Ancestors: Collections-topa.637, Collections.spur-eem.636

Collections-topa.637 patched for Spur by SpurBootstrapMonticelloPackagePatcher Cog-eem.270

Always store Characters as if they had one instance variable with their value, regardless whether they are actually shaped that way.

=============================================

http://lists.squeakfoundation.org/pipermail/packages/2015-July/008780.html

Name: Kernel.spur-eem.930
Ancestors: Kernel-eem.930, Kernel.spur-eem.929

Kernel-eem.930 patched for Spur by SpurBootstrapMonticelloPackagePatcher Cog-eem.270

Fix the bug with the Debugger's through such that the Debugger would appear to freeze when encountering an MNU.  The example is Debug It on:

        Object flushDependents do: [ : e | ]

followed by Over, Through.  But in fact one can see the same issue doing Debug It and then Through on

        nil zork

What was happening is that Through was stepping through the uncaught and looping MNUs (of do: or zork in the above examples) since the Debugger did not catch unhandled errors during Through, and sicne doesNotUnderstand:'s default if uncaught is to resend.  The fix is merely to catch unhandled errors when doing Through to the same effect as runUntilErrorOrReturnFrom: caching errors for Over.

Also speed up Through.  The changes made in Kernel-eem.857 through Kernel-eem.896 to provide process-faithful debugging slowed down Process>>step a lot.  These changes restore the performance by using evaluate:onBehalfOf: once for each Through, rather than once for each step within Through.

=============================================

http://lists.squeakfoundation.org/pipermail/packages/2015-July/008781.html

Name: Kernel.spur-eem.931
Ancestors: Kernel-eem.931, Kernel.spur-eem.930

Kernel-eem.931 patched for Spur by SpurBootstrapMonticelloPackagePatcher Cog-eem.270

When an error occurs during complete:, which is used by the Debugger, raise a Notification to allow the Debugger to learn of the error's description.

=============================================

http://lists.squeakfoundation.org/pipermail/packages/2015-July/008782.html

Name: System.spur-cmm.744
Ancestors: System-cmm.744, System.spur-topa.743

System-cmm.744 patched for Spur by SpurBootstrapMonticelloPackagePatcher Cog-eem.270

Updated copyright year.

=============================================

http://lists.squeakfoundation.org/pipermail/packages/2015-July/008783.html

Name: Kernel.spur-eem.932
Ancestors: Kernel-eem.932, Kernel.spur-eem.931

Kernel-eem.932 patched for Spur by SpurBootstrapMonticelloPackagePatcher Cog-eem.270

Provide the same Debugger label support as complete: for the step into block support.

=============================================

http://lists.squeakfoundation.org/pipermail/packages/2015-July/008784.html

Name: System.spur-eem.745
Ancestors: System-eem.745, System.spur-cmm.744

System-eem.745 patched for Spur by SpurBootstrapMonticelloPackagePatcher Cog-eem.270

Rewrite Preferences to eliminate the AccessProtect.
Use a copy, update copy, assign scheme to update
the preferences dictionary atomically.

Change Preferences access method compilation to
use Object>>#value to eliminate a block creation.

Change Preference initialization to eliminate the
isKindOf: Symbol.

This is step 1.  Given SystemPreferences it is clear
that the preferences dictionary should be stored in
a class inst var, so that SystemPreferences and
Preferences can share methods but access different
dictionaries.  The dictionaryOfProferences[:] accessors
are dubious as they break encapsulatiopn.  For example,
the reportPreferences: method, which is the only external
access, could insateaqd be moved into Preferences class.

=============================================

http://lists.squeakfoundation.org/pipermail/packages/2015-July/008785.html

Name: System.spur-eem.746
Ancestors: System-eem.746, System.spur-eem.745

System-eem.746 patched for Spur by SpurBootstrapMonticelloPackagePatcher Cog-eem.270

First part of Preferences putsch to move preferences dictionary from class var to inst var.  Also update class comment to describe preference pragmas.

=============================================

http://lists.squeakfoundation.org/pipermail/packages/2015-July/008786.html

Name: System.spur-eem.747
Ancestors: System-eem.747, System.spur-eem.746

System-eem.747 patched for Spur by SpurBootstrapMonticelloPackagePatcher Cog-eem.270

Second part of putsch.  Move preferences dictionary from class var to inst var.  Remove the setter, and makde the getter, currently used only by SystemReporter, answer a copy.

=============================================

http://lists.squeakfoundation.org/pipermail/packages/2015-July/008787.html

Name: System.spur-ul.748
Ancestors: System-ul.748, System.spur-eem.747

System-ul.748 patched for Spur by SpurBootstrapMonticelloPackagePatcher Cog-eem.270

- Iterate over pragmas once per method instead of once per pragma in Preferences class>>prefEvent:.
- There's no need to copy preferencesDictionary in Preferences class>>storePreferencesIn:, because it's a read-only data structure.
- Ensure the durability of the changes of preferencesDictionary in Preferences class>>atomicUpdatePreferences: by checking for changes before overwriting it.

=============================================

http://lists.squeakfoundation.org/pipermail/packages/2015-July/008788.html

Name: System.spur-eem.749
Ancestors: System-eem.749, System.spur-ul.748

System-eem.749 patched for Spur by SpurBootstrapMonticelloPackagePatcher Cog-eem.270

Revert storePreferencesIn: to work with a copy,
which accords with the old code.  Go for brevity
in prefEvent:.

=============================================

http://lists.squeakfoundation.org/pipermail/packages/2015-July/008789.html

Name: System.spur-eem.750
Ancestors: System-eem.750, System.spur-eem.749

System-eem.750 patched for Spur by SpurBootstrapMonticelloPackagePatcher Cog-eem.270

Provide a defaultAction for Warning that gives the user the option of debugging, ignoring or terminating when a Warning is raised in normal execution, or allows the Debugger to handle it if a Warning is raised during debugging.

=============================================

http://lists.squeakfoundation.org/pipermail/packages/2015-July/008790.html

Name: Tools-cmm.629
Ancestors: Tools-eem.628

Restore the classic Warning window because it supports application-formatted messages which can wrap and scroll as needed.

=============================================

http://lists.squeakfoundation.org/pipermail/packages/2015-July/008791.html

Name: System-cmm.751
Ancestors: System-eem.750

Restore classic Warning window because it supports application-formatted messages which can wrap and scroll as needed.

=============================================