Smalltalk current createPackage: 'Kernel-Methods' properties: #{}! Object subclass: #CompiledMethod instanceVariableNames: '' category: 'Kernel-Methods'! !CompiledMethod commentStamp! CompiledMethod hold the source and compiled code of a class method. You can get a CompiledMethod using `Behavior>>methodAt:` String methodAt: 'lines' and read the source code (String methodAt: 'lines') source See referenced classes: (String methodAt: 'lines') referencedClasses or messages sent from this method: (String methodAt: 'lines') messageSends! !CompiledMethod methodsFor: 'accessing'! source ^(self basicAt: 'source') ifNil: [''] ! source: aString self basicAt: 'source' put: aString ! category ^(self basicAt: 'category') ifNil: [''] ! category: aString self basicAt: 'category' put: aString ! selector ^self basicAt: 'selector' ! selector: aString self basicAt: 'selector' put: aString ! fn ^self basicAt: 'fn' ! fn: aBlock self basicAt: 'fn' put: aBlock ! messageSends ^self basicAt: 'messageSends' ! methodClass ^self basicAt: 'methodClass' ! referencedClasses ^self basicAt: 'referencedClasses' ! arguments ! ! Object subclass: #BlockClosure instanceVariableNames: '' category: 'Kernel-Methods'! !BlockClosure commentStamp! A BlockClosure is a lexical closure. The JavaScript representation is a function. A BlockClosure is evaluated with the `#value*` methods in the 'evaluating' protocol.! !BlockClosure methodsFor: 'accessing'! compiledSource ! numArgs ! ! !BlockClosure methodsFor: 'controlling'! whileTrue: aBlock "inlined in the Compiler" ! whileFalse: aBlock "inlined in the Compiler" ! whileFalse "inlined in the Compiler" self whileFalse: [] ! whileTrue "inlined in the Compiler" self whileTrue: [] ! ! !BlockClosure methodsFor: 'error handling'! on: anErrorClass do: aBlock ^self try: self catch: [:error | (error isKindOf: anErrorClass) ifTrue: [aBlock value: error] ifFalse: [error signal]] ! ! !BlockClosure methodsFor: 'evaluating'! value "inlined in the Compiler" ! value: anArg "inlined in the Compiler" ! value: firstArg value: secondArg "inlined in the Compiler" ! value: firstArg value: secondArg value: thirdArg "inlined in the Compiler" ! valueWithPossibleArguments: aCollection ! new "Use the receiver as a JS constructor. *Do not* use this method to instanciate Smalltalk objects!!" ! applyTo: anObject arguments: aCollection ! timeToRun "Answer the number of milliseconds taken to execute this block." ^ Date millisecondsToRun: self ! ensure: aBlock | success | success := false. ^[self value. success := true. aBlock value] on: Error do: [:ex | success ifFalse: [aBlock value]. ex signal] ! newValue: anObject "Use the receiver as a JS constructor. *Do not* use this method to instanciate Smalltalk objects!!" ! newValue: anObject value: anObject2 "Use the receiver as a JS constructor. *Do not* use this method to instanciate Smalltalk objects!!" ! newValue: anObject value: anObject2 value: anObject3 "Use the receiver as a JS constructor. *Do not* use this method to instanciate Smalltalk objects!!" ! ! !BlockClosure methodsFor: 'timeout/interval'! valueWithTimeout: aNumber ! valueWithInterval: aNumber ! ! Object subclass: #MethodContext instanceVariableNames: '' category: 'Kernel-Methods'! !MethodContext commentStamp! MethodContext holds all the dynamic state associated with the execution of either a method activation resulting from a message send. That is used to build the call stack while debugging. MethodContext instances are JavaScript `SmalltalkMethodContext` objects defined in boot.js Current limitation: MethodContext instances are not created on Block evaluation. That means it's actually impossible to debug inside a Block.! !MethodContext methodsFor: 'accessing'! receiver ! selector ! home ! temps ! printString ^super printString, '(', self asString, ')' ! asString ^self receiver class printString, ' >> ', self selector ! ! Object subclass: #Message instanceVariableNames: 'selector arguments' category: 'Kernel-Methods'! !Message commentStamp! Generally, the system does not use instances of Message for efficiency reasons. However, when a message is not understood by its receiver, the interpreter will make up an instance of it in order to capture the information involved in an actual message transmission. This instance is sent it as an argument with the message `doesNotUnderstand:` to the receiver. See boot.js, `messageNotUnderstood` and its counterpart `Object>>doesNotUnderstand:`! !Message methodsFor: 'accessing'! selector ^selector ! selector: aString selector := aString ! arguments: anArray arguments := anArray ! arguments ^arguments ! ! !Message methodsFor: 'printing'! printString ^ String streamContents: [:aStream| aStream nextPutAll: super printString; nextPutAll: '('; nextPutAll: selector; nextPutAll: ')' ] ! ! !Message class methodsFor: 'instance creation'! selector: aString arguments: anArray ^self new selector: aString; arguments: anArray; yourself ! !