#2 Replacing the help output doesn't work

v1.0 (example)
closed-fixed
nobody
5
2005-01-13
2005-01-04
hbutler
No

As per example test4.exe I wanted to replace the help
string output for a Cmdline object. The
TCLAP::CmdLine::_output variable is set in the
constructor for the Cmdline object. It then goes off and
registers the Stdoutput created in the constructor
rather than my derived Stdoutput object. The
setOutput function call allows you to set the _output
variable, but this can only be done after the call to the
constructor that registers the help message.

Discussion

  • Mike Smoot

    Mike Smoot - 2005-01-05

    Logged In: YES
    user_id=27603

    Doh! This is indeed a bug. I've checked a fix into CVS
    and will put out a proper release in the next couple of
    weeks and possibly sooner.

    Mike

     
  • Nobody/Anonymous

    Logged In: NO

    One of the motives for trying to replace help output was
    because I was getting expections from iterators. In
    spacePrint there were cases where allowedLen, indentSpaces
    where actually getting assigned negative values... I wasn't
    sure why and so I tried my own help. Have you ever seen
    anything like this? I don't have a good test case at the
    moment and have moved on to something else.

     
  • Mike Smoot

    Mike Smoot - 2005-01-05

    Logged In: YES
    user_id=27603

    Yeah, several other people have encountered the same
    behavior. The problem occurred when commands were
    executed with long paths or the command names themselves
    were very long (over ~75 chars in length). This problem
    has been fixed in 1.0.4. I'll try and get 1.0.5 out in a
    few days. Sorry for the troubles.

    Mike

    Mike

     
  • Mike Smoot

    Mike Smoot - 2005-01-13

    Logged In: YES
    user_id=27603

    This has been fixed in release 1.0.5.

     
  • Mike Smoot

    Mike Smoot - 2005-01-13
    • status: open --> closed-fixed
     

Log in to post a comment.

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

Sign up for the SourceForge newsletter:





No, thanks