Jim Henderson wrote:
> And you need to look up again the definition of "DLL Hell".

You know, they solved this problem quite some time ago... Like, around 
2000 or earlier.

-- 
   Darren New / San Diego, CA, USA (PST)
     "That's pretty. Where's that?"
          "It's the Age of Channelwood."
     "We should go there on vacation some time."

Post a reply to this message

Jim Henderson wrote:
> You've been lucky.  Last company I worked for had many applications with 
> DLLs in common but requiring different versions. 

FWIW, that's actually easy to fix. You just put the right version of the 
DLL next to each executable, and create a file in the same directory 
with a magic name (that I disremember offhand but something like 
"loadseparate"), and the DLL loader will look at the directory with the 
executable first for any DLL.  It's the same thing that the 
"side-by-side" is supposed to solve, so googling for that would probably 
lead you to the right place.

-- 
   Darren New / San Diego, CA, USA (PST)
     "That's pretty. Where's that?"
          "It's the Age of Channelwood."
     "We should go there on vacation some time."

Post a reply to this message

Darren New wrote:
> Now, if Linux supported the thing that NTFS supports where you can 
> delete the beginning of a file, maybe I'd use that. But as it is, I have 
> to chop the file up so I can delete parts of it.
> 

Could "split" possibly help you?

-- 
Eero "Aero" Ahonen
    http://www.zbxt.net
       aer### [at] removethiszbxtnetinvalid

Post a reply to this message

Chambers wrote:
> When you're writing a single, simple tool, with well defined inputs and 
> outputs, it's much easier to make it work *no matter what*. 

I saw a study done a number of years ago where researchers took each 
UNIX tool and piped random data into its input. The only ones that 
didn't dump core were programs that didn't care (e.g., cat) or programs 
specifically designed to parse its input (e.g., gcc).  Something like 
70% of the tools they tested dumped core.

A couple years later, it was all cleaned up or at least vastly improved, 
apparently.

-- 
   Darren New / San Diego, CA, USA (PST)
     "That's pretty. Where's that?"
          "It's the Age of Channelwood."
     "We should go there on vacation some time."

Post a reply to this message

On Tue, 11 Mar 2008 15:34:28 +0000, Invisible wrote:

>>> Who said anything about the kernel? I'm talking about the entire Linux
>>> OS. (Most of which is actually GNU, if you want to be technical about
>>> it...)
>> 
>> So yes, be technical about it, then - I don't know of any Linux distro
>> that uses "standard" tools that aren't GNU, be it awk, sed, perl, bash,
>> etc.
> 
> Except that Unix /= Linux. There's also BSD and Solaris and random stuff
> like that... and autoconf works with all of them.

Yes, I'm aware - have used Solaris, BSD, and SYSV.  And autoconf is there 
to make sure what's there.

> "Windoze" is more or less one product line. Binaries work unmodified on
> most versions of it. (Assuming the features they use are there.) "Unix"
> is not one product. It's not even close to being one product. It's a
> vast stew of different products all bolted together in a giant mess.

An OS can be called a "UNIX System" only if it meets certain standards, 
as defined by The Open Group.  So right away, you're operating under a 
fallacy that you can compare UNIX to Windows - Windows is a product, UNIX 
is a set of standards that define the operation of a product.

Microsoft occasionally deigns it's OK to follow standards they didn't 
define - they use the BSD TCP/IP stack in most versions of Windows; they 
follow (to a greater or lesser extent) standards for web browsing 
software; they even have in the past (not sure about today) incorporated 
a POSIX-compliant subsystem.  They don't own any of these standards, but 
they use them.

>>> I have yet to experience "DLL Hell". I'm told it exists, and it's not
>>> fun, but I haven't seen it personally. (Don't ask me why...)
>> 
>> You've been lucky.
> 
> Let's hope it stays that way...

The longer you work in IT, the less likely it is to happen.

Jim

Post a reply to this message

On Tue, 11 Mar 2008 11:33:41 -0700, Darren New wrote:

> Jim Henderson wrote:
>> chkdsk
> 
> It's actually not even chkdsk at boot time. It's autochk, which is a
> different program to do the same thing. And the recovery console has yet
> a different version. Why they felt the need to implement it three times
> I don't understand. :-)

Yeah, that's what I was thinking.  Last time I did something like this 
with Windows, it was Partition Magic that inserted itself into the boot 
process.

Jim

Post a reply to this message

Invisible wrote:
> ad-hoc *mess* of haphazardly interacting command switches that you have 
> to spend 20 minutes studying the manpage to decode the interactions for?

Don't forget that it also changes behavior depending on whether it 
things stdout is a terminal, a different character device, or a file.

> Also: autoconf exists. Need I say more?

And ptys.

-- 
   Darren New / San Diego, CA, USA (PST)
     "That's pretty. Where's that?"
          "It's the Age of Channelwood."
     "We should go there on vacation some time."

Post a reply to this message

Warp wrote:
>   Portability is a key feature of unix-like systems.

I always have to cringe a bit when someone decides that two different 
versions of source code in one file means it's "portable".

#ifdef isn't a sign of portability. It's a sign of lack of portability. 
If your 32-bit code breaks on a 64-bit machine, your language isn't 
portable.

-- 
   Darren New / San Diego, CA, USA (PST)
     "That's pretty. Where's that?"
          "It's the Age of Channelwood."
     "We should go there on vacation some time."

Post a reply to this message

Warp wrote:
>   (Sure, the code could have been written so that endianess doesn't matter,
> but then it wouldn't have been so efficient.)

And of course, in *portable* languages for doing system-level 
programming, you simply specify that particular variables have a certain 
endianness, and you let the compiler write the code to do the 
byteswapping at the places it's needed. :-)

-- 
   Darren New / San Diego, CA, USA (PST)
     "That's pretty. Where's that?"
          "It's the Age of Channelwood."
     "We should go there on vacation some time."

Post a reply to this message

Phil Cook wrote:
> But wasn't it v7 that introduced the ability to layout and print 
> multiple images? Such a handy little thing.

Actually, it's rather annoying.  And v8 tried to improve it and just 
made it way more suckful.

-- 
   Darren New / San Diego, CA, USA (PST)
     "That's pretty. Where's that?"
          "It's the Age of Channelwood."
     "We should go there on vacation some time."

Post a reply to this message