On 2 February 2015 at 23:56, Jonathan Wakely jwakely@gmail.com wrote:
On 2 February 2015 at 21:11, Jonny Grant wrote:
Is this a consensus agreement to rename those .C - .cc ?
No.
While I remember:
Stroustrup lists C++ extensions as .cxx and .cpp
http://www.stroustrup.com/glossary.html
On 16 February 2015 at 17:45, Jonny Grant wrote:
While I remember:
Stroustrup lists C++ extensions as .cxx and .cpp
http://www.stroustrup.com/glossary.html
ISO sample sources use .cpp:
http://standards.iso.org/ittf/PubliclyAvailableStandards/c043351_ISO_IEC_TR_18015_2006(E).zip
.C in GCC
On Sat, 2015-02-07 at 23:17 +, Jonny Grant wrote:
On 03/02/15 23:20, Andreas Schwab wrote:
Jonny Grant j...@jguk.org writes:
How many minutes labor is this task?
What does it fix?
Consistency. Less important if these files are only compiled after GCC
available, to use as a
On 03/02/15 23:20, Andreas Schwab wrote:
Jonny Grant j...@jguk.org writes:
How many minutes labor is this task?
What does it fix?
Consistency. Less important if these files are only compiled after GCC
available, to use as a testsuite. Although I understood from other
replies that other
On 4 February 2015 at 00:22, Kevin Ingwersen (Ingwie Phoenix) wrote:
How many hacks/workarounds can be avoided?
How many new hacks/workaround will be needed for exploring the files'
version control history, even with a VCS that supports renaming?
Renaming the files has downsides as well as
On 02/02/15 21:18, Andrew Pinski wrote:
On Mon, Feb 2, 2015 at 1:11 PM, Jonny Grant j...@jguk.org wrote:
On 01/02/15 16:34, Kevin Ingwersen (Ingwie Phoenix) wrote:
Am 01.02.2015 um 17:09 schrieb Eli Zaretskii e...@gnu.org:
Date: Sat, 31 Jan 2015 01:55:29 +
From: Jonathan Wakely
On Tue, 3 Feb 2015, Jonny Grant wrote:
There are around 11k files that have the .C ending to them; all in the
testsuite. I don't think it make sense to move them.
How many minutes labor is this task?
It's desirable for test names to be stable so that results can be compared
over time,
Jonny Grant j...@jguk.org writes:
How many minutes labor is this task?
What does it fix?
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
And now for something completely different.
Am 04.02.2015 um 00:20 schrieb Andreas Schwab sch...@linux-m68k.org:
Jonny Grant j...@jguk.org writes:
How many minutes labor is this task?
What does it fix?
How many hacks/workarounds can be avoided?
On Tue, Feb 3, 2015 at 4:22 PM, Kevin Ingwersen (Ingwie Phoenix)
ingwie2...@googlemail.com wrote:
Am 04.02.2015 um 00:20 schrieb Andreas Schwab sch...@linux-m68k.org:
Jonny Grant j...@jguk.org writes:
How many minutes labor is this task?
What does it fix?
How many hacks/workarounds can
On 01/02/15 16:34, Kevin Ingwersen (Ingwie Phoenix) wrote:
Am 01.02.2015 um 17:09 schrieb Eli Zaretskii e...@gnu.org:
Date: Sat, 31 Jan 2015 01:55:29 +
From: Jonathan Wakely jwakely@gmail.com
Cc: Andrew Pinski pins...@gmail.com, gcc@gcc.gnu.org gcc@gcc.gnu.org, Jonny
Grant
On Mon, Feb 2, 2015 at 1:11 PM, Jonny Grant j...@jguk.org wrote:
On 01/02/15 16:34, Kevin Ingwersen (Ingwie Phoenix) wrote:
Am 01.02.2015 um 17:09 schrieb Eli Zaretskii e...@gnu.org:
Date: Sat, 31 Jan 2015 01:55:29 +
From: Jonathan Wakely jwakely@gmail.com
Cc: Andrew Pinski
On 2 February 2015 at 21:11, Jonny Grant wrote:
Is this a consensus agreement to rename those .C - .cc ?
No.
On Fri, 2015-01-30 at 23:24 +0100, Kevin Ingwersen (Ingwie Phoenix)
wrote:
Am 30.01.2015 um 22:39 schrieb DJ Delorie d...@redhat.com:
pins...@gmail.com writes:
No because they are c++ code so capital C is correct.
However, we should avoid relying on case-sensitive file systems
From: DJ Delorie d...@redhat.com
Cc: gcc@gcc.gnu.org, Jonny Grant j...@jguk.org
Date: Fri, 30 Jan 2015 16:39:51 -0500
However, we should avoid relying on case-sensitive file systems
(Windows) and use .cc or .cxx for C++ files (+ is not a valid file
name character on Windows, so we can't
Date: Sat, 31 Jan 2015 01:55:29 +
From: Jonathan Wakely jwakely@gmail.com
Cc: Andrew Pinski pins...@gmail.com, gcc@gcc.gnu.org gcc@gcc.gnu.org,
Jonny Grant j...@jguk.org
These files are only compiled by GCC's own build system, with GCC's
own makefiles, so we know we invoke the C++
Am 01.02.2015 um 17:09 schrieb Eli Zaretskii e...@gnu.org:
Date: Sat, 31 Jan 2015 01:55:29 +
From: Jonathan Wakely jwakely@gmail.com
Cc: Andrew Pinski pins...@gmail.com, gcc@gcc.gnu.org gcc@gcc.gnu.org,
Jonny Grant j...@jguk.org
These files are only compiled by GCC's own build
On 1/31/2015 02:55, Jonathan Wakely wrote:
On 30 January 2015 at 21:39, DJ Delorie wrote:
pins...@gmail.com writes:
No because they are c++ code so capital C is correct.
However, we should avoid relying on case-sensitive file systems
(Windows) and use .cc or .cxx for C++ files (+ is not a
John Marino gnu...@marino.st writes:
Even if this issue is normally hidden due to gcc's makefiles
There are no makefiles involved.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
And now for something completely
Aren't current Windows file systems case-preserving? Then they
shouldn't have no problems with .C files.
They are case preserving, but not case sensitive. A wildcard search
for *.c will match foo.C and bar.c, and foo.c can be opened as FOO.C.
Am 31.01.2015 um 21:21 schrieb DJ Delorie d...@redhat.com:
Aren't current Windows file systems case-preserving? Then they
shouldn't have no problems with .C files.
They are case preserving, but not case sensitive. A wildcard search
for *.c will match foo.C and bar.c, and foo.c can be
* DJ Delorie:
pins...@gmail.com writes:
No because they are c++ code so capital C is correct.
However, we should avoid relying on case-sensitive file systems
(Windows) and use .cc or .cxx for C++ files
Aren't current Windows file systems case-preserving? Then they
shouldn't have no
31.01.2015 14:10, Florian Weimer writes:
Aren't current Windows file systems case-preserving? Then they
shouldn't have no problems with .C files.
They are, but with some limitations: you can't create two files with
names differing only by case. I didn't try API functions, but here is
how it
On Jan 30, 2015, at 4:22 AM, Jonny Grant j...@jguk.org wrote:
Hello
When I checked out from the trunk I saw that various files had .C
capital extension. Its not a big issue.. but I wondered if they should
be .c like regular source files?
No because they are c++ code so capital C is
pins...@gmail.com writes:
No because they are c++ code so capital C is correct.
However, we should avoid relying on case-sensitive file systems
(Windows) and use .cc or .cxx for C++ files (+ is not a valid file
name character on Windows, so we can't use .c++).
Am 30.01.2015 um 22:39 schrieb DJ Delorie d...@redhat.com:
pins...@gmail.com writes:
No because they are c++ code so capital C is correct.
However, we should avoid relying on case-sensitive file systems
(Windows) and use .cc or .cxx for C++ files (+ is not a valid file
name character
Am 30.01.2015 um 21:30 schrieb Jonny Grant j...@jguk.org:
On 30/01/15 17:09, pins...@gmail.com wrote:
On Jan 30, 2015, at 4:22 AM, Jonny Grant j...@jguk.org wrote:
Hello
When I checked out from the trunk I saw that various files had .C
capital extension. Its not a big
On 30/01/15 17:09, pins...@gmail.com wrote:
On Jan 30, 2015, at 4:22 AM, Jonny Grant j...@jguk.org wrote:
Hello
When I checked out from the trunk I saw that various files had .C
capital extension. Its not a big issue.. but I wondered if they should
be .c like regular source files?
No
On 30 January 2015 at 21:39, DJ Delorie wrote:
pins...@gmail.com writes:
No because they are c++ code so capital C is correct.
However, we should avoid relying on case-sensitive file systems
(Windows) and use .cc or .cxx for C++ files (+ is not a valid file
name character on Windows, so we
On 30 January 2015 at 22:24, Kevin Ingwersen (Ingwie Phoenix) wrote:
Apple’s HFS is, on a default OS X install, case insensitive.
Which doesn't matter, see my previous reply.
But .c++ is valid. .cxx sounds pretty straight forward to me, since people
also use the $CXX variable.
We already
Am 31.01.2015 um 02:57 schrieb Jonathan Wakely jwakely@gmail.com:
On 30 January 2015 at 22:24, Kevin Ingwersen (Ingwie Phoenix) wrote:
Apple’s HFS is, on a default OS X install, case insensitive.
Which doesn't matter, see my previous reply.
That is true; though its good to keep an eye
Hello
When I checked out from the trunk I saw that various files had .C
capital extension. Its not a big issue.. but I wondered if they should
be .c like regular source files?
libitm\testsuite\libitm.c++\static_ctor.C
libitm\testsuite\libitm.c++\dropref.C
libitm\testsuite\libitm.c++\eh-1.C
32 matches
Mail list logo
