🚀 go-pugleaf

Guy Finney (gaf@anasazi.com) wrote:
: gaf@misty.anasazi.com (Guy Finney - me) writes:
: >
: >Fine, it compiles into hello.obj.  But when I try to link it into hello.exe,
: >I get the message "Invalid object module" in reference to hello.obj.
: >Not even one of the Lnnnn message numbers to look up.  Hmmphh.
: 
: Thanks to all those who suggested there might be some other program
: named link.exe in my PATH prior to the one in my C development directory.
: That was it.  This was very annoying.  One might be forgiven for thinking
: that Microsoft would have anticipated this and either named their linker
: something else, or at least mentioned in the release notes that they
: overloaded the name link.exe so you could take appropriate action.
: 
: Oh well.  Another fun DOS development story.  I'm glad I don't work
: on DOS for a living.

What makes you think the same thing couldn't happen on say a UNIX system? Or
any other system that supports multiple directories and an execution path
mechanism.

I see this type of thing all the time on UNIX. Users just need to be aware
of their environment. I think, whenever there is any doubt, to use a DOS
utility similar to "which" to tell where it actually found a specific
program.

Russ Poffenberger               DOMAIN: poffen@sj.ate.slb.com
Schlumberger Technologies ATE   UUCP:   {uunet,decwrl,amdahl}!sjsca4!poffen
1601 Technology Drive		CIS:	72401,276
San Jose, Ca. 95110             Voice: (408)437-5254  FAX: (408)437-5246