Self-interest August 1992

self-interest@lists.selflanguage.org

26 participants
29 discussions

Re: porting self
by David.Ungar＠Eng.Sun.COM 19 Aug '92

19 Aug '92

using gcc for Self seems farfetched to me. IN addition to GC, you would have to figure out how to support blocks, debugging information, inline caching and who-knows-what-else. Maybe there is a clever way that I just don't see. Dave > From owner-self-interest(a)self.stanford.edu Tue Aug 18 14:43:34 1992 > Date: Tue, 18 Aug 92 17:29:53 -0400 > To: self-interest(a)self.stanford.edu > Cc: Urs.Hoelzle@Eng > Subject: porting self > Reply-To: moss(a)cs.umass.edu > > >>>>> On Tue, 18 Aug 92 13:52:53 PDT, Urs.Hoelzle(a)Eng.Sun.COM said: > > Urs.Hoelzle> How about using the gcc backend? > > Urs.Hoelzle> We have considered that, but it's not as easy as it seems. One > Urs.Hoelzle> problem is that gcc's backend needs to be taught about garbage > Urs.Hoelzle> collection. Some people at UMass (Eliot Mass' group) are doing > Urs.Hoelzle> this for Modula-3, but as far as I know it's not working yet (and > Urs.Hoelzle> they have put a lot of effort in it). The other problem is that > Urs.Hoelzle> gcc might be too slow - in Self, compilation happens at run-time, > Urs.Hoelzle> so you'd like to keep compile pauses in the millisecond area, and > Urs.Hoelzle> I'm not sure if gcc as a traditional batch compiler is up to > Urs.Hoelzle> that. > > Actually, it *is* working (gc support in GNU Modula-3, using gcc's back end). > We would be thrilled if some other people tried to use this technology, though > I would say we're probably not so far along that we're ready to release code > to just anybody (still needs some cleanup I think). We would also be pleased > to help someone (say a graduate student at Stanford) get our gc toolkit > (implemented) and mature object space collector (not yet implemented) going > with Self. > > As for the speed issue, perhaps if you kept a gcc fork around, designed to > receive methods for compilation on standard input and to deliver the compiled > code to standard output you could get reasonable response. Probably not as > fast as what you have now, but perhaps good enough (especially on a > multiprocessor?). > > Regards -- Eliot > > J. Eliot B. Moss, Associate Professor > Department of Computer Science > Lederle Graduate Research Center > University of Massachusetts > Amherst, MA 01003 > (413) 545-4206, 545-1249 (fax); Moss(a)cs.umass.edu >

1 0

Re: Self 2.0 being ported?
by clp＠home.HarvardSq.COM 18 Aug '92

18 Aug '92

I would LOVE to hear of people interested in a port to the NeXT machine. I am going to begin one ASAP myself unless I hear back from some of you. Anyone who would like to help, drop me a line...it's a long-term goal, so I may not get to it right away, but I WANT IT BAD!! Charles

1 0

subscribe
by timborn＠iesde.att.com 18 Aug '92

18 Aug '92

I'd like to subscribe to the "random ramblings about Self". Thanks, -tim t.born(a)att.com

1 0

Self 2.0: bug report
by Lars.Bak＠Eng.Sun.COM 12 Aug '92

12 Aug '92

Dear Self user Release 2.0 has a bug in the self code implementing the self debugger. The error can occur when an activation record is displayed and will result in a stack trace. On the ftp server (self.stanford.edu) the file Self-2.0/KNOWN-BUGS explains how to fix the error. //Lars Bak

1 0

Self 2.0 being ported?
by Sean Levy 11 Aug '92

11 Aug '92

Is there any movement/interest in the Self group to port Self to architectures other than Sun? The inclusion of source code with the 2.0 release is a welcome blessing, but one of my main criteria (and the main reason why I decided not to go with Self for the coding of my project but went off and rolled my own prototype-based system) is that it work on as many platforms as humanly possible and be (reasonably) easily portable. I can't be locked in to sparcs (or any one architecture) for a number of reasons. The ideas in Self have been my inspriation in a number of ways ever since I read them; unfortunately, their expression as implementation have not been useful to me. If only for the ideas, the Self group should be commended. If I can actually jump on the bandwagon and use their code, so much the better! Cheers, -- Sean -- Sean Levy, n-dim Group, EDRC, CMU, 5000 Forbes Ave, PGH, PA 15213 Email: snl+(a)cmu.edu, Phone: +1 412 268 5221, Fax: +1 412 268 5229

2 1

Re: Problem after installing Self 2.0
by Ole Agesen 11 Aug '92

11 Aug '92

Hi Geoff. I think your problems may be caused by a typo in the selfrc file. We discovered this typo shortly after sending out the announcement. The typo was fixed very quickly so most of you in self-interest should not encounter any problems, but if you are among the few that have gotten the bad version, here is the diff between selfrc with and without the typo: 68c68 < the trace if desired.' --- > the trace if desired." In other words, the single-quote should be changed to a duoble-quote. Good luck! Ole P.S. Note that the selfrc file is copied to ~/.selfrc by the SelfUserSetup, script so you have to fix the typo both in selfrc and your ~/.selfrc. Or you can re-install Self, if that seems easier.

1 0

Problem after installing Self 2.0
by wyant＠centerline.com 11 Aug '92

11 Aug '92

I installed Self 2.0 according to the instructions, started it up and got the following error message: reading ~/.selfrc Self VM error: slot names must begin with a lowercase letter on line 78, character 6 of "~/.selfrc" This is the unmodified .selfrc as created by the installation. The line in question is: "Scheduler" <--- offending line "Prints all the processes known to the Self scheduler, including recent processes that have been suspended with an error, but not yet killed." jobs = (scheduler printProcessQueues. self). Any suggestions ? thanks in advance ! Geoff Wyant wyant(a)centerline.com Centerline Software, Inc. (Formerly Saber Software, Inc) 10 Fawcett Street Cambridge, Ma. 01238

1 0

sub
by Richard Everman 11 Aug '92

11 Aug '92

1 0

Announcing Self Release 2.0
by Ole.Agesen＠Eng.Sun.COM 10 Aug '92

10 Aug '92

Announcing Self Release 2.0 The Self Group at Sun Microsystems Laboratories, Inc., and Stanford University is pleased to announce Release 2.0 of the experimental object-oriented exploratory programming language Self. Release 2.0 introduces full source-level debugging of optimized code, adaptive optimization to shorten compile pauses, lightweight threads within Self, support for dynamically linking foreign functions, changing programs within Self, and the ability to run the experimental Self graphical browser under OpenWindows. Designed for expressive power and malleability, Self combines a pure, prototype-based object model with uniform access to state and behavior. Unlike other languages, Self allows objects to inherit state and to change their patterns of inheritance dynamically. Self's customizing compiler can generate very efficient code compared to other dynamically-typed object-oriented languages. Self Release 2.0 runs on Sun-3's and Sun-4's, but no longer has an optimizing compiler for the Sun-3 (and therefore runs slower on the Sun-3 than previous releases). This release is available free of charge and can be obtained via anonymous ftp from self.stanford.edu. Unlike previous releases, Release 2.0 includes all source code and is legally unencumbered (see the LICENSE file for legal information.) Also available for ftp are a number of papers published about Self. Finally, there is a mail group for those interested in random ramblings about Self, self-interest(a)self.stanford.edu. Send mail to self-request(a)self.stanford.edu to be added to it (please do not send such requests to the mailing list itself!). The Self Group at Sun Microsystems Laboratories, Inc. and Stanford University

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

1993

1992

1991

1990

Self-interest August 1992