Squeak-dev June 2008

squeak-dev@lists.squeakfoundation.org

130 participants
143 discussions

[JSqueak] Which list?
by Victor Rodriguez 27 Jun '08

27 Jun '08

Hello, In which list do you prefer to have discussions about JSqueak? On one hand, there is the jsqueakinterest mailing list, on the other, Dan Ingalls suggested to use squeak-dev.. Please reply if you are, or are not, interested. I'll try not to post to both mailing lists again. Best Regards, Víctor Rodríguez.

2 1

#collect: on strings
by Damien Cassou 27 Jun '08

27 Jun '08

Hi, is it normal that the following code fails: 'something' collect: [ :letter | letter isVowel ]. It fails because #collect: creates a new string and tries to put booleans in it. However, I don't think this is the desired behavior. -- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)

10 23

question on Parser>>pattern:inContext: and method:context:encoder:
by Eliot Miranda 27 Jun '08

27 Jun '08

Hi All, I noticed when merging the base and Tweak compilers that Andreas wrote different versions of Parser>>method:context:encoder: and Parser>>pattern:inContext: for the Tweak compiler (in CParser) that "do the right thing". His versions in CParser bind the arguments in pattern:inContext: as each arg name is encountered. The versions in Parser bind the arguments in Parser>>method:context:encoder: all in one go *after* pattern:inContext: has parsed all arguments. This means that if there is an error (e.g. use the same arg name twice) the Parser methods insert the error at the wrong point since prevMark is now always pointing to the last argument not necessarily to the argument that is repeated. yes, you guessed it I just repeated an argument name and was confused as hell for a while since the damn compiler pointed to the error at the wrong place. So I clearly want to replace the methods in Parser with Andreas' mo' betta ones in CParser. The annoying question is why did anyone change the original Parser methods to do the wrong thing in the first place? Until I know that I have a nagging doubt that I'm missing something. I've gone through the update history up to version 3.6 and don't see the new behaviour in Parser in any update there-in. Anyone know why this changed or can point me to where to look next? AdvThanksance Eliot

4 5

ESUG Awards
by Noury Bouraqadi 27 Jun '08

27 Jun '08

Hi, Don't forget to submit your software. More on: http://www.esug.org/conferences/awards2008/ Regards, Noury ------------------------------------------------------------------ Dr. Noury Bouraqadi - Enseignant/Chercheur Responsable de l'enseignement de l'informatique ARMINES - Ecole des Mines de Douai - Dept. I.A. http://vst.ensm-douai.fr/noury European Smalltalk Users Group Board http://www.esug.org ------------------------------------------------------------------

1 1

[JSqueak] Keyboard input fix
by Victor Rodriguez 27 Jun '08

27 Jun '08

Hello, I committed a fix for JSqueak keyboard input to my unofficial git repository. I fixed the handling of the return, navigation and modifier keys. The repository is at http://github.com/victorr/jsqueak/tree and if you do not want to bother checking out the repository you can obtain a tar file from http://github.com/victorr/jsqueak/tarball/master Best Regards, Víctor Rodríguez. p.d. I crossposted again... I'm sorry, but I'm impatient!

1 0

Delay scheduling lacks atomicity
by Igor Stasenko 25 Jun '08

25 Jun '08

Here the two lines of code, from Delay>>activate, which making me feel bad: TimingSemaphore initSignals. Delay primSignal: TimingSemaphore atMilliseconds: resumptionTime. Things can go wild, if VM will signal previously scheduled timer semaphore between first line and second line. The more appropriate code would be: Delay primSignal: nil atMilliseconds: 0. "reset VM timer, so there is no chance that TimingSemaphore can be signaled in between" TimingSemaphore initSignals. Delay primSignal: TimingSemaphore atMilliseconds: resumptionTime. Without it, there are chance that delay can be signaled prematurely, and also a TimingSemaphore will have an excessive signals after VM signal it again. I not sure if this is possible at all. VM checks for interrupts at each real send. A primitive , which is in #primSignal:atMilliseconds: is not real send, so maybe its ok here, but i would not put much trust into it. The code should be written in a way, that it impossible to break it regardless on how often VM checks for interrupts. A more reliable, would be is to change primitive and reset signals counter of installed semaphore. This will ensure atomicity. So, a primitive would behave as following: - reset semaphore signals - schedule semaphore signal at given millisecond clock value -- Best regards, Igor Stasenko AKA sig.

1 0

Squeak and the iPhone
by John M McIntosh 24 Jun '08

24 Jun '08

