Set a 0, 1 or 2 argument block that runs when the
     #info method is called on an OsNativeProcess instance.
     This provides users the ability to further customize the process
     information being collected up.

     Examples:
     addInfoExtensionBlock: [Logger log: '#info was called'].
     addInfoExtensionBlock: [:info | info at: ##argumentCount put: (info arguments ifNil: [0] ifNotNil: [:args | args size])]
     addInfoExtensionBlock: [:info :process | info at: ##virtualMemInUse put: (self getVirtualMemInUse: process pid)]

     Arguments:
        aBlock - <Block> 0-Argument
                                    1-Argument <OsProcessInfo> info
                                    2-Argument <OsProcessInfo> info  <OsNativeProcess> process

  Answer all native processes running in the system at the time
     of this call.  This will be a pid sorted array that will contain
     a mixture OsNativeProcess and subclasse:
        - OsVastProcess: This vast process
        - OsVastSubprocess: Current spawned child processes of vast
        - OsNativeProcesses: All other processes that are not a vast process or subprocess

     Answers:
        <Array> of <OsNativeProcess> sorted by pids

  Remove the info extension block.
     Answer true if it was removed, false otherwise

     Arguments:
        aBlock - <Block> info extension block
     Answes:
        <Boolean>

  Answer true if the native processes are equal, false otherwise.

     Equality is based on three attributes of a process, the native
     process class, the pid and process creation time.  The pid and
     creation time are needed to establish equality since operating 
     systems will recycle pids meaning we could be comparing 2 
     different processes that share the same pid.

     Answers:
        <Boolean>

  Answers an array of native processes, sorted by pid, that are the
     children, and decendents of children recursivley, of this process.
     If this process has no children, an empty array is answered
     Based on the state of this process, which can change
     at any time (i.e. process died), it may not be possible to get all the children.
     In this case, an empty array is answered.

     Answers:
        <Array> of <OsNativeProcess>

  Answers all the parent processes of this native process, if accessible.
     Based on the state of the native process, which can change
     at any time (i.e. process died), it may not be possible to get the parents.
     The first element of the resulting array will be parent of this process.
     The next element will be the parent of the first element...and so on until
     the most accessible root parent is reached which is the last element

     Answers:
        <Array> of <OsNativeProcess>

  Answers an array of native processes, sorted by pid, that are the
     direct children of this process.
     If this process has no children, an empty array is answered.
     Based on the state of this process, which can change
     at any time (i.e. process died), it may not be possible to get the children.
     In this case, an empty array is answered.

     Answers:
        <Array> of <OsNativeProcess>

  Answer the command line of the native process.
     If not accessible (i.e. permissions), then answer nil

     By default, this is expressed in the current code page

     A primitive failure will occur if the name is not
     a byte object
     A primitive failure will occur if the args is not
     nil or an Array

     Answers:
        <String> or nil

  Answer an integer representing the receiver's exitCode,
     if the process has not completed answer nil. 
     Note: This is operating system dependent.

     Answers:
        <Integer>

  Answers information about the process at the time this call was made.
     Included in this are customized user actions which may be used to
     decorate the info.

     @see OsNativeProcess class>>addInfoExtensionBlock:
     for more information on how to add customized info

     Note: The strings from the info are converted from UTF-8
     to the current code page.  If you want UTF-8, call #utf8Info
     instead

     Answers:
        <OsProcessInfo>
     Raises:
        <OsProcessException>

  Answer true if the receiver process has completed, false otherwise

     Answers:
        <Boolean>

  Object check

     Answers:
        <Boolean> true

  Kill the process immediatley, bypassing any graceful shutdown
     that may be offerred by the OS.

     This semantics of 'kill' vs 'terminate' are OS dependent.
         Windows - terminate and kill are equivalent
         Unix - SIGKILL is used here.  (SIGTERM for terminate)

     @see OsNativeProcess>>terminate: for further details

     Answers:
        <Boolean> true if terminated, false otherwise

  Answer a future that represents the
     eventual completion of this process

     Answers:
        <EsFuture>

  Answers the parent of this native process, if accessible.
     Based on the state of the native process, which can change
     at any time (i.e. process died), it may not be possible to get the parent.
     In this case, nil is answered

     Answers:
        <OsNativeProcess> or nil

  Answer the native process identifier assigned
     by the operating system

     Answers:
        <Integer>

  Terminate the process, gracefully if the OS supports it.
     @see OsNativeProcess>>terminate: for further details

     This semantics of 'kill' vs 'terminate' are OS dependent.
         Windows - terminate and kill are equivalent
         Unix - SIGTERM is used here.  (SIGKILL for kill)

     Answers:
        <Boolean> true if terminated, false otherwise

  Answer the unique identifier assigned
     by VAST.  This id will be unique for the
     duration of the VAST instance

     Answers:
        <Integer>

  Answer the command line of the process.
     If not accessible (i.e. permissions), then answer nil

     Answers:
        <String> or nil

  Answers information about the process at the time this call was made.
     Included in this are customized user actions which may be used to
     decorate the info.

     @see OsNativeProcess class>>addInfoExtensionBlock:
     for more information on how to add customized info

     Note: The strings from the info are UTF-8
     If you want string in the current code page,
     then call #info instead

     Answers:
        <OsProcessInfo>
     Raises:
        <OsProcessException>

  Convenience Method: From a completion future,
     request to wait for the process to complete and answer the
     exit code.
     The calling smalltalk process will block until the process completes

     Answers:
        <Integer> - exit code

  Convenience Method: From a completion future,
     request to wait for the process to complete and answer the
     exit code.
     The calling smalltalk process will block until the process completes or the
     wait duration (@aDurationOrMs) elapses.
     Answers the <Integer> exit code if the process completes before the elapsed time.
     Otherwise, answer nil if the duration time elapses

     Arguments:
        aDurationOrMs - <Duration>duration object
                                    <Integer> duration in milliseconds
     Answers:   
        <Integer> - exit code
        <UndefinedObject> - nil if the duration elapsed before the process exited