#1233 .traceOutput has no objectName set

v4.2.0
closed
None
complete
1
2015-03-27
2013-12-30
No

.traceOutput has no objectName like "The TRACE OUTPUT monitor" set to it, hence it will report itself as "a Monitor".

This is in contrast to .debugInput which objectName is set to "The DEBUG INPUT monitor", hence speculating that .traceOutput should have an objectName set as well.


    F:\test\orx\420>rexxtry
    REXX-ooRexx_4.2.0(MT)_32-bit 6.04 27 Dec 2013
      rexxtry.rex lets you interactively try REXX statements.
        Each string is executed when you hit Enter.
        Enter 'call tell' for a description of the features.
      Go on - try a few...            Enter 'exit' to end.
    say .traceoutput
    a Monitor
      ........................................... rexxtry.rex on WindowsNT
    say .debugInput
    The DEBUG INPUT monitor
      ........................................... rexxtry.rex on WindowsNT
    say .traceOutput
    a Monitor
      ........................................... rexxtry.rex on WindowsNT

Discussion

  • Rick McGuire

    Rick McGuire - 2013-12-30
    • status: open --> pending
    • assigned_to: Rick McGuire
    • Pending work items: none --> complete
    • Group: None --> v4.2.0
     
  • Rick McGuire

    Rick McGuire - 2013-12-30

    Committed [r9775] 4.2.0, [r9776] trunk.

    The real issue was the object name was accidentally changed for .OUTPUT, resulting in .traceOutput not having a name, and .Output having the wrong name.

     

    Related

    Commit: [r9775]
    Commit: [r9776]

  • Rick McGuire

    Rick McGuire - 2014-04-15
    • status: pending --> closed
     


Anonymous

Cancel  Add attachments





Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks