Tag Archives: Model Action

More about “new”

By Wyrd Smythe on | Leave a comment

Picking up the topic of Model implementation two years later, some further thoughts about the new method as well as about the set and get methods.

The summary here is that all three are virtual methods built into the implementation. They have to be to handle the under-the-hood aspects of Instances. They can be “extended” by user code, but not over-ridden.

Continue reading →

Posted in: Implementation | Tagged: , , , , , ,

Singleton Messages and Actions

By Wyrd Smythe on | Leave a comment

A recommended idiom involves defining Actions to implement Singleton Messages. This cleans up source code by removing the need to use the semi-colon, and shifts possible “Unknown Message” errors to data type errors, some of which can be detected at compile time.

Continue reading →

Posted in: Basics | Tagged: , , , ,

Action Walkthrough, part 4

By Wyrd Smythe on | Leave a comment

While not really part of the Action walk-through, per se, the sequence of events involving Messages still involves Actions, because Model Actions implement message behaviors. Therefore, nearly all messages ultimately result invoking some (Model) Action.

This article details the sequence of events involving Message objects.

Continue reading →

Posted in: Implementation | Tagged: , , , , , ,

Action Walkthrough, part 3

By Wyrd Smythe on | Leave a comment

The discussion of how an Action works continues with a detailed list of Action start-up events. The example code for the Action under discussion is shown in the first article.

Continue reading →

Posted in: Implementation | Tagged: , , , , ,

Action Walkthrough, part 2

By Wyrd Smythe on | Leave a comment

There are two protocols for invoking Actions that are under consideration. Both are described here. The example code for the discussion was shown in the previous article.

Continue reading →

Posted in: Implementation | Tagged: , , , ,

Action Walkthrough, part 1

By Wyrd Smythe on | Leave a comment

This post series explores an Action in detail with emphasis on the Instance objects, especially the dynamic (temporary) ones. Posts are broken up mainly for size considerations.

Continue reading →

Posted in: Design | Tagged: , , , , , , ,

Casting Values

By Wyrd Smythe on | 1 Comment

There is the situation when an operation takes multiple operands, and one (or more) of those operands are inappropriate for the operation. For example, suppose an integer add operation was passed an integer object and an open file object? There is generally no “add” semantic for an integer and a file.

Total incompatibility results in a run-time error, but sometimes values are compatible enough for the operation to proceed. How the system accomplishes that often involves casting one value into another.

Continue reading →

Posted in: Basics | Tagged: , , , , ,

Invoking Actions

By Wyrd Smythe on | Leave a comment

Finally, a post not filed under Basics!  I’m in a BOOL development mode (they come and go over the years), so more advanced topics are likely. I’m making what feels like excellent progress. Maybe once this phase completes, I can set down to the business of really documenting BOOL here.  (Assuming the development doesn’t end in frustration and tears and I put the whole mess on the shelf for another few years.)

I’ve been mucking about with my Python implementation trying to work my way through an implementation aspect I’ve never been able to see clearly. It has to do with how BOOL invokes code sub-units. We’re talking about “calling” what are variously called: sub-routines, routines, functions, procedures, methods or sub-programs. At least the term “call” is fairly global; in fact, the generic term for these things is “callable unit.”

Continue reading →

Posted in: Implementation | Tagged: , , , , , , ,
Design a site like this with WordPress.com
Get started