Loading ...
Sorry, an error occurred while loading the content.
220
Re: *Google Hosting Ready* Never mind it was temporary. Ron _____ From: strongtalk@yahoogroups.com [mailto:strongtalk@yahoogroups.com] On Behalf Of Ron Teitelbaum Sent: Thursday,
Ron Teitelbaum
Sep 28, 2006
#220
 
219
Re: *Google Hosting Ready* Dave, I tried to join Google's strongtalk group and it failed. It could be a temporary problem but I thought I'd let you know. Ron _____ From:
Ron Teitelbaum
Sep 28, 2006
#219
 
218
Re: *How to Contribute Code* ... What WebKit (Apple's browser core) does is: * submitter opens a bug describing the problem and attaches a patch * he sets the "review required" flag with
Krzysztof Kowalczyk
Sep 28, 2006
#218
 
Fetching Sponsored Content...
217
*** Discussion Group Moving *** Hi everyone, We are finally ready to move our discussion over to Google Groups, at strongtalk-general .
davegriswold9
Sep 27, 2006
#217
 
216
*Development Direction* Ok, everyone, we need to establish our development priorities and direction, so here are my ideas to kick-off our discussion: Strongtalk Project Direction
davegriswold9
Sep 27, 2006
#216
 
215
*How to Contribute Code* Hi everyone, Until now we have been unable to accept source contributions, since we didn't have the legal boilerplate in place to ensure the licensng stays
davegriswold9
Sep 27, 2006
#215
 
214
*Google Hosting Ready* Hi everyone, I think we are finally ready to go! Following will be a series of kick-off emails. Hosting The project is now hosted at Google Code, project
davegriswold9
Sep 27, 2006
#214
 
213
Re: *Strongtalk Project Status Report* Sorry, I guess I don't understand your question. If you subscribe to the group you can get it all as email. -Dave
davegriswold9
Sep 25, 2006
#213
 
212
Re: *Strongtalk Project Status Report* ... Any chance of mirroring the google group on e-mail? Adelle.
Adelle Hartley
Sep 25, 2006
#212
 
211
*Strongtalk Project Status Report* Hi everyone, Here is a quick status report on what is going on: - I'm sorry for the long silence; I'm working on this part time and have been doing a lot of
davegriswold9
Sep 25, 2006
#211
 
210
Re: Differences in the license files Hi Carlo, - As Gilad pointed out, the file sourceLicense.html is the single actual license. The others are obsolete, from the previous release. - The 1.0.1
davegriswold9
Sep 24, 2006
#210
 
209
Re: Sound support? Yes. There is a mechanism for external function calls which could be used to invoke any system functionality for sound (or anything else), but there is no
Gilad Bracha
Sep 24, 2006
#209
 
208
Re: Differences in the license files Carlo, sourceLicense is the correct license, as you note.
Gilad Bracha
Sep 24, 2006
#208
 
207
Sound support? Is the assumption correct that there is presently no sound support in Strongtalk? Regards, Lothar
Lothar Schenk
Sep 24, 2006
#207
 
206
Re: Differences in the license files I managed to spell several things inorrectly. Among other things, I meant to say below [...] Neither difference changes the meaning, most importantly they do
Carlo Dapor
Sep 24, 2006
#206
 
Fetching Sponsored Content...
205
Differences in the license files There is still a small differences between sourceLicense.html documentation/sourceLicense.html vm-license.txt vm/vm-license.txt Observations: The first one I
Carlo Dapor
Sep 24, 2006
#205
 
204
Re: become: ... Another possibility is to clone the loop then check if the assumptions are still true in your method re-entry code (1). So long as the compiled code is
Bryce Kampjes
Sep 21, 2006
#204
 
203
Re: become: Hi Eliot, I don't see this as being a big problem in Strongtalk. As you pointed out, deoptimization takes care of the problem nicely. That is in fact one
davegriswold9
Sep 20, 2006
#203
 
202
Re: become: ... IMO, the issue with become: isn't how its implemented at the GC level but how it, and the other meta-behavioural prim,itives, ineract with the optimizer.
eliotemiranda
Sep 20, 2006
#202
 
201
Re: References and latest sources ... URLs pointing to the ... technology used in the ... Hi Roman, here's the list of references I used in a sketch I did on doing adaptive optimization at the
eliotemiranda
Sep 20, 2006
#201
 
200
Re: What will be the licensing policy for future contributions to S ... The only point in getting an explicit assignment of copyright is so that a single copyright owner exists who can sue in case of breach. However, breaching
John Cowan
Sep 19, 2006
#200
 
199
Re: What will be the licensing policy for future contributions to S ... What apple folks did for their webkit open-source core is a modification of bugzilla: when you attach a patch to the bug, you have to check a box saying
Krzysztof Kowalczyk
Sep 19, 2006
#199
 
198
Re: What will be the licensing policy for future contributions to S + 1 This would be a good thing to talk to Dan at the Software Freedom Law Center about. SFLC provides free legal services and representation for open source
Ron Teitelbaum
Sep 19, 2006
#198
 
197
Re: What will be the licensing policy for future contributions to S Yes, I am already aware of this issue. I have been investigating whether a simple attachement of the license to the contributions is all that is needed, or
davegriswold9
Sep 19, 2006
#197
 
196
*corrected source release* Hi everyone, I have posted the new source release from Sun on the downloads page at http://www.strongtalk.org/downloads/strongtalk-source-1.0.1.zip This is the
davegriswold9
Sep 19, 2006
#196
 
195
What will be the licensing policy for future contributions to Stron First of all, since this is my first post on the list, let me express my deep appreciation for making this software available, for the groundbreaking new ideas
Lothar Schenk
Sep 19, 2006
#195
 
194
New file uploaded to strongtalk Hello, This email message is a notification to let you know that a file has been uploaded to the Files area of the strongtalk group. File :
strongtalk@yahoogroups.com
Sep 19, 2006
#194
 
Fetching Sponsored Content...
193
Re: VMCrash - Access Violation ... I simply rewrote the supplied Makefile, so I don't need UN*X utilities. I will upload the modified Makefile now. When time permits, I will upload the
pahihu
Sep 19, 2006
#193
 
192
Re: Smalltalk source control ... most recently, svn http://squeakvm.org/svn/squeak/ (Although several take the source and modify for their own usage) For building plugins,
bradallenfuller
Sep 18, 2006
#192
 
191
Re: Smalltalk source control ... In Squeak, most people use Monticello, which is a versioning system that Avi Bryant and I wrote a few years ago. It does native versioning and merging of
Colin Putney
Sep 18, 2006
#191
 
View First Topic Go to View Last Topic
Loading 1 - 30 of total 220 messages