Re: DIP 1024---Shared Atomics---Accepted

2020-01-02 Thread Manu via Digitalmars-d-announce
On Fri, Jan 3, 2020 at 9:20 AM Walter Bright via
Digitalmars-d-announce  wrote:
>
> On 1/2/2020 4:17 AM, Manu wrote:
> > On Thu, Jan 2, 2020 at 7:45 PM Walter Bright via
> > Digitalmars-d-announce  wrote:
> >>
> >> On 1/2/2020 12:01 AM, Manu wrote:
> >>> Quick quick, we need a PR to issue deprecation messages for those
> >>> invalid read/writes! :)
> >>
> >> It's already been merged!
> >>
> >> https://github.com/dlang/dmd/pull/10209
> >>
> >> Some really fast work there :-)
> >
> > Doesn't the acceptance of the DIP suggest that it should no longer be
> > `-preview`; it should be enabled and an option to disable the feature
> > via `-revert` should be introduced?
>
> We switch to -revert after some time has passed (a year or two) so people have
> time to adapt.
>
> > Or short of that, a deprecation message should be emit when compiling?
>
> I'm not sure that's necessary with the preview/revert switches.

Okay, although I don't really understand; if we have accepted the
feature, but we don't enable the feature... then nobody will use it,
and no code will be written that's compatible.
This kinda seems like a future-acceptance?
Nobody enables `-preview`s.


Re: DIP 1024---Shared Atomics---Accepted

2020-01-02 Thread Walter Bright via Digitalmars-d-announce

On 1/2/2020 4:17 AM, Manu wrote:

On Thu, Jan 2, 2020 at 7:45 PM Walter Bright via
Digitalmars-d-announce  wrote:


On 1/2/2020 12:01 AM, Manu wrote:

Quick quick, we need a PR to issue deprecation messages for those
invalid read/writes! :)


It's already been merged!

https://github.com/dlang/dmd/pull/10209

Some really fast work there :-)


Doesn't the acceptance of the DIP suggest that it should no longer be
`-preview`; it should be enabled and an option to disable the feature
via `-revert` should be introduced?


We switch to -revert after some time has passed (a year or two) so people have 
time to adapt.



Or short of that, a deprecation message should be emit when compiling?


I'm not sure that's necessary with the preview/revert switches.



Re: When will you announce DConf 2020?

2020-01-02 Thread Murilo via Digitalmars-d-announce

On Sunday, 3 November 2019 at 06:33:48 UTC, Mike Parker wrote:

On Sunday, 3 November 2019 at 00:51:38 UTC, Murilo wrote:
Hi guys. I'm eager to attend the next DConf, which is why I'm 
already planning everything about how I will travel from 
Brazil to the UK(or maybe Germany). When will you announce the 
place and date of the next DConf?


When our plans are finalized.


Do you already know in which country it will happen?


Re: My Android project nearing beta

2020-01-02 Thread Adam D. Ruppe via Digitalmars-d-announce

On Thursday, 2 January 2020 at 20:26:05 UTC, visitor wrote:

i see you updated everything ! wow !! :))


yea, the setup program should now download the runtime binaries 
for you and set up ldc2.conf fairly automatically (I haven't 
tested on Windows yet though and of course it will static assert 
on Mac but should be easy fix when I get to it).


Getting there. I think I have a plan for making new Java classes 
from D too that I'll play with when I get more time...



just a note : i had to add a sourceSets instruction


hmm, ok, I didn't have to do that on mine but I can add a note to 
the docs for others.


tbh I don't really understand very much about android and the 
ide. I've never actually made an android app myself and never 
actually even heard of gradle before I started playing with 
this


Re: My Android project nearing beta

2020-01-02 Thread visitor via Digitalmars-d-announce

On Wednesday, 1 January 2020 at 18:15:32 UTC, Adam D. Ruppe wrote:

i see you updated everything ! wow !! :))

just a note : i had to add a sourceSets instruction
```
android {
...
defaultConfig {
...
}
sourceSets {
main {
// let gradle pack the shared library into apk
jniLibs.srcDirs = ['./src/main/jniLibs']
}
}
...
}
```
in the build.gradle file (the one in app directory) of the test 
application


