March 19, 2004 Re: [VOTE:] Should the cast operator be mandatory? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Matthew | Another "yes" "Matthew" <matthew@stlsoft.org> wrote in message news:c39fo1$1iq4$3@digitaldaemon.com... > Matthew: Yes > > |
March 23, 2004 Re: [VOTE:] Should the cast operator be mandatory? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Matthew | The cast operator is broken; it should be "cast (a, b)", so no. Having a non-broken alternative that at least has the benefit of being historic is better than one which makes code look like crap. |
March 23, 2004 Re: [VOTE:] Should the cast operator be mandatory? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Burton Radons | In article <c3oo6k$2v44$1@digitaldaemon.com>, Burton Radons says... > >The cast operator is broken; it should be "cast (a, b)", so no. Having a non-broken alternative that at least has the benefit of being historic is better than one which makes code look like crap. We discussed alternative cast sintax, the one that looks better is a.castTo(B) however seems to have been rejected by Walter. (were you here at that time?) the problem with cast(a,b) is that it's not explicit whit is the type. Ant |
March 24, 2004 Re: [VOTE:] Should the cast operator be mandatory? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Ant | Ant wrote: > In article <c3oo6k$2v44$1@digitaldaemon.com>, Burton Radons says... > >>The cast operator is broken; it should be "cast (a, b)", so no. Having a non-broken alternative that at least has the benefit of being historic is better than one which makes code look like crap. > > > We discussed alternative cast sintax, the one that looks better is > a.castTo(B) > however seems to have been rejected by Walter. > (were you here at that time?) I wasn't. But I don't like fake methods and properties; they get into a lot of unintentional conflicts and method conflicts are much messier than function conflicts. > the problem with cast(a,b) is that it's not explicit whit is > the type. Eh? You don't have any functions or methods that take more than one argument? Just have an explicit error in the compiler; a couple doses of that and one shouldn't make the mistake ever again. |
March 24, 2004 Re: [VOTE:] Should the cast operator be mandatory? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Burton Radons | Burton Radons wrote:
> The cast operator is broken; it should be "cast (a, b)", so no. Having a non-broken alternative that at least has the benefit of being historic is better than one which makes code look like crap.
I like it. It looks like a cast and not a function call. It's also easy for a compiler to parse and for a programmer to recognize.
-- andy
|
Copyright © 1999-2021 by the D Language Foundation