1735: In Progress

A-Shell Release Notes Version 6.5.1735.2 (28 July 2023)
1. Compiler bug fix (edit 1033) relating to the transclude  mechanism:

•     Eliminate spurious errors when the TCF spec in a ++include statement contained a device: prefix.

A-Shell Release Notes Version 6.5.1735.1 (27 July 2023)
1. Compiler bug fixes (edit 1030) relating to the transclude mechanism:

•     Failure to specify a TCF section in the ++include line was causing the operation to ignore the TCF file contents.

•    PRIVATE module variables now work as expected in transcluded modules. (Previously the compiler was complaining of duplicate variables.)

A-Shell Release Notes Version 6.5.1735.0 (23 July 2023)
1. Runtime enhancement: new MIAMEX function MX_RUNPROF (203) generates a run profile log which can then be analyzed for an overview of the program call structure and performance.

    xcall MIAMEX, MX_RUNPFOF, OPSTS {,FSPEC}

where:
    OPSTS (num) [in/out] specifies the opcode and return status:
                0) check profiling status
                     returns: 0=disabled, 1=enabled (+flags)
                1) enable profiling (outputting to FSPEC)
                     returns: 2=now enabled, -2=already enabled, -3=can't open file
                2) disable profiling
                     returns: 3=now disabled, 0=was disabled
    
    FSPEC (str) [in] - filespec where profiling data will be recorded

2. New system command RUNPROF.LIT provides user-level access to profiling operations.  Use RUNPROF/? for help.

3. New REGEX flag PCREX_NOT_PRECOMPILE (&h08000000) may be used with a single-character pattern to indicate that it is a string pattern and not a pre-compiled pattern #.

4. Param passing refinement:  passing an X value to a numeric parameter type
   now performs a string-to-numeric conversion like you would get when passing an
   S value to a numeric type, or when assigning an X value to a numeric type.
   Previously it was doing a raw byte copy from the source to the receiving
   parameter.

5. GRIDMAP bug fix: gridmap parameters appearing in complex expressions were in some cases resulting in corruption of the string stack.

6. INPUT CSV to GRIDMAP bug fix: quoted values in the CSV source were not properly unquoted when loading them into the GRIDMAP. Also, it wasn't clearing the GRIDMAP prior to the operation.

7. Compiler bug fix (edit 1029) - ++include with [p,pn] was getting confused with the new transclude (see edit 1025) syntax.

11 Dec 2020 Conversion

 Jack and Ty had a long discussion about several matters on this date, including the subject of this blog. We touched on many points, but here is a summary.

Options for moving A-Shell to the next phase. We're not sure what precisely that next phase is, but its main feature is that its future is not so tightly tied to Jack.

• Find a local guy who can take over.
  
  
• Convert A-Shell to open source, and give/sell it to our big dealers.
  
  
• Find a current A-Shell dealer/developer to take over. SGA, Omniledger, Jorge.
  
  
• Have a conference with selected A-Shell people who have history with us and can grasp all the issues and complexities involved. Jorge, Stephen F, Phil, Denis.
  
  
• Write a letter to major dealers/users explaining situation and asking for their perspective and see if they are interested in becoming the A-Shell home. Omniledger, SGA, GOP. Jack expressed reluctance about this plan because it might alarm the parties because they have a lot to lose. 

No actions or next steps were decided.

 

 

Introduction

 It is fairly important that MicroSabio develop a plan for "post-Jack A-Shell." We're not exactly sure what form this plan or future will take, but its main characteristic is that the A-Shell business (development, sales, support, everything) will no longer be so dependent on Jack and MicroSabio. We're starting this discussion in December 2020, with the hope that a complete transition to "the new A-Shell" will be done/complete/in-place by 2030.  As of this beginning, Jack is 61 and Ty is 70. Both plan to work indefinitely, but retirement and/or reduced levels of involvement are on the horizon.

There are many complicated aspects to the situation and hence to any plan we come up with. The purposes of this blog are to:

• Have a place to collect our thoughts, write down concerns, remind us of things we have previously done or decided
  
  
• Provide a record of our deliberations for purposes of review and re-evaluation over time
  
  
• Provide a link to which we can refer interested parties so as to share our evolving thoughts and plans

The main author is Ty. It's not yet known if Jack will contribute directly.