Re: Redirecting stderr



In article <1172611168.921804.263450@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
praetor.michael@xxxxxxxxx <praetor.michael@xxxxxxxxx> wrote:
On Feb 27, 4:02 pm, rober...@xxxxxxxxxxxxxxxxxx (Walter Roberson)
wrote:
In article <1172608859.551149.90...@xxxxxxxxxxxxxxxxxxxxxxxxxxx>,

praetor.mich...@xxxxxxxxx <praetor.mich...@xxxxxxxxx> wrote:
I have a DLL written in C that writes to stderr. I have a win32
console application that makes calls to the DLL.

That sounds like a question more appropriate for a Windows
programming newsgroup.

It actually works the same on either platforms. The code was designed
to work on windows and all unix flavors. Which is why I posted it
here.

That's bogus. There's no DLL support in the Unix version I use,
and it is one of the few officially certified Unix releases.
If you search opengroup.org (official certifiers of Unix),
you will find that the DLL references are all platform specific.

Whatever it is you are using is *not* part of standard C -- and
if it is called "DLL", it is not even part of standard Unix,
nor POSIX. If the code uses DLLs on Windows and shared libraries
on the POSIX-compatible Unix systems, then it it is using something
platform specific, not part of the C language.



Note, by the way, the official opengroup definition of dlopen()
http://www.opengroup.org/onlinepubs/009695399/functions/dlopen.html

The dlopen() function shall make an executable object file
specified by file available to the calling program. The class of
files eligible for this operation and the manner of their
construction are implementation-defined, though typically such
files are executable objects such as shared libraries,
relocatable files, or programs.

Notice the lack of reference to DLL. That is not an accident:
C doesn't have them and POSIX doesn't have them either.
--
"No one has the right to destroy another person's belief by
demanding empirical evidence." -- Ann Landers
.



Relevant Pages

  • Re: .Net packaging/wrapper application?
    ... the simple answer to DLL Hell for Visual Basic apps was simply to place a copy of the needed DLLs in the same directory as your executable. ... The way Windows works is to look in the executable's directory for a needed DLL BEFORE using the registry to find one EVEN IF THE REFERENCED DLL IS REGISTERED ON THE PC RUNNING THE APPLICATION THAT NEED IT. ... Perhaps I'm getting old and but what really bothers me is nobody seems to notice this--maybe the 80s was before they got into programming. ... Looks to me like Jim is looking for the .NET equivalent of compiling with static libraries to produce a single executable. ...
    (microsoft.public.dotnet.framework.aspnet)
  • addsourcefilter locking file in windows
    ... I'm new to this group and somewhat new to directshow programming. ... with windows programming. ... I wrote a C++ MFC dll that I am calling from a VB6 application. ... and builds a graph. ...
    (microsoft.public.win32.programmer.directx.video)
  • Re: services for unix redistribution licence question
    ... IIRC, MSFU is free. ... area for either 'services for unix' or 'licensing'. ... Suppose I am porting to windows an application that currently uses Posix ... So if I make my product dependent on this DLL, ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Windows: Perl:Inline
    ... This DLL is responsible to create ... > registry entries in the given Machine. ... currently my perl module is capable of creating ... > registry entries in Windows, but not in Unix, so I am trying to extend ...
    (comp.lang.perl.modules)
  • Re: Linux, X, ld, gcc, linking, shared libraries and stuff
    ... "Cygwin"; This is a general project to make UNIX software run on Windows, ... a pretty simple idea...the Cygwin programs use the DLL as if it ...
    (alt.lang.asm)