What is so special about Smalltalk? - Stack Overflow
WEBMay 26, 2010 · 94. Smalltalk was one of the earliest object-oriented (OO) languages (with others like Simula and Eiffel) and can be said to be extremely "pure" in an OO sense: Everything is an object and objects are only communicated with via the sending of messages. No primitives (no int s, boolean s etc)
smalltalk - How to read/write objects to a file? - Stack Overflow
WEBJan 11, 2016 · Note however that there are better ways to store structured data in files, e.g. STON (Smalltalk Object Notation, Smalltalk version of JSON) or XML. If you want to persist objects than you might want to checkout Fuel , StOMP (probably no longer supported) or any of the other object serializers.
smalltalk - Check if an object is an instance of a given class or of a ...
WEBDec 8, 2012 · 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 …
What's so special about message passing in Smalltalk?
WEBFeb 28, 2017 · In Smalltalk, you compile a new method by sending a message to a Compiler. In Smalltalk, a Debugger is opened in response to an unhandled exception by sending a message. All the exception handling is implemented in term of sending messages. In Smalltalk you can query the methods of a Class, or gather all its instances …
if statement - Smalltalk Variadic functions - Stack Overflow
WEBOct 24, 2010 · Smalltalk's keyword-like syntax for method calls inherently defines the arity of the method. There's no &rest pattern like in Common Lisp. You can of course have a method take a list, like BlockClosure>>valueWithArguments: but that's hardly the same thing. You might modify Compiler to support variadic method calls.
Why use Ruby instead of Smalltalk? - Stack Overflow
WEBAug 15, 2016 · 1) Smalltalk's RPN-like control flow by messages is like Lisp - it's regular and cool but weirds people out. 2) Ruby lets people write code using the idiomatic way people speak - do blah unless there's a reason not to. update rewrote the Smalltalk sample to actually be more legal code.. edited Apr 30, 2014 at 14:01.
Understanding weird logical operators in smalltalk
WEBNov 22, 2017 · Since the Smalltalk VM is stack based, this rule means that: The receiver is evaluated first and the result is pushed on the stack. The arguments are evaluated in order and their results pushed on the stack. The message is sent. Item 3 means that the method that the send invokes will find the receiver and the arguments in the stack, in the ...
Smalltalk: what's the difference between "&" and "and:"
WEBSep 14, 2021 · Welcome to Smalltalk! You are asking a good question that points out some subtle differences in expressions that are outside or inside blocks. The '&' message is a "binary" message so takes only one argument. In this case the argument is expected to be a Boolean or an expression that evaluates to a Boolean.
Smalltalk - is there something similar to && from C?
WEBFeb 26, 2017 · Conditional " and ing" can be achieved by using the & message, or the and: message. ifTrue: [ 'do something' ]. Using & as show above, the second part of the condition (secondBooleanExpression) is evaluated regardless of whether the first half evaluates to true or false. ifTrue: [ 'do something' ]. Using and:, on the other hand, the second part ...
Smalltalk - Print something for each 2 seconds - Stack Overflow
WEBDec 2, 2012 · You forked all 5 processes at once so that all 5 delays ends at the same time. To print every 2 seconds from the background, rather fork a whole loop in a separate process: |i delay|. [. i := 0. [i < 5] whileTrue: [. delay := Delay forSeconds: 2. delay wait. Transcript show: '2 seconds are up'.