Anoymous via Digitalmars-d | 22 Dec 20:50 2014

Does anyone want to render D with gsource ?

A few monthes ago I've seen this:

https://code.google.com/p/gource/

Does anyone want to render D with gsource (dmd/phobos) ?

DConf 2015?

By this time last year, dconf 2014 preparations were already 
under way but I haven't heard anything this year. Is another one 
planned?

deadalnix via Digitalmars-d | 22 Dec 18:25 2014

Re: Do everything in Java…

On Sunday, 21 December 2014 at 10:00:36 UTC, Russel Winder via 
Digitalmars-d wrote:
> Although the vast majority of Java is used in a basically I/O 
> bound
> context, there is knowledge of and desire to improve Java in a 
> CPU-
> bound context. The goal here is to always be as fast as C and 
> C++ for
> all CPU-bound codes. A lot of people are already seeing Java 
> being
> faster than C and C++, but they have to use primitive types to 
> achieve
> this. With the shift to internal iteration and new JITS, the 
> aim is to
> achieve even better but using reference types in the code.
>

That is quite a claim. If it is true in some context, and I'd go 
as far as to say that vanilla code in C/C++ tend to be slower 
than the vanilla version in java, ultimately, C and C++ offer 
more flexibility, which mean that if you are willing to spend the 
time to optimize, Java won't be as fast. Generally, the killer is 
memory layout, which allow to fit more in cache, and be faster. 
Java is addicted to indirections.

Allocators stack

How about allocators stack? Allocator e.g. one of these
https://github.com/andralex/phobos/blob/allocator/std/allocator.d
-------------
allocatorStack.push(new GCAllocator);
//Some code that use memory allocation
auto a = ['x', 'y'];
a ~= ['a', 'b']; // use allocatorStack.top.realloc(...);
allocatorStack.pop();
-------------
Allocators must be equipped with dynamic polymorphism. For those
cases when it is too expensive attribute
 <at> allocator(yourAllocator) applied to declaration set allocator
statically.

-------------
 <at> allocator(Mallocator.instance)
void f()
{
// Implicitly use global(tls?) allocator Mallocator when allocate 
an
object or resize an array or etc.
}

 <at> allocator("StackAllocator")
void f()
{
// Implicitly use allocatorStack.top() allocator when allocate an
object or resize an array or etc.
}
-------------
(Continue reading)

via Digitalmars-d | 22 Dec 16:36 2014

Re: Do everything in Java…

On Thursday, 18 December 2014 at 08:56:29 UTC, ketmar via 
Digitalmars-d wrote:
> On Thu, 18 Dec 2014 08:09:08 +0000
> via Digitalmars-d <digitalmars-d <at> puremagic.com> wrote:
>
>> On Thursday, 18 December 2014 at 01:16:38 UTC, H. S. Teoh via 
>> Digitalmars-d wrote:
>> > On Thu, Dec 18, 2014 at 12:37:43AM +0000, via Digitalmars-d 
>> > wrote:
>> >> Regular HD I/O is quite slow, but with fast SSD on PCIe and 
>> >> a good
>> >> database-like index locked to memory…
>> >
>> > That's hardly a solution that will work for the general D 
>> > user, many of
>> > whom may not have this specific setup.
>> 
>> By the time this would be ready, most programmers will have 
>> PCIe interfaced SSD. At 100.000 IOPS it is pretty ok.
>
> didn't i say that the whole "64-bit" hype sux? ;-) that's about 
> "memory
> as database".

Heh, btw, I just read on osnews.com that HP is going to create a 
new hardware platform The Machine and a new operating system for 
it based on resistor based non-volatile memory called memristors 
that is comparable to dram in speed. Pretty interesting actually:

http://www.technologyreview.com/news/533066/hp-will-release-a-revolutionary-new-operating-system-in-2015/
(Continue reading)

Re: ARMv7 vs x86-64: Pathfinding benchmark of C++, D, Go, Nim, Ocaml, and more.

On Monday, 22 December 2014 at 12:43:19 UTC, Iain Buclaw via 
Digitalmars-d wrote:
> On 22 December 2014 at 11:45, logicchains via Digitalmars-d
> <digitalmars-d <at> puremagic.com> wrote:
>> On Sunday, 21 December 2014 at 09:48:24 UTC, Dicebot wrote:
>>>
>>> On Saturday, 20 December 2014 at 21:47:24 UTC, Walter Bright 
>>> wrote:
>>>>
>>>> I did notice this:
>>>>
>>>> "I updated the ldc D compiler earlier today (incidentally, 
>>>> as part of
>>>> upgrading my system with pacman -Syu), and now it doesn't 
>>>> compile at all. It
>>>> was previously compiling, and ran at around 90% the speed of 
>>>> C++ on ARM."
>>>>
>>>> Sigh.
>>>
>>>
>>> I have deployed experimental LDC package exactly to be able 
>>> to detect such
>>> issues, otherwise it will never get there. It will be either 
>>> fixed within a
>>> week or reverted to old mode.
>>
>>
>> I installed the new Arch Linux LDC package but it still fails 
>> with the same
(Continue reading)

via Digitalmars-d | 22 Dec 14:45 2014

