Re: broken links?
Am 30.06.2014 um 01:12 schrieb Gerald Pfeifer : > On Tue, 10 Jun 2014, Hebenstreit, Michael wrote: >> you are right - must be a Firefox problem; I had no problem using wget, IE8 >> works as well >> Firefox is still redirected to https://gcc.gnu.org/pub/gcc/infrastructure/ >> though > > Does it work for you know? We made a number of changes in the last > two weeks, and Firefox 30 on GNU/Linux works for me just fine. > > Gerald Two browsers plus wget working whilst another does not work? This smells like browser cache. Clear that, and try again. Kind regards, Ingwie
Re: broken links?
Am 30.06.2014 um 01:43 schrieb Hebenstreit, Michael : > Could our firewall (plus proxy) be the reason? I still get "page no found" > for both Firefox 25 and IE > > Michael Does the proxy have a cache? Some proxys have something similar to a browser cache - in fact, more compareable with what CloudFlare does. It probably saved a copy of the URL’s result and deals it out upon request. So you might wish to check this out too.
Re: broken links?
Am 30.06.2014 um 05:22 schrieb Hebenstreit, Michael : > I tested from home to reach https://gcc.gnu.org/pub/gcc/infrastructure/ - > same result; ftp://gcc.gnu.org/pub/gcc/infrastructure/ works though. Trying > ftp from behind the company FW on FF redirects me to the htpps, though on IE > it works > > Regards > Michael So, youre actually getting protocol changed - from HTTP to HTTPS? Well, that actually has nothing to do with your internet; but Firefox itself. It is why I switched. Firefox, for some reason, attempts to go HTTPS as much as possible. Dont ask me why, it just does, from my experience...
Re: Rename C files to .c in GCC source
> Am 30.01.2015 um 21:30 schrieb Jonny Grant : > > > > On 30/01/15 17:09, pins...@gmail.com wrote: >> >> >> >> >>> On Jan 30, 2015, at 4:22 AM, Jonny Grant 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 correct. > > Ok, I see. Only ever encountered files called .cpp. > > Regards, Jonny „Valid“ extensions happen to be .cpp, .cxx, .c++, .cc or .C. Although, .C can, in rare occasions, also speak about a pre-processed .c file. But finding this case is like searching a needle in a haystack. :)
Re: Rename C files to .c in GCC source
> Am 30.01.2015 um 22:39 schrieb 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 ("+" is not a valid file
> name character on Windows, so we can't use .c++).
Apple’s HFS is, on a default OS X install, case insensitive. But .c++ is valid.
.cxx sounds pretty straight forward to me, since people also use the $CXX
variable.
Re: Rename C files to .c in GCC source
> Am 31.01.2015 um 02:57 schrieb Jonathan Wakely : > > 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 out for it. >> But .c++ is valid. .cxx sounds pretty straight forward to me, since people >> also use the $CXX variable. > > We already use .C and .cc in GCC sources, so even if we needed to > change it, it would probably be better to use .cc for consistency > rather than add a third extension. Oh, I did not know this detail since I haven’t peered into the GCC source in a felt forever. Would make sense to use .cc then if it has already been used elsewhere in the source.
Re: Rename C files to .c in GCC source
> Am 31.01.2015 um 21:21 schrieb DJ Delorie : > > >> 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. That also applies to OS X: $ head -n 1 build.it /** $ head -n 1 BUILD.IT /** $ head -n 1 BuIlD.iT /**
Re: Rename C files to .c in GCC source
> Am 01.02.2015 um 17:09 schrieb Eli Zaretskii : > >> Date: Sat, 31 Jan 2015 01:55:29 + >> From: Jonathan Wakely >> Cc: Andrew Pinski , "gcc@gcc.gnu.org" , >> Jonny Grant >> >> These files are only compiled by GCC's own build system, with GCC's >> own makefiles, so we know we invoke the C++ compiler and so the >> language isn't inferred from the file extension, and so we aren't >> relying on case-sensitive file systems. > > That is true for building GCC. But what about editors and other > development tools? They _will_ be affected. Indeed. Atom keeps thinking .C is an actual „ANSI C“ thing. If I were to make a suggestion to the GCC dev’s, then I probably could also swiftly word it as: $ find gcc-src -name "*.C“ | while read f; do mv $f $(echo $f | sed 's/\.C/\.cxx/g’); done In other words; .cxx, .cpp or .cc seems like a solution that works across platforms. Since .cc is already used at some places, I would recommend that this is to be the extension to choose. One does not neccessarily need to make a dev apply hacks all over just to start development.
Re: Rename C files to .c in GCC source
> Am 04.02.2015 um 00:20 schrieb Andreas Schwab : > > Jonny Grant writes: > >> How many minutes labor is this task? > > What does it fix? How many hacks/workarounds can be avoided?