it didn't pack the library in the apk otherwise, in my setup 
(which is plain basic, probably not relevant anyway)






Re: Bison 3.5 is released, and features a D backend

2020-01-02 Thread Basile B. via Digitalmars-d-announce

On Wednesday, 1 January 2020 at 09:47:11 UTC, Akim Demaille wrote:

Hi all!

GNU Bison 3.5 was released with a D backend
(https://savannah.gnu.org/forum/forum.php?forum_id=9639).  This 
backend is
functional, and you can get a sense of its current shape by 
looking at the

shipped example (a calculator, what did you expect?):
https://github.com/akimd/bison/blob/master/examples/d/calc.y.

Bison is an LR parser generator.  It supports not only Yacc's 
original
LALR(1) parsers, but also canonical LR and IELR(1) which are 
strictly more
powerful (meaning: they accept wider classes of languages).  It 
also
features Generalized LR, which can even parse ambiguous 
grammars.


The D backend currently does not support the full range of 
Bison features.
We desperately need some skilled D programmer(s) to support 
this backend.


It was first contributed by Oliver Mangold, based on Paolo 
Bonzini's Java
backend.  It was cleaned and improved thanks to H. S. Teoh, yet 
it's
certainly not yet fitting perfectly the D spirit.  Since the 
backend is
still experimental, there is flexibility: it can be changed and 
improved

until it meets the D community standards.

If you would like to contribute, please reach out to us via
bison-patc...@gnu.org, or help-bi...@gnu.org.

Best wishes for 2020.  Cheers!


nice, thanks


Re: DIP 1024---Shared Atomics---Accepted

2020-01-02 Thread Manu via Digitalmars-d-announce
On Thu, Jan 2, 2020 at 7:45 PM Walter Bright via
Digitalmars-d-announce  wrote:
>
> On 1/2/2020 12:01 AM, Manu wrote:
> > Quick quick, we need a PR to issue deprecation messages for those
> > invalid read/writes! :)
>
> It's already been merged!
>
> https://github.com/dlang/dmd/pull/10209
>
> Some really fast work there :-)

Doesn't the acceptance of the DIP suggest that it should no longer be
`-preview`; it should be enabled and an option to disable the feature
via `-revert` should be introduced?
Or short of that, a deprecation message should be emit when compiling?


DIP 1028---Make @safe the Default---Community Review Round 1 Begins

2020-01-02 Thread Mike Parker via Digitalmars-d-announce
The first round of Community Review for DIP 1028, "Make @safe the 
Default", has begun. To participate, please visit the review 
thread for the details:


https://forum.dlang.org/post/ejaxvwklkyfnksjkl...@forum.dlang.org

*Please leave all feedback in the review thread rather than here!*

Thanks!


Re: DIP 1024---Shared Atomics---Accepted

2020-01-02 Thread Walter Bright via Digitalmars-d-announce

On 1/2/2020 12:01 AM, Manu wrote:

Quick quick, we need a PR to issue deprecation messages for those
invalid read/writes! :)


It's already been merged!

https://github.com/dlang/dmd/pull/10209

Some really fast work there :-)


Re: DIP 1024---Shared Atomics---Accepted

2020-01-02 Thread Manu via Digitalmars-d-announce
On Thu, Jan 2, 2020 at 4:45 PM Walter Bright via
Digitalmars-d-announce  wrote:
>
> On 1/1/2020 9:53 PM, Manu wrote:
> > On Thu, Jan 2, 2020 at 3:40 PM Mike Parker via Digitalmars-d-announce
> >  wrote:
> >>
> >> DIP 1024, "Shared Atomics", was accepted without comment.
> >>
> >> https://github.com/dlang/DIPs/blob/master/DIPs/accepted/DIP1024.md
> >
> > This has been a long time coming!
>
> A New Year's present for all of us!

Quick quick, we need a PR to issue deprecation messages for those
invalid read/writes! :)