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

http://lists.squeakfoundation.org/pipermail/packages/2013-January/005632.html

Name: Sound-dtl.33
Ancestors: Sound-ul.32

Bitshift optimizations by Nicolas Cellier. Use #>> or #<&lt; operator rather than #bitShift: in cases where shift direction is known in order to eliminate runtime check for shift direction in compiled VM methods.

These changes affect ADPCMCodec methods that are translated as primitives in the ADPCMCodecPlugin and are thus part of the compiled VM. See VMMaker-dtl.293 in the VMMaker repository for related changes affecting other methods in the VM.

Discussion thread: http://lists.squeakfoundation.org/pipermail/vm-dev/2012-December/011688.html

Original change sets: http://code.google.com/p/cog/issues/detail?id=111

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

http://lists.squeakfoundation.org/pipermail/packages/2013-January/005633.html

Name: Environments-fbs.9
Ancestors: Environments-cwp.8

The ReleaseSqueakTrunk CI job fails because it raises a debugger. This avoids that problem.

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

http://lists.squeakfoundation.org/pipermail/packages/2013-January/005634.html

Name: Tests-fbs.182
Ancestors: Tests-fbs.181

Environment >> #at:ifPresent:ifAbsent:.

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

http://lists.squeakfoundation.org/pipermail/packages/2013-January/005635.html

Name: Environments-fbs.10
Ancestors: Environments-fbs.9

Environment >> #at:ifPresent:ifAbsent:.

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

http://lists.squeakfoundation.org/pipermail/packages/2013-January/005636.html

Name: Environments-fbs.10
Ancestors: Environments-fbs.9

Environment >> #at:ifPresent:ifAbsent:.

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

http://lists.squeakfoundation.org/pipermail/packages/2013-January/005637.html

Name: Environments-fbs.11
Ancestors: Environments-fbs.10

For the moment - until we're sure about the proper API for environments - put things that mimic Dictionary methods in the compatibility protocol.

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

http://lists.squeakfoundation.org/pipermail/packages/2013-January/005638.html

Name: ToolsTests-fbs.57
Ancestors: ToolsTests-fbs.56

Test that when you select a system category in a new Browser, you see what you expect to see: a template for creating a new class.

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

http://lists.squeakfoundation.org/pipermail/packages/2013-January/005639.html

Name: Tools-fbs.434
Ancestors: Tools-cwp.433

Pulling these bits out makes new kinds of Browsers able to partially override behaviour.

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

http://lists.squeakfoundation.org/pipermail/packages/2013-January/005640.html

Name: ToolsTests-fbs.58
Ancestors: ToolsTests-fbs.57

Basic labelString tests. These don't test the multiwindow labelStrings though.

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

http://lists.squeakfoundation.org/pipermail/packages/2013-January/005641.html

Name: Tools-fbs.435
Ancestors: Tools-fbs.434

Don't use Class objects when all you care about is a name.

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

http://lists.squeakfoundation.org/pipermail/packages/2013-January/005642.html

Name: ToolsTests-fbs.59
Ancestors: ToolsTests-fbs.58

More characterisation tests. Note that #testClassCommentAnnotation is 'forward looking', in that it defines the soon-to-be behaviour of Browser >> #annotationForClassCommentFor:.

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

http://lists.squeakfoundation.org/pipermail/packages/2013-January/005643.html

Name: Tools-fbs.436
Ancestors: Tools-fbs.435

We already have the organization in classOrganizer. CodeHolder's version goes and looks it up.

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

http://lists.squeakfoundation.org/pipermail/packages/2013-January/005644.html

Name: ToolsTests-fbs.60
Ancestors: ToolsTests-fbs.59

Much better testing for Browser >> #annotationForClassCommentFor:.

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