Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. General Programming
  3. C / C++ / MFC
  4. Displaying the output of another program

Displaying the output of another program

Scheduled Pinned Locked Moved C / C++ / MFC
4 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • O Offline
    O Offline
    oldbritthumper
    wrote on last edited by
    #1

    This needs to be removed

    L 1 Reply Last reply
    0
    • O oldbritthumper

      This needs to be removed

      L Offline
      L Offline
      Lost User
      wrote on last edited by
      #2

      Not heard of that, and I cannot see what use it is. Why not just run the original in a command window to start with?

      O 1 Reply Last reply
      0
      • L Lost User

        Not heard of that, and I cannot see what use it is. Why not just run the original in a command window to start with?

        O Offline
        O Offline
        oldbritthumper
        wrote on last edited by
        #3

        This calling program (that I have not yet found), does not necessarily need to understand graphics. And the simpler the code, the better. But this program will very much need to understand text. As a matter of fact it will really like text and it really won't like graphics. It's just funny that way. This program will be submitting a Bash shell script and displaying that script's output. Or, it might be submitting a Bourne shell script and displaying that script's output. Or, it might be submitting a Korne shell script and displaying that script's output. Or, it might be submitting a C-Shell shell script and displaying that script's output. Or, it might be submitting a Perl script and displaying that script's output. Or, it might be submitting a very fundamental Java application and displaying that program's output. Or, it might be submitting a very fundamental C executable and displaying that program's output. Or, it might be submitting a very fundamental C++ executable and displaying that program's output. I don't think that *it* even knows what it will be submitting yet. Oh, wait. *It* hasn't been identified yet. Whatever that calling program is (which is hasn't been identified yet), it MUST be command-line and text-based. The why of it isn't really important. What's important is whether or not there is an open-source C++ example of this type of program available to the general public.

        L 1 Reply Last reply
        0
        • O oldbritthumper

          This calling program (that I have not yet found), does not necessarily need to understand graphics. And the simpler the code, the better. But this program will very much need to understand text. As a matter of fact it will really like text and it really won't like graphics. It's just funny that way. This program will be submitting a Bash shell script and displaying that script's output. Or, it might be submitting a Bourne shell script and displaying that script's output. Or, it might be submitting a Korne shell script and displaying that script's output. Or, it might be submitting a C-Shell shell script and displaying that script's output. Or, it might be submitting a Perl script and displaying that script's output. Or, it might be submitting a very fundamental Java application and displaying that program's output. Or, it might be submitting a very fundamental C executable and displaying that program's output. Or, it might be submitting a very fundamental C++ executable and displaying that program's output. I don't think that *it* even knows what it will be submitting yet. Oh, wait. *It* hasn't been identified yet. Whatever that calling program is (which is hasn't been identified yet), it MUST be command-line and text-based. The why of it isn't really important. What's important is whether or not there is an open-source C++ example of this type of program available to the general public.

          L Offline
          L Offline
          Lost User
          wrote on last edited by
          #4

          I still don't see the point. All of those functions will run perfectly in their own console window so what is the benefit of "It"?

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • World
          • Users
          • Groups