Squeak-dev February 2011

squeak-dev@lists.squeakfoundation.org

87 participants
295 discussions

Procedure for condensing sources
by Chris Muller 20 Feb '11

20 Feb '11

>> We should also condense the sources file and remove deprecated >> methods. We're early in the cycle, this is a good time to "break" >> code still using 3.9Deprecated methods. > > IMHO condensing should be done before the release. It's not possible to tell > a 4.2 image to use a different sources file without changing it. > For 4.3 it doesn't worth condensing now, because we will do further changes, > which would generate cruft in the file (compared to condensing before the > release). Each release should be able to present it's deltas to the prior release. That is not cruft.

6 10

Daily Commit Log
by commits＠source.squeak.org 20 Feb '11

20 Feb '11

Changes to Trunk (http://source.squeak.org/trunk.html) in the last 24 hours: http://lists.squeakfoundation.org/pipermail/packages/2011-February/004299.h… Name: Compiler-ul.191 Ancestors: Compiler-ul.190 Restored VariableNode >> #canBeSpecialArgument, which got lost with Compiler-nice.188 for some unknown reason. It is required to compile #caseOf: with non-brace array arguments. =============================================

1 0

The Trunk: Compiler-ul.191.mcz
by commits＠source.squeak.org 19 Feb '11

19 Feb '11

Levente Uzonyi uploaded a new version of Compiler to project The Trunk: http://source.squeak.org/trunk/Compiler-ul.191.mcz ==================== Summary ==================== Name: Compiler-ul.191 Author: ul Time: 19 February 2011, 10:02:37.736 pm UUID: a7628e80-ae41-e348-b9b0-6b5f475cd90b Ancestors: Compiler-ul.190 Restored VariableNode >> #canBeSpecialArgument, which got lost with Compiler-nice.188 for some unknown reason. It is required to compile #caseOf: with non-brace array arguments. =============== Diff against Compiler-ul.190 =============== Item was added: + ----- Method: VariableNode>>canBeSpecialArgument (in category 'testing') ----- + canBeSpecialArgument + "Can I be an argument of (e.g.) ifTrue:?" + + ^code < LdNil!

1 0

20s send timeout in Socket >> sendSomeData:startIndex:count:
by Matthew Fulmer 18 Feb '11

18 Feb '11

We ran into an issue in cobalt, and finally tracked it down to the hardcoded 20 second timeout in Socket >> sendSomeData:startIndex:count: . We need to make the timeout configurable, ideally turning it off. The read timeouts in Socket and SocketStream are configurable, kind of. Has anybody done the same for the write timeouts? -- Matthew Fulmer (a.k.a. Tapple)

2 2

The Inbox: Network-fbs.108.mcz
by commits＠source.squeak.org 18 Feb '11

18 Feb '11

A new version of Network was added to project The Inbox: http://source.squeak.org/inbox/Network-fbs.108.mcz ==================== Summary ==================== Name: Network-fbs.108 Author: fbs Time: 18 February 2011, 11:00:05.486 am UUID: 228bf8a5-3dd5-be4f-a34b-2223842e5bab Ancestors: Network-nice.107 Provide a (TCP) data send with explicit timeout. The existing method (Socket>>sendSomeData:startIndex:count:) calls the new method with a default timeout of 20s. =============== Diff against Network-nice.107 =============== Item was changed: ----- Method: Socket>>sendSomeData:startIndex:count: (in category 'sending') ----- sendSomeData: aStringOrByteArray startIndex: startIndex count: count + ^ self sendSomeData: aStringOrByteArray startIndex: startIndex count: count for: 20.! - "Send up to count bytes of the given data starting at the given index. Answer the number of bytes actually sent." - "Note: This operation may have to be repeated multiple times to send a large amount of data." - - | bytesSent | - (self waitForSendDoneFor: 20) - ifTrue: [ - bytesSent := self primSocket: socketHandle - sendData: aStringOrByteArray - startIndex: startIndex - count: count] - ifFalse: [ConnectionTimedOut signal: 'send data timeout; data not sent']. - ^ bytesSent - ! Item was added: + ----- Method: Socket>>sendSomeData:startIndex:count:for: (in category 'sending') ----- + sendSomeData: aStringOrByteArray startIndex: startIndex count: count for: aTimeoutInSeconds + "Send up to count bytes of the given data starting at the given index. Answer the number of bytes actually sent." + "Note: This operation may have to be repeated multiple times to send a large amount of data." + + | bytesSent | + (self waitForSendDoneFor: aTimeoutInSeconds) + ifTrue: [ + bytesSent := self primSocket: socketHandle + sendData: aStringOrByteArray + startIndex: startIndex + count: count] + ifFalse: [ConnectionTimedOut signal: 'send data timeout; data not sent']. + ^ bytesSent + !

1 0

[ANN] OSProcess and CommandShell updated on SqueakMap
by David T. Lewis 18 Feb '11

18 Feb '11

I have updated the SqueakMap releases for OSProcess and CommandShell on SqueakMap. There are new packages identified as Squeak 4.2 versions, and also a "head" version that gets the latest from SqueakSource via update streams. Please load the "head" version of OSProcess and CommandShell unless you have a specific requirement for some older version, since I try to maintain some reasonable backward compatibility on these packages. SqueakMap has usable(?) versions of OSProcess and CommandShell going back to 2002. For earlier versions, you need to look on the Swiki, which was my original "home page" for this stuff. The first version of that OSProcess page is dated 4 October 1999, which just shows how far we have come in packaging, version control, and tools since those days :) Thanks to Chris for reviving SqueakMap and providing the new tools in the image. Dave

1 0

SqueakVM for Arm WinCE...
by melatiah＠gmx.net 18 Feb '11

18 Feb '11

Hi, I am looking for pointers please. I run a WinCE 6.0 Arm laptop on which I have a functional GCC complier 3.3.3. I have tried a PocketPC Arm Squeak VM without success. So I am looking to role my own. I did not find any sources for the pocketpc vm so have not much of a staring point. Has anyone else registered an interest in a WinCE port? Any links available for sources or discussion threads? Thanks in advance. Sash -- GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit gratis Handy-Flat! http://portal.gmx.net/de/go/dsl

2 1

Your SqueakMap Packages
by Chris Muller 18 Feb '11

18 Feb '11

Hi Aaron, Ken Brown from the Squeak community has made some enhancements to your "Script Manager" package, and would like to post his enhancement. I have made enhancements to SqueakMap recently that allow the community to _append_ releases to existing packages, as long as the package is tagged with a particular SM-Category called "Community Supported". I am a SqueakMap administrator, would you mind if I did that? Your legacy work is preserved, it cannot be removed or updated. But Ken would be able to add a new / enhanced version.. Thanks, Chris On Tue, Nov 27, 2007 at 11:50 AM, Aaron Reichow <revaaron(a)bitquabit.com> wrote: > >> Does any one ever tried to file out a BlockClosure object using >> SmartRefStream..? > > I know this is from a couple weeks ago, but I see you got not replies... > > To my knowledge, there isn't any way to do this, with ReferenceStream or > SmartRefStream. I believe you can do it with an ImageSegment, but I've had > problems with that in the past, and with saving and loading image segments > in general, at least using the examples available in the image and > elsewhere, though this is in older versions. > > > Regards, > Aaron > > Aaron Reichow >> revaaron(a)bitquabit.com > "Liberty will not descend to a people, a people must > raise themselves to Liberty." -- emma goldman > > > On Nov 7, 2007, at 2:48 PM, Thushar G R wrote: > >> Hi, >> >> Does any one ever tried to file out a BlockClosure object using >> SmartRefStream..? >> >> thanks in advance >> >> thushar >> >> -- >> thuchu >> > > >

1 1

multi-avatar Cobalt
by Lawson English 17 Feb '11

17 Feb '11

So, congratulations to John Dougan and Matt Fulmer and the other OpenCobalt developers: http://imagebin.org/138355 each window is the camera view from a different avatar. It runs at 0.05 FPS at best, but once Matt gets Cobalt working on Cog, it might be an interesting speed test. Lawson

1 0

Monticello: committing part of a change
by Frank Shearar 17 Feb '11

17 Feb '11

I often find that in the middle of some large change I see a small thing that needs correcting. Often, I just fix it and carry on hacking. Usually - with git or mercurial - I'll commit just that small change separately, so it's clear what's going on. Is there any way to do something similar in Monticello? What's the usual workflow people use to selectively commit a change? frank

7 11

← Newer
1
...
8
9
10
11
12
13
14
...
30
Older →

Jump to page: