[RFC] Separate cmd, mi and actions in the app sources

[Jose E. Marchesi]

Hi people!

The command-related sources of the poke application are right now
structured as follows:

  pk-cmd.[ch] -> Infrastructure for dot-commands.

  pk-ios.c -> IOS-related dot-commands.
  pk-vm.c  -> VM-related dot-commands.
  ...
  pk-FOO.c -> FOO-related dot-commands.

With the addition of the machine-interface, however, I propose to switch
to this schema instead (using the IOS-related stuff as an example):

   pk-cmd-ios.c  --+
                   |
                   +-->  pk-ios.c
                   |
   pk-mi-ios.c ----+

Where:

- pk-mi.c contains the code that dispatches IOS-related requests to the
  "semantic" routines in pk-ios.c.  For example, it would translate a
  REQUEST_OPEN_IOS to the corresponding pk_ios_open implemented in
  pk-ios.c

- pk-cmd-ios.c contains the cmd machinery for the IOS-related
  dot-commands.  Basically what pk-ios.c contains nowadays, minus the
  "semantic" routines.

- pk-ios.c contains the "semantic" routines to manipulate IOS.  These
  services are used

Sounds good?
Objections?