cvs.gedasymbols.org/archives/browse.cgi | search |
Date: | Mon, 22 Sep 1997 09:42:27 +0300 (IDT) |
From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
To: | "A. Sinan Unur" <asu1 AT cornell DOT edu> |
cc: | djgpp AT delorie DOT com |
Subject: | Re: *.C on Windows 95 (was: Stupid problem) |
In-Reply-To: | <342611AA.C1F03DBB@cornell.edu> |
Message-ID: | <Pine.SUN.3.91.970922093824.11513A-100000@is> |
MIME-Version: | 1.0 |
On Mon, 22 Sep 1997, A. Sinan Unur wrote: > D:\djgpp\C\TEST\b> for %f in (*.c) do gcc -c %f > > D:\djgpp\C\TEST\b> gcc -c PROG.C > > hence prog.c will be compiled as C++. But the same happens on plain DOS, I think. `for' always expands the files in UPPER CASE on plain DOS, so this is actually something that had no solution on DOS (except to not use `for' when compiling) and Windows 95 have corrected this. Am I missing something?
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |