<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> My sentence was hard to understand, it should read: <blockquote> Another interest of the builder is to have just one pragma (<worldMenu>) or method name (#worldMenuSpec: aBuilder) for the whole menu hierarchy (including menu and submenus definition), and a different symbol name for each menu and submenus. </blockquote> Thinking about this, you can't define all the menus with several methods sharing the same name (here in the example worldMenuSpec:), the methods will have to be spread in different classes, not practical. Now I understand very clearly why the author of the Pharo menu registry used pragma to select the methods providing the menu definition. Oh by the way, pragma are discoverable as easily as method implementors can be: Smalltalk browseAllSelect: [:m| m pragmas anySatisfy: [:p | p key = #primitive:]]. (Hernan courtesy) Hilaire <div class="moz-cite-prefix">Le 28/05/2022 à 11:23, Hilaire Fernandes a écrit : </div> <blockquote type="cite" cite="mid:8e6ed3ef-d8ca-b4a5-e85f-205ea221a713@drgeo.eu">Another interest of the builder is to have just one pragma (<worldMenu>) or method name (#worldMenuSpec: aBuilder) for the whole menu hierarchy, and a different name for each menu and submenus. </blockquote> <pre class="moz-signature" cols="72">-- GNU Dr. Geo <a class="moz-txt-link-freetext" href="http://drgeo.eu">http://drgeo.eu</a> <a class="moz-txt-link-freetext" href="http://blog.drgeo.eu">http://blog.drgeo.eu</a></pre> </body> </html>