Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

Where did SOM support go in 4.0.0?

Developers
OCTAGRAM
2013-01-04
2013-01-05
  • OCTAGRAM
    OCTAGRAM
    2013-01-04

    IBM Object REXX has integration with SOM, and ooRexx seems to inherit this capability at least up to 3.2.0. Looking at 3.2.0 sources I can't say for sure which targets used SOM. Given that it was very hard to find Windows version of SOM and given that open source SOM is not widely known I guess SOM support files were lying around like an orphan, but Makefile, bat files and so on carefully preserved SOM links so it was never clear if SOM is supported or not. Then SCM migration occured. The latest CVS version is 3.1.1.1. The first SVN version is 4.0. As opposed to converting repository from CVS to SVN the history was reset over and started from scratch. Even worse, essential slice of history right in between is missing. 3.2.0 source refers to https://oorexx.svn.sourceforge.net/svnroot/oorexx/interpreter-3.x/trunk , but this location ceased to exist.

    3.1.1.1 has SOM support, So does 3.2.0. 4.0 doesn't have one. I've looked through CHANGES file in 4.0.0 release. CHANGES is stated to enumerate changes from 3.2.0 to 4.0.0, but nothing is said about SOM despite drastical changes in both directory structure and file contents. In 3.2.0 sources were full of "SOMObj" occurences, in 4.0.0 there are none and the exact slice of SCM history where it happened is deleted so I can't find it out on my own. What's going on?

    Can you please clarify a history of SOM support in O(O)REXX in Wiki.

     
    • Rick McGuire
      Rick McGuire
      2013-01-04

      ERROR! The markdown supplied could not be parsed correctly. Did you forget to surround a code snippet with "~~~~"?

      The source that IBM released did not include all of the source necessary to
      implement SOM.  Some of the code was in the base interpreter, but was never
      enabled in any releases.  The 4.0 code cleanup removed all of the SOM code
      because it would have required some very difficult cleanup to make 64-bit
      clean.
      
      Rick
      
      On Fri, Jan 4, 2013 at 5:21 PM, OCTAGRAM <octagram-3@users.sf.net> wrote:
      
      > IBM Object REXX has integration with SOM, and ooRexx seems to inherit this
      > capability at least up to 3.2.0. Looking at 3.2.0 sources I can't say for
      > sure which targets used SOM. Given that it was very hard to find Windows
      > version of SOM and given that open source SOM is not widely known I guess
      > SOM support files were lying around like an orphan, but Makefile, bat files
      > and so on carefully preserved SOM links so it was never clear if SOM is
      > supported or not. Then SCM migration occured. The latest CVS version is
      > 3.1.1.1. The first SVN version is 4.0. As opposed to converting repository
      > from CVS to SVN the history was reset over and started from scratch. Even
      > worse, essential slice of history right in between is missing. 3.2.0 source
      > refers to
      > https://oorexx.svn.sourceforge.net/svnroot/oorexx/interpreter-3.x/trunk ,
      > but this location ceased to exist.
      >
      > 3.1.1.1 has SOM support, So does 3.2.0. 4.0 doesn't have one. I've looked
      > through CHANGES file in 4.0.0 release. CHANGES is stated to enumerate
      > changes from 3.2.0 to 4.0.0, but nothing is said about SOM despite
      > drastical changes in both directory structure and file contents. In 3.2.0
      > sources were full of "SOMObj" occurences, in 4.0.0 there are none and the
      > exact slice of SCM history where it happened is deleted so I can't find it
      > out on my own. What's going on?
      >
      > Can you please clarify a history of SOM support in O(O)REXX in Wiki.
      >
      > ---
      > [Where did SOM support go in 4.0.0?](
      > https://sourceforge.net/p/oorexx/discussion/408479/thread/1f93f87f/?limit=25#b47a
      > )
      >
      > ---
      >
      > Sent from sourceforge.net because you indicated interest in <
      > https://sourceforge.net/p/oorexx/discussion/408479/>
      >
      > To unsubscribe from further messages, please visit <
      > https://sourceforge.net/auth/prefs/>
      >
      
       
  • Mark Miesfeld
    Mark Miesfeld
    2013-01-04

    The left over SOM files were definitely removed in the general refactoring of the code base that was done between 3.2.0 and 4.0.0.

    Rick would be the authority on this and he may correct or clarify anything I say here.

    The SOM files in the code base were for OS2 support. As far as I know, SOM was never supported on Windows by IBM.

    The ooRexx project itself has never made any claim that SOM was supported in any release we have done.

    If SOM works on Windows with ooRexx 3.2.0 or earlier using a Windows version of SOM or an open source version of SOM, then you can find that out by testing it. But, we don't claim to support it.

    As far as I know, Rick did not make any changes to deliberately change the SOM support that was in the files we inherited from IBM. But, that doesn't imply we ever thought SOM would work.

    As far as the disconnect that happened during the change from CVS to SVN and again during the change from 3.2.0 to 4.0.0, that was unanticipated and in my view unfortunate.

    I think, but am not sure, that there should be a way to recover the missing "essential slice of history" from SVN. That location https://oorexx.svn.sourceforge.net/svnroot/oorexx/interpreter-3.x/trunk can not be located, is as I said unfortunate. It is something I've run into, but didn't take the time to try and resolve. It is due to the fact that we renamed interpreter-3.x to main. Since that was done through svn, it should be possible, some way, to retrieve any code revision from the time we moved from CVS to subversion.

    If you discover how to do that, I'd appreciate if you'd add it to this discussion.

    It might be possible to get some help on that from SourceForge support on that.

    I hope that clarifies things somewhat.

     
  • Mark Miesfeld
    Mark Miesfeld
    2013-01-04

    As far as recovering the history of files from svn:

    This command:

    svn co https://oorexx.svn.sourceforge.net/svnroot/oorexx/@r1

    will check out what I believe was the original code base imported from CVS:

    Path: .
    Working Copy Root Path: C:\work.ooRexx\wc\my.oorexx
    URL: https://oorexx.svn.sourceforge.net/svnroot/oorexx
    Repository Root: https://oorexx.svn.sourceforge.net/svnroot/oorexx
    Repository UUID: 5c7345e9-2c1c-0410-8966-b4899360e60d
    Revision: 1
    Node Kind: directory
    Schedule: normal
    Last Changed Author: wdashley
    Last Changed Rev: 1
    Last Changed Date: 2006-08-29 13:00:54 -0700 (Tue, 29 Aug 2006)

    C:\work.ooRexx\wc\my.oorexx>

    It might take a bit of work for you to get exactly what you want, but it does prove that all revisions of the code base since we switched from CVS to present are available.

     
  • Rick McGuire
    Rick McGuire
    2013-01-04

    There is a fairly significant piece of the SOM support that was never released by IBM, so the code in the original codebase is completely non-functional.