X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
X-Recipient: djgpp AT delorie DOT com
X-Recipient: djgpp-workers AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc;
        bh=0P33YPJPPoNuSR9B4yx61LSi2AdFarqiCrzZEdImqgs=;
        b=lXJeIo1wtX/tGB2KGVRcqNVnPS36ejjoSfJyLtaTY19lKubJ7W0Xyrag61mZ4qmWXe
         C9uF8hprius8zIEr2O6N+Lpx83nDgQ7vPjy1nu1HtTGlWMjJFjj0wlbKJXirrMT4S6oA
         JuBmw5ITjmrqTwbvt3w4QCDtD1AXvRaXhA4rgIt0Ahamm1SO2YyLa79nI4CcDxVwUzY0
         1n3KYR8+cJfVKONGodA+K/2PtILXDIqd0+4Xs9iOFX27cCeGB3/xEPCsi+epqeihNTen
         LkRuJIP/X30ot+L+Q18yPH7+a27myCeFrZorkq9DIzzB6bf2/zUS8UDM710DAVQt9fLR
         lEQQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:in-reply-to:references:from:date
         :message-id:subject:to:cc;
        bh=0P33YPJPPoNuSR9B4yx61LSi2AdFarqiCrzZEdImqgs=;
        b=FL6/Tk/UVs5rDlcPOAnV6UTGRv6HnrpwjuHDUKMVrCnAX8Xhd5GtlfJqR1xng306nl
         d9JETlWzBWIrC7Z9c2mLMj6zE2WNuwc/vZn+TLC3KPq7d35vmPyZXkHStyFVm1Lp48zp
         0IpI1PLuknAe3LOI45+j75qcfJEIa5XJQCvZSb+TWyTQkxkGPbkcpU+/van5+aPdiP3A
         IxMm8AfED7otHFkpfRgcq5Yf4wGaQW+c58dGYZbtSJTPQEGK/j6VfNTgbnlCthrK6I1N
         o/ZAbB12vqIYShnyylwNxRM6Pl6pX9qWh38APfzniPgAhkfFL5xwYPDeT8isPxv7Zh4W
         KL9g==
X-Gm-Message-State: AIkVDXL0N4BD6mkmDl/CriUq+m0sQTVAu5UdXl4y7u2M8FnoTeBoMHXBX+9FYnZicFBaqIh2+1y1SE2NDZ7ohA==
X-Received: by 10.107.59.193 with SMTP id i184mr21311524ioa.86.1484392565749;
 Sat, 14 Jan 2017 03:16:05 -0800 (PST)
MIME-Version: 1.0
In-Reply-To: <83h951c41o.fsf@gnu.org>
References: <CAA2C=vAxwXB1-nsiDMmKQLt7rmkFHonK-8Cxqx4M_2uKN7ZzPA AT mail DOT gmail DOT com>
 <83h951c41o DOT fsf AT gnu DOT org>
From: "Ozkan Sezer (sezeroz AT gmail DOT com) [via djgpp-workers AT delorie DOT com]" <djgpp-workers AT delorie DOT com>
Date: Sat, 14 Jan 2017 14:16:05 +0300
Message-ID: <CAA2C=vAQsONZ-bG1dnoso3RWno6bDWGeDhnMJk33RypA5JjG=A@mail.gmail.com>
Subject: Re: memory.h
To: djgpp AT delorie DOT com
Cc: djgpp-workers AT delorie DOT com
Content-Type: text/plain; charset=UTF-8
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On 1/14/17, Eli Zaretskii (eliz AT gnu DOT org) [via djgpp AT delorie DOT com]
<djgpp AT delorie DOT com> wrote:
>> From: "Ozkan Sezer (sezeroz AT gmail DOT com) [via djgpp AT delorie DOT com]"
>> <djgpp AT delorie DOT com>
>> Date: Sat, 14 Jan 2017 12:36:44 +0300
>> Cc: djgpp AT delorie DOT com
>>
>> Why is djgpp memory.h including stdlib.h and not string.h?
>
> Maybe because Borland's headers did that?  DJGPP historically tried to
> emulate Borland's compilers.  I don't have any of them installed
> anymore to see what they did, though.
>

I just installed bcc55 free version (freecommandlinetools.exe) under wine
and its memory.h includes mem.h which in turn prototypes several string.h
stuff like memcmp, memcpy, memset, etc.

IMO, there is no excuse in including stdlib.h instead of string.h from
memory.h.  Possibly it was a typo?