Re: python vs d

2014-04-29 Thread Paulo Pinto via Digitalmars-d
On Monday, 28 April 2014 at 22:31:58 UTC, bearophile wrote: Paulo Pinto: Pascal expatriates like myself won't consider indexes from 1 a design mistake. :) What's the good of having all arrays always start from index 1 (this is different from Ada, where you can choose the indexing range and

Re: python vs d

2014-04-29 Thread Paulo Pinto via Digitalmars-d
On Tuesday, 29 April 2014 at 08:21:04 UTC, John Colvin wrote: On Monday, 28 April 2014 at 23:02:03 UTC, bearophile wrote: I think it could be a good idea to add something intermediate to D: optional strong typing for array indexing. I'd like to write a DIP on this someday (note that this does

Re: D For A Web Developer

2014-04-29 Thread Paulo Pinto via Digitalmars-d
Am 29.04.2014 19:45, schrieb Nick Sabalausky: On 4/29/2014 11:55 AM, Etienne wrote: On 2014-04-29 11:27 AM, Adam D. Ruppe wrote: I recently started a Ruby on Rails job and using it makes me really, really miss the high productivity and ease of use D offers. (And, of course, a dynamic site in D

Re: python vs d

2014-04-28 Thread Paulo Pinto via Digitalmars-d
Am 28.04.2014 22:31, schrieb bearophile: Chris: Especially in the scientific community Python is popular because one can protoype very fast, test things etc. However, as the code base grows it becomes more and more obvious that Python is too slow and doesn't scale very well. Julia seems to

Re: DIP60: @nogc attribute

2014-04-19 Thread Paulo Pinto via Digitalmars-d
On Saturday, 19 April 2014 at 05:08:06 UTC, froglegs wrote: Also possible in C# with structs, interop annotations and unsafe blocks. And now you aren't using the language, but a (very) poor subset of a language that doesn't even support templates. Doesn't change the fact it is

Re: DIP60: @nogc attribute

2014-04-18 Thread paulo Pinto via Digitalmars-d
On Wednesday, 16 April 2014 at 22:11:23 UTC, froglegs wrote: I am really looking forward to .NET Native becoming widespread. Then this type of comparisons (C# vs C++) will be quite different. I don't think it will make a major difference. Taking a GC based language and giving it a

Re: DIP60: @nogc attribute

2014-04-17 Thread Paulo Pinto via Digitalmars-d
On Thursday, 17 April 2014 at 04:19:00 UTC, Manu via Digitalmars-d wrote: On 17 April 2014 09:20, Walter Bright via Digitalmars-d digitalmars-d@puremagic.com wrote: On 4/16/2014 3:42 PM, Adam Wilson wrote: ARC may in fact be the most advantageous for a specific use case, but that in no way

Re: DIP60: @nogc attribute

2014-04-17 Thread Paulo Pinto via Digitalmars-d
On Thursday, 17 April 2014 at 08:05:42 UTC, Ola Fosheim Grøstad wrote: On Thursday, 17 April 2014 at 06:56:11 UTC, Paulo Pinto wrote: There is a reason why Dalvik is being replaced by ART. AoT compilation? Not only. Dalvk was left to bit rotten and has hardly seen any updates since 2.3.

Re: DIP60: @nogc attribute

2014-04-17 Thread Paulo Pinto via Digitalmars-d
On Thursday, 17 April 2014 at 08:52:28 UTC, Ola Fosheim Grøstad wrote: On Thursday, 17 April 2014 at 08:22:32 UTC, Paulo Pinto wrote: Of course it was sold at WWDC as ARC is better than GC and not as ARC is better than the crappy GC implementation we have done. I have never seen a single

Re: DIP60: @nogc attribute

2014-04-17 Thread Paulo Pinto via Digitalmars-d
On Thursday, 17 April 2014 at 09:55:38 UTC, Ola Fosheim Grøstad wrote: On Thursday, 17 April 2014 at 09:32:52 UTC, Paulo Pinto wrote: Any iOS device runs circles around those systems, hence why I always like to make clear it was Apple's failure to make a workable GC in a C based language and

Re: DIP60: @nogc attribute

2014-04-16 Thread Paulo Pinto via Digitalmars-d
On Wednesday, 16 April 2014 at 09:17:48 UTC, Ola Fosheim Grøstad wrote: On Wednesday, 16 April 2014 at 09:03:22 UTC, JN wrote: I'd have to agree. I doubt @nogc will change anything, people will just start complaining about limitations of @nogc (no array concat, having to use own libraries

Re: DIP60: @nogc attribute

2014-04-16 Thread Paulo Pinto via Digitalmars-d
On Wednesday, 16 April 2014 at 11:51:07 UTC, Manu via Digitalmars-d wrote: On 16 April 2014 19:03, JN via Digitalmars-d digitalmars-d@puremagic.comwrote: On Wednesday, 16 April 2014 at 01:57:29 UTC, Mike wrote: I don't believe users hesitant to use D will suddenly come to D now that there

Re: D gc on local objects

2014-04-16 Thread Paulo Pinto via Digitalmars-d
Am 16.04.2014 18:51, schrieb Adam D. Ruppe: This is one of the things the `scope` storage class on local variables can do, but since it isn't implemented properly, it is not memory safe and thus its usage is deprecated. I really really really want to see scope be fully implemented, including

Re: DIP60: @nogc attribute

2014-04-16 Thread Paulo Pinto via Digitalmars-d
Am 16.04.2014 22:49, schrieb froglegs: Well, most of the new games (Unity3D) are done in C# nowadays and people live with it even though game development is one of the biggest C++ loving and GC hating crowd there is. Unity3D the engine is written primarily in C++, not C#. The Unity editor

Re: Safe method wont check dangling pointer?

2014-04-15 Thread Paulo Pinto via Digitalmars-d
On Tuesday, 15 April 2014 at 09:33:19 UTC, bearophile wrote: Walter Bright: Valgrind is an incredibly useful tool, but programs run terribly slowly under it. On the other hand the C/C++ world in the last years has seen numerous advancements that D should keep an eye on. If you look at the

Re: Safe method wont check dangling pointer?

2014-04-15 Thread Paulo Pinto via Digitalmars-d
Am 15.04.2014 13:05, schrieb bearophile: Paulo Pinto: Except, as far as I am aware, they only work on GNU/Linux and Mac OS X, leaving out all other operating systems out there. Is -fsanitize=integer not available in the Windows version of Clang? Perhaps it's a good idea to create something

<    3   4   5   6   7   8