stz

break

[self my-method: arg] [:MyClass, :Integer -> ø |
  [ -> break |
    arg = 1 then: [self do-thing-one; break];
    arg = 2 then: [self do-thing-two; break];
    arg = 3 then: [self do-thing-three-fall-through];
    arg ≤ 4 then: [self do-thing-four; break];
    self do-thing-default;
  ]
  self do-other-stuff]

This falls out of the current syntax nicely. You can even assign from the 'switch' statement. You can test whatever you want and you can even return from an outer scope if so desired.

Very short post. Just had to jot this down.

coroutines using tina

The idea that we can support different kinds of coroutines libraries in STZ makes me happy. So much so I think it's worth abandoning the Smalltalk-80 fork API and providing the libraries as-is, with some nice wrapping to clean them up. Tina provides us not only with asynchronous

coroutines using minicoro

Let's approach coroutines as something we utilise rather than get in the language. Using the minicoro library and the ability to use C code directly from STZ, let's see what it'll take to utilise. Starting with the basics - let's create a

another attempt

It will come as no surprise to people who know me that using <> as a grouping mechanism for any kind of information is distasteful. It visually conflicts with less than, greater than, etc. It's already visually conflicting with select> and do>. I made all

not ambiguous, just displeasing

(Integer | 1,) (my-object | b | c) (MyType | my-object | b | c,) The | is used in a lot of places to delineate between 'the type' and 'the code' inside of list creation (type | ...elements...), methods and blocks [type | ...code...], new object {type | ...code list...}. We have also been using

Read more

coroutines using tina

coroutines using minicoro

another attempt

not ambiguous, just displeasing