Peter William Lount wrote:
> Hi,
>
> It is not only possible and deseriable to write ALL META data and 
> operations in Unary, Binary and Keyword Message Passing Syntax ( 
> [UBKMPS] )  (as done in Smalltalk), it has potent results. See it as a 
> simulation in 3d+time.
>
> Let us see the flow of programs alter with declarations guiding their 
> construction and operation.
>
> Reply with any declaration or meta program operation that you wish to 
> have expressed in MPS. What are they?
>
> Rewrite it into MPS using standard Smalltalk with minimal Objects from 
> the library. What do declarations look like in Smalltalk?
>
> Declarations can exist within a stream of coding whatever aspect of 
> program operation that you desire. Declarations interact in an 
> environment influencing those relevant program statements according to 
> the dynamics or statics of the declation internals.
>
> What are the consequences and impact for implementation and other 
> details?
>
> Peter William Lount
> peter at smalltalk.org
>
>
>
>
>
>
Hi,

In a way the control and data streams in network protocols such as voice 
and video calls and conferencing have the same issue as meta and program 
syntax described above. Separate control and data syntaxes? Separate 
feed channels? Or use one unified syntax for both? One stream for both? 
In a streaming flow which are control and which are data? In a streaming 
flow which are meta and which are program? An age old inquiry in 
formation for solutions that work.

Unified Method and Block [UMB] syntax in combination with [Unary, Binary 
and Keyword Message Passing Syntax ( [UBKMPS] ) provides a means to 
accomplish this.

A name space enables the mixing of messages to controlling meta data and 
meta operations with dynamically adjustable program statements and 
runtime operational execution. Really? A name space assists in the 
unification of meta data, meta operations, application data and program 
instructions? Yeah, a name space. Makes you think of what the name space 
that the hierarchical file system achieves with scripts and files in 
unix, doesn't it? Hmmm...

One can imagine an N directional stream nexus driving communications to 
other core nodes and client nodes using streams of Unary, Binary and 
Keyword messages expressing the information transmitted and acted upon. 
The same format that all the programs are written in. The same format 
that all the data is written in. The same format that we know so well 
with minor adjustments making it more pure [UBKMPS] based.

All "code" in a UMB Browser tool are in the UMB+UBKMPS format. Think of 
all "method" panes that you would see in a typical Smalltalk Hierarchy 
Browser as a DO IT Workspace window with statements in the form of 
operations with objects just like a workspace would have. Streamlined 
for efficient organization of meta data, meta operations, application 
data,  and program statements much like the Hierarchy Browser is 
streamlined for class definitions and method browsing, specification, 
editing, compiling, running, and debugging.


[ | peter at smalltalk dot org ] email.

[ | categorize as vision and inquiry with design and implementation focus ].

[ | allow these thoughts to simmer, rattle and boil on the back burner; 
communicate when ready ].