Squeak-dev February 2013

squeak-dev@lists.squeakfoundation.org

61 participants
225 discussions

Which ConfigurationOf to use for 1.9?
by Frank Shearar 26 Feb '13

26 Feb '13

Hi Martin, Would I be correct in assuming that I can reference ConfigurationOfFuel-MartinDias.188 for Fuel 1.9? Should I wait for an official announcement before adding a SqueakMap release? (I don't think you guys have written the 1.9 release notes yet, for instance.) frank

3 3

Re: [squeak-dev] The Trunk: SMLoader-fbs.78.mcz
by Tobias Pape 26 Feb '13

26 Feb '13

Am 25.02.2013 um 21:27 schrieb commits(a)source.squeak.org: > Frank Shearar uploaded a new version of SMLoader to project The Trunk: > http://source.squeak.org/trunk/SMLoader-fbs.78.mcz > > ==================== Summary ==================== > > Name: SMLoader-fbs.78 > Author: fbs > Time: 25 February 2013, 9:27:11.959 pm > UUID: cd8023fe-60a1-4dd9-a7dd-60e8ce7f4ac5 > Ancestors: SMLoader-cmm.77 > > When installing WebClient, use the most recent version. > > =============== Diff against SMLoader-cmm.77 =============== > > Item was changed: > SystemOrganization addCategory: #SMLoader! > - SystemOrganization addCategory: #'SMLoader-Models'! > > Item was changed: > ----- Method: SMClient class>>installWebClient (in category 'private') ----- > installWebClient > + Installer ss > + project: 'WebClient'; > + install: 'WebClient-Core-ar.92.mcz'! Shouldn't this be WebClient-Core-ar.92 without the .mcz? > - (Installer repository: 'http://www.squeaksource.com/WebClient') > - install: 'WebClient-Core-ar.83'! > Best -Tobias

3 9

Regression: MVCToolBuilderTests >> #testButtonFiresSymbol
by Frank Shearar 26 Feb '13

26 Feb '13

My apologies for not noticing this sooner. Since build #175, http://build.squeak.org/job/SqueakTrunk/178/testReport/ToolBuilder.MVC/MVCT… shows a failure, saying Error Message UndefinedObject>>asParagraph Stacktrace UndefinedObject(Object)>>doesNotUnderstand: #asParagraph PluggableButtonView>>label: MVCToolBuilder>>buildPluggableButton: PluggableButtonSpec>>buildWith: MVCToolBuilder(ToolBuilder)>>build: MVCToolBuilderTests(ToolBuilderTests)>>testButtonFiresSymbol MVCToolBuilderTests(TestCase)>>performTest frank PS At some stage we ought to think of getting CI to report regressions. However, we really ought to have a clean green test suite before that, or we'll be spammed every time the build runs. When I'm hacking on the CI scripts, that can be quite a lot!

1 0

Regression: RenderBugz >> #testHeading
by Frank Shearar 26 Feb '13

26 Feb '13

My apologies for not having noticed this earlier. Since #180, http://build.squeak.org/job/SqueakTrunk/lastCompletedBuild/testReport/Tests… shows a failure, saying Error Message Block evaluation took more than the expected 0:00:00:00.004 Stacktrace RenderBugz(TestCase)>>assert:description: RenderBugz(TestCase)>>should:notTakeMoreThan: RenderBugz(TestCase)>>should:notTakeMoreThanMilliseconds: RenderBugz>>shouldntTakeLong: RenderBugz>>testHeading RenderBugz(TestCase)>>performTest I don't know if this is an intermittent failure or what might cause it. frank

1 0

Daily Commit Log
by commits＠source.squeak.org 26 Feb '13

26 Feb '13

Changes to Trunk (http://source.squeak.org/trunk.html) in the last 24 hours: http://lists.squeakfoundation.org/pipermail/packages/2013-February/005735.h… Name: SMLoader-fbs.78 Ancestors: SMLoader-cmm.77 When installing WebClient, use the most recent version. ============================================= http://lists.squeakfoundation.org/pipermail/packages/2013-February/005736.h… Name: Compiler-nice.256 Ancestors: Compiler-nice.255 Continue cleaning of Compiler by removing now unused instance variables. Also remove CompilationCue>>sourceStream which is unused. =============================================

1 0

Installing SqueakSSL automatically?
by Frank Shearar 25 Feb '13

25 Feb '13

http://www.squeaksource.com/WebClient/ says To install SqueakSSL you need to download and install the binary version of the plugin and then install SqueakSSL via: (Installer ss) project: 'SqueakSSL'; install: 'SqueakSSL-Core'; install: 'SqueakSSL-Tests'. But how do I install the plugin? Is it possible to do so programmatically/in an automated fashion? Otherwise these will stay sad and yellow: http://build.squeak.org/job/ExternalPackage-WebClient/1/#showFailuresLink frank

2 6

The Trunk: Compiler-nice.256.mcz
by commits＠source.squeak.org 25 Feb '13

25 Feb '13

Nicolas Cellier uploaded a new version of Compiler to project The Trunk: http://source.squeak.org/trunk/Compiler-nice.256.mcz ==================== Summary ==================== Name: Compiler-nice.256 Author: nice Time: 25 February 2013, 10:49:12.747 pm UUID: f3619127-599b-4b0e-864b-9508047d84cf Ancestors: Compiler-nice.255 Continue cleaning of Compiler by removing now unused instance variables. Also remove CompilationCue>>sourceStream which is unused. =============== Diff against Compiler-nice.255 =============== Item was removed: - ----- Method: CompilationCue>>sourceStream (in category 'accessing') ----- - sourceStream - ^ source readStream! Item was changed: Object subclass: #Compiler + instanceVariableNames: 'sourceStream parser cue' - instanceVariableNames: 'sourceStream requestor class category context parser cue' classVariableNames: '' poolDictionaries: '' category: 'Compiler-Kernel'! !Compiler commentStamp: 'cwp 12/26/2012 23:17' prior: 0! The compiler accepts Smalltalk source code and compiles it with respect to a given class. The user of the compiler supplies a context so that temporary variables are accessible during compilation. If there is an error, a requestor (usually a kind of StringHolderController) is sent the message notify:at:in: so that the error message can be displayed. If there is no error, then the result of compilation is a MethodNode, which is the root of a parse tree whose nodes are kinds of ParseNodes. The parse tree can be sent messages to (1) generate code for a CompiledMethod (this is done for compiling methods or evaluating expressions); (2) pretty-print the code (for formatting); or (3) produce a map from object code back to source code (used by debugger program-counter selection). See also Parser, Encoder, ParseNode.! Item was changed: ----- Method: Compiler>>setCue: (in category 'private') ----- setCue: aCue + cue := aCue! - cue := aCue. - - "Set legacy instance variables for methods that don't use cue yet." - requestor := cue requestor. - class := cue getClass. - category := cue category. - context := cue context.!

1 0

The Trunk: SMLoader-fbs.78.mcz
by commits＠source.squeak.org 25 Feb '13

25 Feb '13

Frank Shearar uploaded a new version of SMLoader to project The Trunk: http://source.squeak.org/trunk/SMLoader-fbs.78.mcz ==================== Summary ==================== Name: SMLoader-fbs.78 Author: fbs Time: 25 February 2013, 9:27:11.959 pm UUID: cd8023fe-60a1-4dd9-a7dd-60e8ce7f4ac5 Ancestors: SMLoader-cmm.77 When installing WebClient, use the most recent version. =============== Diff against SMLoader-cmm.77 =============== Item was changed: SystemOrganization addCategory: #SMLoader! - SystemOrganization addCategory: #'SMLoader-Models'! Item was changed: ----- Method: SMClient class>>installWebClient (in category 'private') ----- installWebClient + Installer ss + project: 'WebClient'; + install: 'WebClient-Core-ar.92.mcz'! - (Installer repository: 'http://www.squeaksource.com/WebClient') - install: 'WebClient-Core-ar.83'!

1 0

Re: [squeak-dev] The Trunk: KernelTests-nice.244.mcz
by Eliot Miranda 25 Feb '13

25 Feb '13

Please, please, *please* let's not do things like WriteStream on: ''. Just decompile the method and you'll see why. Please, please, *PLEASE* use either WriteStream on: String new or WriteStream on: '' copy. Modifying literals is a baaaad idea. On Sat, Feb 23, 2013 at 11:49 AM, <commits(a)source.squeak.org> wrote: > Nicolas Cellier uploaded a new version of KernelTests to project The Trunk: > http://source.squeak.org/trunk/KernelTests-nice.244.mcz > > ==================== Summary ==================== > > Name: KernelTests-nice.244 > Author: nice > Time: 23 February 2013, 8:49:05.862 pm > UUID: 7b3445ea-0910-4ee4-a6c7-c7305f930764 > Ancestors: KernelTests-fbs.243 > > Avoid using ReadWriteStream gratuitously when we just need a WriteStream. > > =============== Diff against KernelTests-fbs.243 =============== > > Item was changed: > ----- Method: DateAndTimeEpochTest>>testPrintOn (in category 'testing') ----- > testPrintOn > + | ref ws | > + ref := '1901-01-01T00:00:00+00:00'. > + ws := '' writeStream. > + aDateAndTime printOn: ws. > + self assert: ws contents = ref. > + ref := 'a TimeZone(ETZ)'. > + ws := '' writeStream. > + aTimeZone printOn: ws. > + self assert: ws contents = ref! > - | cs rw | > - cs := ReadStream on: '1901-01-01T00:00:00+00:00'. > - rw := ReadWriteStream on: ''. > - aDateAndTime printOn: rw. > - self assert: rw contents = cs contents. > - cs := ReadStream on: 'a TimeZone(ETZ)'. > - rw := ReadWriteStream on: ''. > - aTimeZone printOn: rw. > - self assert: rw contents = cs contents! > > Item was changed: > ----- Method: DateAndTimeLeapTest>>testPrintOn (in category 'testing') ----- > testPrintOn > + | ref ws | > + ref := '2004-02-29T13:33:00+02:00'. > + ws := '' writeStream. > + aDateAndTime printOn: ws. > + self assert: ws contents = ref. > + ref := 'a TimeZone(UTC)'. > + ws := '' writeStream. > + aTimeZone printOn: ws. > + self assert: ws contents = ref ! > - | cs rw | > - cs := ReadStream on: '2004-02-29T13:33:00+02:00'. > - rw := ReadWriteStream on: ''. > - aDateAndTime printOn: rw. > - self assert: rw contents = cs contents. > - cs := ReadStream on: 'a TimeZone(UTC)'. > - rw := ReadWriteStream on: ''. > - aTimeZone printOn: rw. > - self assert: rw contents = cs contents ! > > Item was changed: > ----- Method: DateTest>>testPrintOn (in category 'testing') ----- > testPrintOn > + | ref ws | > + ref := '23 January 2004'. > + ws := '' writeStream. > + aDate printOn: ws. > + self assert: ws contents = ref! > - | cs rw | > - cs := ReadStream on: '23 January 2004'. > - rw := ReadWriteStream on: ''. > - aDate printOn: rw. > - self assert: rw contents = cs contents! > > Item was changed: > ----- Method: DateTest>>testPrintOnFormat (in category 'testing') ----- > testPrintOnFormat > + | ref ws | > + ref :='04*Jan*23'. > + ws := '' writeStream. > + aDate printOn: ws format: #(3 2 1 $* 2 2). > + self assert: ws contents = ref! > - | cs rw | > - cs := ReadStream on: '04*Jan*23'. > - rw := ReadWriteStream on: ''. > - aDate printOn: rw format: #(3 2 1 $* 2 2). > - self assert: rw contents = cs contents! > > Item was changed: > ----- Method: DateTest>>testStoreOn (in category 'testing') ----- > testStoreOn > + | ref ws | > + ref := '''23 January 2004'' asDate'. > + ws := '' writeStream. > + aDate storeOn: ws. > + self assert: ws contents = ref! > - | cs rw | > - cs := ReadStream on: '''23 January 2004'' asDate'. > - rw := ReadWriteStream on: ''. > - aDate storeOn: rw. > - self assert: rw contents = cs contents! > > Item was changed: > ----- Method: DurationTest>>testPrintOn (in category 'testing') ----- > testPrintOn > + | ref ws | > + ref := '1:02:03:04.000000005'. > + ws := '' writeStream. > + aDuration printOn: ws. > + self assert: ws contents = ref! > - |cs rw | > - cs := ReadStream on: '1:02:03:04.000000005'. > - rw := ReadWriteStream on: ''. > - aDuration printOn: rw. > - self assert: rw contents = cs contents.! > > Item was changed: > ----- Method: IntegerTest>>testPrintOnBaseShowRadix (in category 'tests - printing') ----- > testPrintOnBaseShowRadix > | s | > + s := '' writeStream. > - s := ReadWriteStream on: ''. > 123 printOn: s base: 10 showRadix: false. > self assert: (s contents = '123'). > > + s := '' writeStream. > - s := ReadWriteStream on: ''. > 123 printOn: s base: 10 showRadix: true. > self assert: (s contents = '10r123'). > > + s := '' writeStream. > - s := ReadWriteStream on: ''. > 123 printOn: s base: 8 showRadix: false. > self assert: (s contents = '173'). > > + s := '' writeStream. > - s := ReadWriteStream on: ''. > 123 printOn: s base: 8 showRadix: true. > self assert: (s contents = '8r173').! > > Item was changed: > ----- Method: StopwatchTest>>testPrintOn (in category 'testing') ----- > testPrintOn > + | ref ws | > + ref := 'a Stopwatch(suspended:0:00:00:00)'. > + ws := '' writeStream. > + aStopwatch printOn: ws. > + self assert: ws contents = ref! > - | cs rw | > - cs := ReadStream on: 'a Stopwatch(suspended:0:00:00:00)'. > - rw := ReadWriteStream on: ''. > - aStopwatch printOn: rw. > - self assert: rw contents = cs contents! > > Item was changed: > ----- Method: TimeStampTest>>testPrintOn (in category 'testing') ----- > testPrintOn > + | ref ws | > + ref := '2 January 2004 12:34:56 am'. > + ws := '' writeStream. > + aTimeStamp printOn: ws. > + self assert: ws contents = ref! > - | cs rw | > - cs := ReadStream on: '2 January 2004 12:34:56 am'. > - rw := ReadWriteStream on: ''. > - aTimeStamp printOn: rw. > - self assert: rw contents = cs contents! > > Item was changed: > ----- Method: TimeStampTest>>testStoreOn (in category 'testing') ----- > testStoreOn > + | ref ws | > + ref := '''2 January 2004 12:34:56 am'' asTimeStamp'. > + ws := '' writeStream. > + aTimeStamp storeOn: ws. > + self assert: ws contents = ref! > - | cs rw | > - cs := ReadStream on: '''2 January 2004 12:34:56 am'' asTimeStamp'. > - rw := ReadWriteStream on: ''. > - aTimeStamp storeOn: rw. > - self assert: rw contents = cs contents! > > Item was changed: > ----- Method: TimespanTest>>testPrintOn (in category 'testing') ----- > testPrintOn > + | ref ws | > + ref := 'a Timespan(2005-01-01T00:00:00+00:00D7:00:00:00)'. > + ws := '' writeStream. > + aTimespan printOn: ws. > + self assert: ws contents = ref > - | cs rw | > - cs := ReadStream on: 'a Timespan(2005-01-01T00:00:00+00:00D7:00:00:00)'. > - rw := ReadWriteStream on: ''. > - aTimespan printOn: rw. > - self assert: rw contents = cs contents > ! > > Item was changed: > ----- Method: YearMonthWeekTest>>testMonthPrintOn (in category 'testing') ----- > testMonthPrintOn > + | aMonth ws | > + aMonth := Month starting: DateAndTime new duration: 31 days. > + ws := '' writeStream. > + aMonth printOn: ws. > + self assert: ws contents = 'January 1901'.! > - | aMonth cs rw | > - aMonth := Month starting: DateAndTime new duration: 31 days. > - cs := ReadStream on: 'January 1901'. > - rw := ReadWriteStream on: ''. > - aMonth printOn: rw. > - self assert: rw contents = cs contents.! > > Item was changed: > ----- Method: YearMonthWeekTest>>testYearPrintOn (in category 'testing') ----- > testYearPrintOn > + | aYear ws | > + aYear := Year starting: DateAndTime new duration: 365 days. > + ws := '' writeStream. > + aYear printOn: ws. > + self assert: ws contents = 'a Year (1901)'.! > - | aYear cs rw | > - aYear := Year starting: DateAndTime new duration: 365 days. > - cs := ReadStream on: 'a Year (1901)'. > - rw := ReadWriteStream on: ''. > - aYear printOn: rw. > - self assert: rw contents = cs contents.! > > -- best, Eliot

6 8

[JOB][Research] 16 month Postdoc "Architectural Design Exploration"
by Marcus Denker 25 Feb '13

25 Feb '13

Architectural Design Exploration ================================ About Inria and the job ----------------------- Inria, with its academic, institutional and industrial partners, is commited to major research and innovation projects in the field of computational sciences. The institute disseminates across France thanks to its eight research centres. The Inria Lille - Nord Europe research centre, inaugurated in 2008, employs 357 people, including 250 scientists, in its seventeen research teams. Recognised for its significant contribution to the social and economic development of the Nord - Pas-de-Calais region, the Inria Lille - Nord Europe research centre promotes a policy of close cooperation with major businesses and small enterprises. By encouraging synergies between researchers and industrial partners, Inria contributes to the transfer of skills and expertise in computational technologies and provides access to top-level European and international research in order to support innovation and businesses, particularly in the region of Lille. Whether designing innovative software for business or logistics, modelling living cells or fusion plasma, or developing medical simulators or interfaces to facilitate human-computer interaction, our research opens up new possibilities that can revolutionise common practice and contribute to a better understanding of the natural phenomena which surround us. The postdoc is hosted by Team-Project RMoD. The goal of RMoD is to support remodularization of object-oriented applications. This objective is tackled from two complementary perspectives: reengineering and modularity constructs for programming languages. In the reengineering perspective we will propose new analyses to understand and restructure existing large applications (specialized package metrics, adapted visualizations, layer identification) on top of Moose [Duca08a], [Bhat12b]. http://rmod.lille.inria.fr/web/ Mission -------- Changes in the architecture may occur during the entire lifecycle of a system. Some of them might only affect local parts of a system, while others have more systemic impact. In general, we distinguish three types of approaches for handling change systematically, listed in an order of increasing severity: - Refactoring. They correspond to improvements and concern only certain components and connectors. They do not alter the offered functionality of the system. - Renovating. Sometimes, parts of the architecture are in such a bad condition that refactoring cannot work anymore. In such contexts, renovating the architecture – by restoring its fundamental principles or refreshing essential components – may be the better choice. Renovating also deals with only parts of the system. - Re-architecting. When an architecture is subject to significant changes, refactoring or renovating may not suffice. This might be the case if for example the technology platform is to be replaced by a new one, if there is a large change in business scope, or if the architecture is in such a bad shape that errors keep emerging. In such cases, re-architecting is required. The re-architecting process usually analyzes the existing architecture (e.g., using a SWOT analysis) and results in a new architecture by: a) reusing those components worthwhile to keep, b) modifying some of the existing components (refactoring) and c) re-building the rest of the components (renovating).[Ieee13] Because software engineers do not have a full understanding of the complete source code, each kind of changes may solve some problems (e.g. reduce some cycle between package), while creating new problems (e.g. creating new cycles). In this situation it would be profitable to have a tool that allows to test a possible new configuration (refactored, renovated or re-architectured) of the source code to see if the abstract property one wishes to improve, first actually improved, and second, did not improve at the expense of another equally important one. For this several alternatives new configurations have to be considered. In the RMoD team, we developed Orion [Lava10b], a tool that uses models as abstract representations of the program and enables the definition of several possible alternative versions of this program. Each version differentiates from the others by a set of refactoring operations. Currently, once an adequate version is selected, the user has to manually perform the operations on the code. Job offer description ---------------------- In this postdoc, we would like to enhance Orion in order to automatically generate code or modify the existing one once a version is chosen. Thus, it would be possible to study various alternatives of possible refactoring or restructuring of an existing program, using metrics [Abde12a], [Mord12b] or some other means [Hema12] to check the improvement in the "quality" of the code, and then ask the tool to perform the changes of the selected final solution onto the source code. The used metamodel enables a representation where code details are abstracted. A new metamodel for example AST metamodel, representing code will be introduced and the links between the two models will have to be maintained. Skills and profile -------------------- The candidate should : - hold a PhD degree in Computer Science - be fluent in English (French is an advantage but not required) - be knowledgeable in the domains of Software Engineering, maintenance, code analysis - have good programming skills in Smalltalk or be able to acquire them in a short amount of time Benefits --------- - Possibility of French courses - Help for housing - Participation for transportation - Scientific Resident card and help for husband/wife visa Additional information ----------------------- - Duration : 16 months - Salary: 2 620,84 € gross/month - Monthly salary after taxes : around 2 138€ (medical insurance included). - Before applying, please contact the scientist advisor: nicolas.anquetil(a)inria.fr - For the first selections, please apply before March 2013, 22nd Security and defense procedure ------------------------------- In the interests of protecting its scientific and technological assets, Inria is a restricted-access establishment. Consequently, it follows special regulations for welcoming any person who wishes to work with the institute. The final acceptance of each candidate thus depends on applying this security and defense procedure. More information: http://rmod.lille.inria.fr/web/pier/blog/2013-02-22-2

1 0

← Newer
1
2
3
4
5
6
7
8
9
...
23
Older →

Jump to page: