Concurrent Smalltalk extension to VisualWorks 2.0 
Author Message
 Concurrent Smalltalk extension to VisualWorks 2.0

Greetings,

Any information regarding concurrent Smalltalk would be most
appreciated.

Thank you in advance for your assistance.

Regards,

Farhan Malik



Tue, 08 Jul 1997 22:32:59 GMT  
 Concurrent Smalltalk extension to VisualWorks 2.0

 >Any information regarding concurrent smalltalk would be most
 >appreciated.

Check out Actalk by Jean-Pierre Briot.  I'm not sure if its in the
archive but it is at
   ftp://camille.is.s.u-tokyo.ac.jp/pub/members/briot/actalk

I don't think that that it has been ported to VW2.0.  Apparently there
were a few little changes that affect it and they have not yet been
resolved.

JEff

--
ato de, |m        -- "But I ain't a big enough man to do
                      anything other than think"  -- The the



Thu, 10 Jul 1997 23:14:01 GMT  
 Concurrent Smalltalk extension to VisualWorks 2.0
In VW 2.0 there is no method to return a Number as a String (asString)
or as a Text (asText).

I have added the obvious following methods. They are so obvious that I
really
wonder if I have not missed a side effect somewhere. Any comment will
be
appreciated.

-----
asString

| stream |

stream :=  WriteStream on: ( String new ).
self printOn: stream.
^ stream contents

-----
asText

^ Text fromString: ( self asString )

Thierry

.....................................................................
. Thierry Thelliez                   Los Alamos National Laboratory .

.   Voice: (505) 665 8631               MS M982 Los Alamos NM 87545 .
.     Fax: (505) 665 8633                                       USA .
.     URL: http://www.lanl.gov:52271/?tgt                           .
.....................................................................



Fri, 11 Jul 1997 11:35:29 GMT  
 Concurrent Smalltalk extension to VisualWorks 2.0

What about printString,that method should do the job.
(I only have VW1.0, so I am not sure).

                        Kjell Larsen,Univ. of Oslo



Sat, 12 Jul 1997 00:46:53 GMT  
 Concurrent Smalltalk extension to VisualWorks 2.0

Quote:
Thelliez) writes:
> In VW 2.0 there is no method to return a Number as a String (asString)
> or as a Text (asText).

I have used displayString instead--it's defined at the Object level, so  
hopefully it's implemented across most classes.

kit transue



Sat, 12 Jul 1997 01:13:58 GMT  
 Concurrent Smalltalk extension to VisualWorks 2.0

   In VW 2.0 there is no method to return a Number as a String (asString)
   or as a Text (asText).

Converting a number to a string is accomplished using #printString.
#asString is only implemented on classes that have an implicit
string-like quality...CharacterArray, ComposedText, Symbol,
IntegerArray, etc.  The same goes for the implementation of #asText
(with the notable execption of the fact that Filename>>asText does NOT
return a Text, a bug in my opinion).

   asString

   | stream |

   stream :=  WriteStream on: ( String new ).
   self printOn: stream.
   ^ stream contents

This is a near 100% copy of the #printString method.  If you still
feel the need for an #asString then it would be better style to change
the body of the above method to read only '^self printString'.

It is not uncommon (and is part of the additions to base classes made
by ENVY) to implement an #asString method that returns 'self printString'
on Object.  This is then inherited by all classes.

t
--

Arbor Intelligent Systems                       Voice:     (313) 996-4238
   "I am meeting with the Tremendous Learning Curve and am unable to smite
       same with my Great Foo-Foo Sword of Much Ouch-making and Power."



Sat, 12 Jul 1997 22:18:55 GMT  
 Concurrent Smalltalk extension to VisualWorks 2.0

Quote:
>In VW 2.0 there is no method to return a Number as a String (asString)
>or as a Text (asText).

Number inherits #printString from Object.  It achieves the affect
that you expect from #asString.

Dave



Sun, 13 Jul 1997 04:21:05 GMT  
 Concurrent Smalltalk extension to VisualWorks 2.0

#printString, #asString, #displayString, #label, #title, etc...
could all be used to get a lexical representation of an object
for human consumption.  To avoid confusion between the selectors
lets attach a conceptualization to the semantics that are desired
for each selector/method pair.

Here are my thoughts on the following selectors:

  #printString answers a string for debugging purposed only.
  #asString, #displayString, #label, #title, etc. are application
  specific methods for extracting an attractive and useful string
  when displayed within a suitable context.

If displayString is implemented as ^self printString displayString
is still responsible for answer an attractive and useful string.

Ted Eiles --- GrokIt Object Engineering, North Carolina



Thu, 17 Jul 1997 10:50:14 GMT  
 
 [ 9 post ] 

 Relevant Pages 

1. US - FL - S.E.****VISUALWORKS/SMALLTALK/VISUALWORKS/SMALLTALK****CONTRACT

2. FS: VisualWorks Smalltalk 2.0 for Win3.1/Win95

3. VisualWorks 2.0 Smalltalk Opportunity in Palo Alto, CA

4. VisualWorks Widgets for VisualWorks 2.0 and 2.5

5. VisualKit 1.5 for VisualWorks 2.0 or VisualWorks 2.5

6. VisualWorks 2.0 vs VisualWorks 2.5

7. Info on Distributed Smalltalk, Concurrent Smalltalk

8. ST VisualWorks- Smalltalk, VisualWorks and Envy

9. Concurrent/Distributed Oberon extensions

10. US-TN Intermediate VisualWorks smalltalk and HP-Distributed Smalltalk opportunities

11. Disributed Smalltalk and OODBMS for VisualWorks and ObjectWorks\Smalltalk

12. Concurrent Smalltalk

 

 
Powered by phpBB® Forum Software