Re: default opAssign(string) behaviour

2010-01-28 Thread strtr
Thanks, now it looks obviously messy to me as well :)

Re: default opAssign(string) behaviour

2010-01-28 Thread Simen kjaeraas
On Thu, 28 Jan 2010 09:02:12 +0100, Simen kjaeraas wrote: On Thu, 28 Jan 2010 02:32:20 +0100, strtr wrote: Personally, I use (D1)std2.conv a lot to get values from strings and thus would love the following default behaviour for all types: int i = "0"; // i = 0 i = cast( int ) "0"; // i

Re: default opAssign(string) behaviour

2010-01-28 Thread Steven Schveighoffer
On Wed, 27 Jan 2010 20:32:20 -0500, strtr wrote: Personally, I use (D1)std2.conv a lot to get values from strings and thus would love the following default behaviour for all types: int i = "0"; // i = 0 Um... why? How is int i = 0; more difficult to use/understand than int i = "0"; If

Re: default opAssign(string) behaviour

2010-01-28 Thread Pelle MÃ¥nsson
On 01/28/2010 02:32 AM, strtr wrote: Personally, I use (D1)std2.conv a lot to get values from strings and thus would love the following default behaviour for all types: int i = "0"; // i = 0 i = cast( int ) "0"; // i = 48 ( If I read the utf8 table correctly ) What keeps this from being the ca

Re: default opAssign(string) behaviour

2010-01-28 Thread Simen kjaeraas
On Thu, 28 Jan 2010 02:32:20 +0100, strtr wrote: Personally, I use (D1)std2.conv a lot to get values from strings and thus would love the following default behaviour for all types: int i = "0"; // i = 0 i = cast( int ) "0"; // i = 48 ( If I read the utf8 table correctly ) What keeps this fr

default opAssign(string) behaviour

2010-01-27 Thread strtr
Personally, I use (D1)std2.conv a lot to get values from strings and thus would love the following default behaviour for all types: int i = "0"; // i = 0 i = cast( int ) "0"; // i = 48 ( If I read the utf8 table correctly ) What keeps this from being the case?