Monticello Extension Categorization Rules

I'm curious about the rules for categorizing Monticello extension methods. I notice (in the Pharo image) some of them have all lowercase letters, such as * package name, and others in the usual case, for example * Package-Name. In addition, I’m interested in learning about subclassification in order to add a β€œreal” category after the package name, for example: * Type of access to packages, for example, when expanding with accessories of any class, is it supported or dangerous and can be broken?

Update: if I did something wrong, I would like to know why instead of downvotes no comments.

+5
source share
1 answer

Comparison of package names is not case sensitive. Traditionally, Smalltalk uses lowercase categories. You can also use.

There is no harm in adding the suffixes '-foo-bar baz' to the category name.

Please note that this is not built into Monticello. It uses PackageInfo to determine which definitions are part of a given package. Browse PackageInfo enlightens.

In addition, matching by name is by default only. The PackageInfo subclass may override this, but this is very rare.

+6
source

Source: https://habr.com/ru/post/1216064/


All Articles