Issue #14366 has been updated by shyouhei (Shyouhei Urabe).

Status changed from Open to Rejected

Let me reject this.  Using long long when available must never be a bad thing.

Also, we do check availability of long long using configure. If you really have to kill long long, try `configure --with-gcc="gcc --pedantic-errors"` or something like that.

----------------------------------------
Bug #14366: Not possible to compile ruby C extension when using `-std=c90`
https://bugs.ruby-lang.org/issues/14366#change-69606

* Author: graywolf (Gray Wolf)
* Status: Rejected
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: ruby 2.5.0p0 (2017-12-25 revision 61468) [i386-mingw32]
* Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN
----------------------------------------
DeveloperHowto says that ruby should be C90, not C99, however it's not possible
to compile C extension using `-std=c90` command line argument with error:

```
C:/Ruby25/include/ruby-2.5.0/ruby/defines.h:224:25: warning: ISO C90 does not support 'long long' [-Wlong-long]

 # define LONG_LONG long long
```

as far a I can tell, `long long` is only defined by `C99`, so `defines.h`
probably shouldn't contain it.




-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>