how to stop info output on screen

Hi,

Does someone know how to stop "the information output on screen"? Now
when I run my code, it outputs a lot of message when calling other
libraries, together with the info with the print command I used.

How can I mask these info on screen when calling other libraries and
how I can mask the info output produced by the print command? Is there
a way to mask them separately.

Thanks a lot if anyone knows it.

Kind regards of your help
Midday

.

Relevant Pages

  • Re: Calling C written API from C# shows strange behaviour
    ... |I have some strange behaviour when calling a function on a C written ... | The API is part of the XCOM server by Computer Associates. ... | The XCOM server documentation comes with a piece of sample code in C to ... | runs and the libraries used are the same. ...
    (microsoft.public.dotnet.framework.interop)
  • Re: Does fopen fclose implement open and close internally??
    ... Does fopen fclose implement open and close ... If it is so how does the overhead of calling low-level ... precompiled libraries. ... C- Programmer has to only worry about their code conforming to C-std ...
    (comp.unix.programmer)
  • Re: MissingMethodxception
    ... "connect") gives an exception. ... Anyway all applications gives an exception calling ... are linked against libraries that don't exist in CE and ... >> public override void Connect ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: YUI Libraries
    ... libraries from Yahoo? ... I was hoping to find a calendar widget in there that would do what I needed, but there were so many includes, millions of style elements, and a bloat I just couldn't accept. ... Then I needed hooks back into the calling page for click, mouseover, and mouseout on the days themselves. ... That part of it I don't think I did in a very clean way, it calls functions on the calling page as callbacks, but the names have to be the same each time. ...
    (comp.lang.javascript)
  • Re: [patch resend] vfs: move executable checking into ->permission()
    ... WTF is going on in that one? ... quite a few of those might have enough information to make calling ... If anything, we want non-directories fail MAY_EXEC here, no matter ... If mask contains MAY_EXEC and we got to calling check_execute, ...
    (Linux-Kernel)