What is so special about Smalltalk? [closed] - Stack Overflow Using Smalltalk as a prototyping tool is where my interest lies: I think that given a new problem, different approaches to solving it can be tried and validated very quickly and easily in a Smalltalk environment, and once the desired solution is found it should be relatively mechanical to convert it to Java C++ C# etc etc
smalltalk - How to read write objects to a file? - Stack Overflow I also went through a lot of sites with broken links etc, but I don't seem to be able to find a way to write to a file in smalltalk I tried this (and other things, but they come down to the same): out := 'newFile' asFileName writeStream d associationsDo: [ :assoc | out nextPutAll: assoc key asString; nextPut: $, ; nextPutAll: assoc value
What is the correct way to define and call functions in GNU Smalltalk . . . When trying to learn smalltalk, use a smalltalk environment Don't use a command line interface, don't use an on-line web tool Both are very useful, but not to learn smalltalk They don't provide the feedback you need to learn smalltalk good and fast If it doesn't allow you to write most of your code in the debugger, you won't learn smalltalk
Why ifTrue and ifFalse are not separated by ; in Smalltalk? The problem of many Smalltalk beginners is that they think of ifXXX: as syntax, where it is actually a message send which generates value Also, the semi is not a statement separator as in many previously learned languages, but a sequencing message send construct
How is Smalltalks whileTrue message implemented behind the scenes? By the way, as the Smalltalk language standard (which does not really exist) does not force implementations to be tail-call-eliminating (in contrast to Scheme, for example), the recursive implementation in VW is not really useful for performing or interpretation (unless the compiler-cheat is standardized) An alternative without recursion could be:
smalltalk - Check if an object is an instance of a given class or of a . . . I agree with Igor Moreover, "nicest and most elegant" is in the eye of the beholder What isInteger and friends do is definitely faster as they are a single message send that immediately returns true false versus isKindOf: which has to loop up the class hierarchy
smalltalk - How is Small talks message to:do: implemented behind the . . . All Smalltalk messages follow the pattern <receiver> <message> In this case the receiver is 1 (a subinstance of Number), and the message is to:do: You can browse class Number and see the implementation of to:do: right there: to: stop do: aBlock | nextValue | nextValue := self
What Syntax for file-based Smalltalks are there? - Stack Overflow Additionally there is the Smalltalk Interchange Format (SIF) which is specified by the ANSI Smalltalk standard, which is similar to the chunk format but incorporates some additional metadata and structure I know that there is a reader for SIF in GST, but I'm not sure if VisualWorks or Squeak have readers for this format