Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!ukc!tcdcs!swift.cs.tcd.ie!maths.tcd.ie!tim From: tim@maths.tcd.ie (Timothy Murphy) Newsgroups: comp.sys.mac.apps Subject: Re: Think C Message-ID: <1990Sep28.115712.18559@maths.tcd.ie> Date: 28 Sep 90 11:57:12 GMT References: Organization: Dept. of Maths, Trinity College, Dublin, Ireland. Lines: 36 In sg2s+@andrew.cmu.edu (Sean Michael Goller) writes: >Small question for everyone in netland: >I'm using my mac to write unix programs, then move the code there and do >final compilation. The problem is this: Think C mentions a function >ccommand() with should be called like so: >argc = ccommand(&argv); >which should simulate command-line parameters in unix. However, they >don't detail where this function is....they say it's in the console >library, but it's not on the disks with the package! I have both ANSI >and unix packages loaded, and Think C just barfs on ccommand...... Have you tried #include The function ccommand is mentioned in my THINK C 'Standard Libraries' manual. It is in a section called 'console'. I imagine that is there used to be a 'console' library, which is now included in the ANSI library. I do find this 'ccommand' business a nuisance. It means that virtually every C program has to be modified on porting to the Mac. I assume the reason is that one 'ought' to use the Mac interface, but life is too short ... -- Timothy Murphy e-mail: tim@maths.tcd.ie