Re: Wed Oct 17 - Avoiding Code Smells by Walter Bright

2018-10-30 Thread Nicholas Wilson via Digitalmars-d-announce
On Wednesday, 31 October 2018 at 05:00:12 UTC, myCodeDontSmell 
wrote:
I did find it confusing however, that you discuss leaky 
abstractions, and putting your public interface at the 
beginning of your code (and all the other crap below it)... but 
then, in D, once your write your abstraction, say a class, with 
it's public interface, all the code below it can do whatever it 
likes to that class, making it a leaky abstraction.


That's sure sound like code smell to me.

i.e. A class (perhaps one of the most important abstractions in 
programming) within a module, is *always* a leaky abstraction 
(within the module), because of the way the code further down 
can just ignore the interface. In fact, there is no way at all 
to ensure code below the class uses that interface.


So I can't help but see contradictions everywhere, in D.


That is by design, because in D the unit of abstraction is the 
module, not the class.
Running into such problems is a sign that your module is too 
large, and should become a package.


Re: Wed Oct 17 - Avoiding Code Smells by Walter Bright

2018-10-30 Thread myCodeDontSmell via Digitalmars-d-announce

On Friday, 19 October 2018 at 03:53:12 UTC, Walter Bright wrote:


Had a nice crowd there last night. Apparently lots of people 
were interested in this topic!


Video: 
https://www.youtube.com/watch?v=lbp6vwdnE0k=youtu.be



Interesting talk. Thanks for the link.

I did find it confusing however, that you discuss leaky 
abstractions, and putting your public interface at the beginning 
of your code (and all the other crap below it)... but then, in D, 
once your write your abstraction, say a class, with it's public 
interface, all the code below it can do whatever it likes to that 
class, making it a leaky abstraction.


That's sure sound like code smell to me.

i.e. A class (perhaps one of the most important abstractions in 
programming) within a module, is *always* a leaky abstraction 
(within the module), because of the way the code further down can 
just ignore the interface. In fact, there is no way at all to 
ensure code below the class uses that interface.


So I can't help but see contradictions everywhere, in D.



Re: Add D front-end, libphobos library, and D2 testsuite... to GCC

2018-10-30 Thread Joakim via Digitalmars-d-announce

On Monday, 29 October 2018 at 09:57:46 UTC, Walter Bright wrote:

On 10/28/2018 8:43 PM, Mike Parker wrote:
Congratulations are in order for Iain Buclaw. His efforts have 
been rewarded in a big way. Last Friday, he got the greenlight 
to move forward with submitting his changes into GCC:


Reddit: 
https://www.reddit.com/r/programming/comments/9sb74k/the_d_language_frontend_finally_merged_into_gcc_9/


HackerNews (at #12 on the front page):
https://news.ycombinator.com/news


On Lobsters too:

https://lobste.rs/s/9ziils/d_language_front_end_finally_merged_into


Re: usable @nogc Exceptions with Mir Runtime

2018-10-30 Thread Oleg via Digitalmars-d-announce

Thanks for your work!


Example
===
///
@safe pure nothrow @nogc
unittest
{
import mir.exception;
import mir.format;
try throw new MirException(stringBuf() << "Hi D" << 2 << 
"!" << getData);

catch(Exception e) assert(e.msg == "Hi D2!");
}

===


I don't understand why you choose C++ format style instead of 
D-style format?





Re: BindBC -- The successor to Derelict

2018-10-30 Thread Nicholas Wilson via Digitalmars-d-announce

On Tuesday, 30 October 2018 at 12:35:15 UTC, Mike Parker wrote:
Thanks! Yes, I'll port all of those over. I implemented most of 
bindbc-al the other day. I plan to sit down and finish it up 
later this week. Be forewarned though, my plans too frequently 
have a mind of their own.


Mike could you add those of us who are members of derelict to 
BindBC? I'll take a look at porting CUDA and OpenCL over to 
BindBC.


Thanks
Nic



Re: BindBC -- The successor to Derelict

2018-10-30 Thread Mike Parker via Digitalmars-d-announce

On Tuesday, 30 October 2018 at 12:17:52 UTC, Danny Arends wrote:



Nice work on the new loader, I'm a big user of the Derelict 
loader, and I agree that having a betterC / @nogc loader is a 
big win, so thanks in advance for working on it.


Which libraries are going to be supported ? In my current 
project I use the following Derelict bindings:


derelict-al
derelict-alure
derelict-vorbis
derelict-lua

Will these be ported to BindBC eventually ?

Thanks for the effort in maintaining Derelict for so long.

Danny


Thanks! Yes, I'll port all of those over. I implemented most of 
bindbc-al the other day. I plan to sit down and finish it up 
later this week. Be forewarned though, my plans too frequently 
have a mind of their own.




Re: Beta 2.082.0

2018-10-30 Thread Walter Bright via Digitalmars-d-announce

Thank you, Martin!


Re: smile.amazon.com Promotion

2018-10-30 Thread Martin Tschierschke via Digitalmars-d-announce

On Monday, 29 October 2018 at 16:40:20 UTC, FooledDonor wrote:

On Monday, 29 October 2018 at 16:01:38 UTC, Mike Parker wrote:

[...]


Perhaps a fundamental principle is not clear enough at the 
foundation: transparency.


Where is the vision of the third and fourth quarter? Where are 
the deliveries of things in the pipeline? What is the progress 
of the various jobs started?


Which people is funding, with how much money and for what 
expected results?
Where is the newCTFE? Was the work on this point financed by 
the foundation?


I've never seen a report on the state of affairs, neither from 
the president, nor from Andrei, nor from Walter.


How do you hope to obtain trust and funding, if NO one even 
deigns to give the least development plan or feedback on past 
developments?


It seems that everyone has locked up in their ivory tower ...


I want to subscribe to this points.

Before trying an other money collection system, please provide 
more transparency of the current financial situation of the 
foundation.


Regards mt.