Vm-dev July 2008

vm-dev@lists.squeakfoundation.org

14 participants
14 discussions

Mac OS - path and file name of the VM app
by Robert Krahn 10 Jul '08

10 Jul '08

Hi! I am trying to create a sar file which moves a .bundle directory into the VM app. Let's assume that my SqueakVM is /Applications/ SqueakVM.app. Then I would have to move my bundle directory into / Applications/SqueakVM.app/Contents/Resources/. I get the path to the vm app with SmalltalkImage current vmPath. But this only evaluates to /Applications/. How do I get the name of the app directory? Thanks, Robert

3 3

MemoryAccess
by David T. Lewis 07 Jul '08

07 Jul '08

FYI, repeating from recent discussions on squeak-dev list: Over the last 2 weeks I've been playing around with replacing the memory access macros in sqMemoryAccess.h with equivalent Smalltalk slang. Along the way I found and fixed several slang issues that prevented inlining of methods with C declarations. I posted a snapshot of this on squeak-dev in response to a question there, so I'm mentioning here on vm-dev for the record. I have the memory access methods working now, and with all the slang inlining applied I'm seeing about 20% of the performance of the interpreter using C macros. I don't know if it will be possible or practical to achieve the performance of the CPP macros, but it does seem useful to be able to generate the VM entirely in C without macros as an aid to debugging and possibly profiling The slang translation bug fixes will be worth capturing on Mantis, and I'll do so within the next couple of weeks. The thread on squeak-dev, including the change sets, is here: http://lists.squeakfoundation.org/pipermail/squeak-dev/2008-July/129982.html Dave

1 0

[Squeak-fr] Master 'Software for embedded systems' -- Master Systèmes Embarqués à Brest - France
by Damien Picard 03 Jul '08

03 Jul '08

(sorry for the multiple copies) ------------------------------ University of Brest (UBO) plans to open two new *Master of Sciences* automn 2008: 'LSE : Logiciel pour les Systèmes Embarqués' (Software for embedded systems) 'iMARS : Microtechnologies, Architecture, Réseaux et Systèmes de communications' (Microtechnologies, Architecture, Networks and communication systems) LSE and iMARS include one course in object oriented programming and methods that covers advanced topics teached on Smalltalk-80 platforms with in mind architectural support of execution, code and hardware synthesis. This course is given by a research group (*) developing tools (circuit and system level) in relation with innovative projects such as reconfigurable system on chips and non-CMOS emergent technologies (lot of Smalltalk programming on hot topics!). Master LSE is a computer science curriculum. Flyer : http://as.univ-brest.fr/flyer_master_fr.pdf<http://as.univ-brest.fr/Depot/flyer_master_es.pdf> student application and program : http://dept-info.univ-brest.fr/pages/master-systeme-embarque.htm contact: *pottier at univ - brest . fr * Master iMARS is a regional merge of electronics/communication and CS curricula: http://www.insa-rennes.fr/master2-imars *contact: Noel . Tanguy at univ - brest . fr * ------------------------------ (*) Architectures et Systemes, LabSTICC, UMR CNRS 3192 _______________________________________________ Squeak-fr mailing list Squeak-fr(a)lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/squeak-fr -- Damien Picard

1 0

Socket listening
by Bert Freudenberg 01 Jul '08

01 Jul '08

Ian, and folks, I'm trying to write a more robust Etoys server for OLPC, and found some surprising listening behavior. The snippet below tries to listen on the same port twice. I'd have expected to get an error on the second listening attempt. However, on both Linux and Mac OS X (John's VM) I get back #(6060 57855) which means the second socket listens successfully, but on a random port. I verified it is actually listening there using lsof. The SO_REUSEADDR option does not make any difference, btw. So, is this intended behavior? If not, will we change it? In my actual use case I would have tried to iterate through some ports to find an unbound one, so in this particular case the behavior is convenient for me. But I think I should not rely on it. Also, the same code gives an error (as expected) on Windows. - Bert - [ p := 6060. s1 := Socket newTCP. s1 setOption: 'SO_REUSEADDR' value: 0. s1 listenOn: p. s2 := Socket newTCP. s2 setOption: 'SO_REUSEADDR' value: 0. s2 listenOn: p. { s1 isValid ifTrue: [s1 port]. s2 isValid ifTrue: [s2 port] } ] ensure: [ s1 destroy. s2 destroy. ]

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Vm-dev July 2008