I'm pleased to say that I'm one of the 1.5% of the iPhone developer population that has been accepted to officially build applications for distribution via Apple's iPhone Application Store. Because of this I have embarked on a 93 work day journey to build a new fully documented Objective C based source tree to host the Squeak VM on the iPhone and as a 64bit VM on OS-X. Likely this *might* take longer and it *hinges* on the ability to get funding from various sources for the effort. So funding offers are welcome. Not only is there VM support work involved, one needs to adapt to the multi-touch paradigm and become much less keyboard input orientated, plus use platform widgets for selection input. Helpfully the folks from Impara have agreed to take on some of that effort, and I'm sure they could use some funding to speed that process. People who are interested in offering Squeak based applications either via the free store, or selling via the paid store are welcome to contact me, likely I will provide for a fee a support agreement for the base iPhone VM and arrange sell-thru opportunities for paid applications. Sadly because of Apple's legal obligations not all application types and general Squeak functionality is acceptable to Apple for sale thru the store, or even offered via the free store. The list of "tho shall not do" is quite lengthy. Still I think there is an opportunity to deliver interesting Squeak based applications on the iPhone and iPod Touch. After 15 days of work just to cross check feasibility I can offer up the attached image of Squeak 3.4 running on an iPod Touch, I could have picked a 3.10 image, but the 3.4 screen below is more visually exciting. At the current 20 days of work I have screen orientation working (mostly), drawing, basic touching to mouse event translation, suffered thru 3 beta versions of the SDK, and posted a few interesting bug reports with Apple, and yes likely behind in my estimated timetable. Still as the other developers here at WWDC 08 (yes I am in SF at the moment) have noted getting something up and running is fast, it's just the other painful 10%... For the curious the VM that I have built & somewhat tuned does about 21,548,821 bytecode/sec; and 564,465 sends/sec Digging in the history books this is equivalent to a 233Mhz 603e powerbook. If you are excited about running your Squeak app on the iPhone, think hard about the meaning of these numbers... Also consider that 64MB of memory use is pushing the Apple's imposed safety limits right to the max. -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

16 30

Units package
by Cesar Rabak 24 Jun '08

24 Jun '08

I'm doing some test with the Units package and the results are puzzling me: In a pristine 3.10.2-7179-basic image, I installed Units version 4 via Universe. I run the UnitsTest via SUnit Runner and all the 8 tests run green. So far OK! Now if I copy to a Workspace from the source of the UnitsTest>>testAdd the following snippet: u := (14 units: #feet) + (10 units: #meters). If I print the whole expression I get '46.8083989501312 feet' as expected: Now when I attempt to make any other thing with the "u" object, like inspecting it, I get a stack, with the Title "Error: My subclass should have overriden #hash. Now, the tests run OK in the SUnit and fail in the Workspace! Even attempting to use the object gets the same stack trace... I probably doing something grossly wrong here as it seems to basic to have eluded other users, but I cannot see what it is it! Can you please advise? -- Cesar Rabak GNU/Linux User 52247. Get counted: http://counter.li.org/

4 7

Bug in BytecodeGenerator>>#jump:if:
by André Wendt 24 Jun '08

24 Jun '08

Hi all, apologies if this doesn't belong here. Mantis is a usability-nightmare and I didn't know where else to report a bug in the NewCompiler. The corresponding ML on squeakfoundation.org hasn't been posted to in over six months. I've noticed that BytecodeGenerator>>#jump:if: has a bug when given a distance >= 1024. It states hi := distance // 256. and then goes on checking if hi < 8. If that's false, the jump is assumed to be too big. However, the check should be hi < 4. Assume the method gets an argument of 1024, and hi is 4. The following self nextPut: (Bytecodes at: #longJumpIfFalse) first + hi. generates bytecode 176, which is an arithmetic message send instead of a conditional jump. I've attached a changeset that checks both jump conditions for hi < 4. Regards, André

7 19

JSqueak, the erstwhile Potato, is out!
by Dan Ingalls 24 Jun '08

24 Jun '08

You can find it here: http://research.sun.com/projects/JSqueak/ It's in exactly the state I left it in 2006, so it still needs color and warpBlt support to be finished, and files/sockets, as desired. That said it's nicely compact, and it performs usably. The license is totally open MIT. There's a mail list to sign up for potato-specific items (oops I mean JSqueak;-), though some of that discussion (and possibly all) might be relevant and better located here. If so, use [JSqueak] in the subject so people can filter. Have fun! - Dan PS: If you have been using an unofficial version of the sources, please now replace them with these and discard the old ones. Thanks

5 6

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

Jump to page: