ith shared POSIX extensions
considered?
I'm not sure either. We try to be strict to avoid inadvertent porting
issues, but MAP_ANON is supported on so many platforms that we might
just leave it in posix.
I'd be okay with that. Anyhow it's important we remove the deprecation
m
On Tuesday, 17 February 2015 at 08:59:48 UTC, Martin Nowak wrote:
I'm not sure either. We try to be strict to avoid inadvertent
porting issues, but MAP_ANON is supported on so many platforms
that we might just leave it in posix.
https://github.com/D-Programming-Language/druntime/pull/1176
On 2015-02-17 00:00, Vladimir Panteleev wrote:
Isn't it already "published"?
http://dlang.org/changelog.html
Not the first place I would go looking for an upcoming release. It would
be better to have a proper page for a road map/plan.
--
/Jacob Carlborg
I'm not sure either. We try to be strict to avoid inadvertent
porting issues, but MAP_ANON is supported on so many platforms
that we might just leave it in posix.
On Monday, 16 February 2015 at 20:31:22 UTC, Andrei Alexandrescu
wrote:
Martin, as our release czar you may want to publish the planned
ship date. -- Andrei
Isn't it already "published"?
http://dlang.org/changelog.html
On 2/16/15 12:23 PM, Jacob Carlborg wrote:
On 2015-02-16 17:51, Gary Willoughby wrote:
I agree.
To be brutally honest the biggest release mistakes (which seems to be
getting worse lately) are D releases with outstanding regressions.
That's pretty unacceptable IMHO.
Yes, and that someone thin
On 2015-02-16 17:51, Gary Willoughby wrote:
I agree.
To be brutally honest the biggest release mistakes (which seems to be
getting worse lately) are D releases with outstanding regressions.
That's pretty unacceptable IMHO.
Yes, and that someone thinks we need release on a specific date, even
On Monday, 16 February 2015 at 16:00:29 UTC, ketmar wrote:
we can't. this issue, for example, was known for monthes (or,
maybe,
years?), yet there is no sign that it's something that MUST be
fixed for
release.
what i want to tell is that there is no release plan, no
feature freeze
before rele
On Sun, 15 Feb 2015 18:19:49 -0800, Andrei Alexandrescu wrote:
> Folks, we want to get 2.067 out the door on March 1. That's two short
> weeks from now. We really need all hands on deck to make this a
> successful release.
we can't. this issue, for example, was known for monthes (or, maybe,
year
is the right fix here?
The line above the faulting one is:
version(linux) import core.sys.linux.sys.mman : MAP_ANON;
I imagine the fix would be along the same line :)
version(OSX) import core.sys.osx.sys.mman : MAP_ANON;
std.mmfile is one of the legacy modules, in good need of a rewrite or
On Sunday, 15 February 2015 at 21:32:53 UTC, David Nadlinger
wrote:
Import core.sys.osx et al. instead (you might need to make sure
that it takes predenence). If I remember correctly, the
rationale behind the change(s) was that core.sys.posix should
only have the symbols that are actually manda
faulting one is:
version(linux) import core.sys.linux.sys.mman : MAP_ANON;
I imagine the fix would be along the same line :)
version(OSX) import core.sys.osx.sys.mman : MAP_ANON;
std.mmfile is one of the legacy modules, in good need of a
rewrite or overhaul.
On Sunday, 15 February 2015 at 21:26:27 UTC, Andrei Alexandrescu
wrote:
Building Phobos yields:
std/mmfile.d(332): Deprecation: alias
core.sys.posix.sys.mman.MAP_ANON is deprecated - Please use
core.sys.osx.sys.mman for non-POSIX extensions
What is the right fix here?
Import core.sys.osx e
Building Phobos yields:
std/mmfile.d(332): Deprecation: alias core.sys.posix.sys.mman.MAP_ANON
is deprecated - Please use core.sys.osx.sys.mman for non-POSIX extensions
What is the right fix here?
Thanks,
Andrei
14 matches
Mail list logo