Re: ARMv7 vs x86-64: Pathfinding benchmark of C++, D, Go, Nim, Ocaml, and more.

On Monday, 22 December 2014 at 12:43:19 UTC, Iain Buclaw via
Digitalmars-d wrote:
> On 22 December 2014 at 11:45, logicchains via Digitalmars-d
> <digitalmars-d <at> puremagic.com> wrote:
>> On Sunday, 21 December 2014 at 09:48:24 UTC, Dicebot wrote:
>>>
>>> On Saturday, 20 December 2014 at 21:47:24 UTC, Walter Bright 
>>> wrote:
>>>>
>>>> I did notice this:
>>>>
>>>> "I updated the ldc D compiler earlier today (incidentally, 
>>>> as part of
>>>> upgrading my system with pacman -Syu), and now it doesn't 
>>>> compile at all. It
>>>> was previously compiling, and ran at around 90% the speed of 
>>>> C++ on ARM."
>>>>
>>>> Sigh.
>>>
>>>
>>> I have deployed experimental LDC package exactly to be able 
>>> to detect such
>>> issues, otherwise it will never get there. It will be either 
>>> fixed within a
>>> week or reverted to old mode.
>>
>>
>> I installed the new Arch Linux LDC package but it still fails 
>> with the same
(Continue reading)

Vic via Digitalmars-d | 22 Dec 13:28 2014

cross post hn: (Rust) _ _ without GC

https://news.ycombinator.com/item?id=8781522

http://arthurtw.github.io/2014/12/21/rust-anti-sloppy-programming-language.html

c'est possible!

Oh how much free time and stability there would be if D core 
*moved* GC downstream.

Vic
ps: more cows waiting for slaughter: 
http://dlang.org/comparison.html

Re: Rectangular multidimensional arrays for D

On Friday, 11 October 2013 at 22:41:06 UTC, H. S. Teoh wrote:
> What's the reason Kenji's pull isn't merged yet? As I see it, 
> it does
> not introduce any problematic areas, but streamlines 
> multidimensional
> indexing notation in a nice way that fits in well with the rest 
> of the
> language. I, for one, would push for it to be merged.
>
> In any case, I've seen your multidimensional array 
> implementation
> before, and I think it would be a good thing to have it in 
> Phobos. In
> fact, I've written my own as well, and IIRC one or two other 
> people have
> done the same. Clearly, the demand is there.
>
> See also the thread about std.linalg; I think before we can 
> even talk
> about having linear algebra code in Phobos, we need a 
> solidly-designed
> rectangular array API. As I said in that other thread, matrix 
> algebra
> really should be built on top of a solid rectangular array API, 
> and not
> be yet another separate kind of type that's similar to, but 
> incompatible
> with rectangular arrays. A wrapper type can be used to make a
> rectangular array behave in the linear algebra sense (i.e. 
> matrix
(Continue reading)

via Digitalmars-d | 21 Dec 23:02 2014

Re: What is the D plan's to become a used language?

On Sunday, 21 December 2014 at 10:26:45 UTC, Russel Winder via 
Digitalmars-d wrote:
> to C++14 rather than D. Most C people will move to Go rather 
> than C++ or D.

I would not use Go for anything I would consider C for atm, but I 
will move some stuff from Python to Go when it is supported on 
GAE…

D could find it's own niche in a competing cloud solution, like 
Amazon WS, if it was deliberately targeted and thus the most 
convenient language on the platform.

Being the most convinient language for a platform is the killer 
app par excellence, but you need to be stable, production ready 
and focused to do it, which requires planning!

> Perhaps like Haskell, D is doomed to be a language used by few, 
> but
> having enormous influence on other languages that are used by 
> many.

What language-features are unique to D?

> achieves nothing. Having a reputation for internal angst and a 
> bad
> garbage collector achieves huge negative waves. A language 11 
> years
> old and still in the same "breaking change" situation as Rust, 
> yet
(Continue reading)

Joakim via Digitalmars-d | 21 Dec 12:18 2014

Re: What is the D plan's to become a used language?

On Sunday, 21 December 2014 at 10:26:45 UTC, Russel Winder via 
Digitalmars-d wrote:
> D was started as a better C++. Technically that may be true, 
> but it
> has failed to gain traction in the market.  Most C++ people 
> will move
> to C++14 rather than D. Most C people will move to Go rather 
> than C++
> or D.

These two developments don't necessarily mean much for D.  C/C++ 
devs are not going to give up their big investments in their 
existing source and knowledge unless D presents some big wins, 
real world success like Sociomantic.  Until then, it's more 
likely that D's traction will come from the new and disaffected.  
If they succeed, C/C++ devs will copy them and switch over, or 
their bosses will make them. ;)

> It doesn't matter that Go may have arrived on a wave of hype, 
> the
> language appealed to some high profile people who did things 
> with it
> and showed how much better it was than the alternatives. For 
> these
> people the alternatives were C and C++. D and Rust are just not 
> in the
> game, though Rust when it gets to 1.0 will have an opportunity.
>  Go
> now has street cred. The biggest angst is now about whether 
> Google
(Continue reading)


Gmane