From mboxrd@z Thu Jan  1 00:00:00 1970
From: david at kdbarto.org (David)
Date: Mon, 9 Jul 2018 06:10:03 -0700
Subject: [COFF] Other OSes?
In-Reply-To: <9C710876-D8BC-4CC6-B1A2-2B1F7C066033@bitblocks.com>
References: <20180705055650.GA2170@minnie.tuhs.org>
 <20180708165006.21a7429e@jabberwock.cb.piermont.com>
 <B52001B7-82DC-4D33-B1AF-02482A6C04A4@bitblocks.com>
 <20180708201151.03aa46c0@jabberwock.cb.piermont.com>
 <CAEoi9W4NkH+H-8--Vn3fPQN9Qpmtz9FP_4xgSutxZXxaYkmNJA@mail.gmail.com>
 <9C710876-D8BC-4CC6-B1A2-2B1F7C066033@bitblocks.com>
Message-ID: <746DC51F-65FB-4656-AED2-A0E244C6F453@kdbarto.org>

> When we did cisco CLI support in our router product, syntax for all
> the commands was factored out. So for example
> 
> show.ip
>  help IP information
> 
> show.ip.route
>  help IP routing table
>  exec cmd_showroutes()
> 
> show.ip.route.ADDR
>  help IP address
>  verify verify_ipaddr()
>  exec cmd_showroutes()
> 
> etc. This was a closed universe of commands so easy to extend.
> 
> Perhaps something similar can be done, where in a command src dir
> you also store allowed syntax. This can be compiled to a syntax
> tree and attached to the binary using some convention. The cmd
> binary need not deal with this (except perhaps when help or verify
> required cmd specific support).
> 

This sounds like a resource fork on a file. Much like MacOS (pre X) had for all files. It was a convenient way to keep data that defined the application associated with the application. You could also edit it to customize it for your own use if you wished.

There were a great many good things about the MacOS of old.

	David


> _______________________________________________
> COFF mailing list
> COFF at minnie.tuhs.org
> https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff