Consider:
try {
...
} catch (Exception) {
...
} catch (StdioException) {
...
}
The second handler never matches because StdioException is a subclass of
Exception, so the first handler will always match whatever the second
matches.
Should that be a compile-time error? I think so.
A
Andrei Alexandrescu, el 23 de noviembre a las 11:43 me escribiste:
> >Again, and in case it's hard to understand, I'm not saying the any patch
> >should be accepted. Even more, I don't think Chad's patched should be
> >accepted, I also think introducing case !: is a bad idea. I'm just saying
> >tha
Steven Schveighoffer, el 23 de noviembre a las 15:18 me escribiste:
> On Mon, 23 Nov 2009 11:10:48 -0500, Leandro Lucarella
> wrote:
>
> >Steven Schveighoffer, el 23 de noviembre a las 07:34 me escribiste:
> >>>Notice that you are using particular implementation detail (MRU
> >>>cache) to explain
Lars T. Kyllingstad wrote:
How about
auto template MixMeInAutomatically(T) { ... }
void main()
{
MixMeInAutomatically!int;
...
}
Would this be ambiguous? It would be using auto for something completely
new, but it would at least make sense. (More so th
Hello Walter,
BCS wrote:
Yes the ignition (as the the key) doesn't turn off but when the
engine quits running the ignition system (as in the magneto or that
block of epoxy and silicon under the hood) quits triggering the
spark. Tie into that.
Trying to determine if the distributor is no long
== Quote from BCS (n...@anon.com)'s article
> Hello dsimcha,
> > 3. Can we simplify this by using runtime exceptions instead of
> > compile time errors for some of this stuff? For example, every range
> > would have a hasLength() method and a length() method. If hasLength()
> > is false, length(
Hello grauzone,
Bill Baxter wrote:
We now have struct constructors that do basically the same thing as a
static opCall.
Non-static opCall should still be ok, for implementing functors, but
I
think having static opCall is just too confusing given struct
literals
/ struct constructors.
Right now
Hello dsimcha,
3. Can we simplify this by using runtime exceptions instead of
compile time errors for some of this stuff? For example, every range
would have a hasLength() method and a length() method. If hasLength()
is false, length() would throw. Though this sacrifices compile time
error
Hello Walter,
Bill Baxter wrote:
On Fri, Nov 20, 2009 at 4:05 PM, Walter Bright
wrote:
Bill Baxter wrote:
Right, but if you do define it (in order to do something extra upon
initialization -- validate inputs or what have you) then it no
longer works at compile time.
Right, but the static
Bill Baxter wrote:
On Mon, Nov 23, 2009 at 11:50 AM, Travis Boucher
wrote:
Denis Koroskin wrote:
Travis Boucher has shown his interest in contribution, but he currently
has issues with D2 not working on FreeBSD. To quote him:
I have dmd working, and druntime (which was a quick hack to make w
Bill Baxter wrote:
On Mon, Nov 23, 2009 at 2:09 PM, Steven Schveighoffer
wrote:
On Mon, 23 Nov 2009 16:33:42 -0500, dsimcha wrote:
But one of my biggest gripes about the current appending implementation,
far more
important from a practical perspective than any theoretical safety
guarantees,
On Mon, Nov 23, 2009 at 2:09 PM, Steven Schveighoffer
wrote:
> On Mon, 23 Nov 2009 16:33:42 -0500, dsimcha wrote:
>
>> But one of my biggest gripes about the current appending implementation,
>> far more
>> important from a practical perspective than any theoretical safety
>> guarantees, is
>> th
== Quote from retard (r...@tard.com.invalid)'s article
> Tue, 24 Nov 2009 00:21:41 +0300, Denis Koroskin wrote:
> > On Mon, 23 Nov 2009 23:04:54 +0300, Pelle Månsson
> > wrote:
> >
> >> dsimcha wrote:
> >>> == Quote from retard (r...@tard.com.invalid)'s article
> Mon, 23 Nov 2009 17:14:54 +00
Tue, 24 Nov 2009 00:21:41 +0300, Denis Koroskin wrote:
> On Mon, 23 Nov 2009 23:04:54 +0300, Pelle Månsson
> wrote:
>
>> dsimcha wrote:
>>> == Quote from retard (r...@tard.com.invalid)'s article
Mon, 23 Nov 2009 17:14:54 +, dsimcha wrote: [snip]
> as opposed to the
> Java way of
On Mon, 23 Nov 2009 16:33:42 -0500, dsimcha wrote:
But one of my biggest gripes about the current appending implementation,
far more
important from a practical perspective than any theoretical safety
guarantees, is
that it doesn't scale to multiple threads. I've experienced this in a
real
== Quote from Andrei Alexandrescu (seewebsiteforem...@erdani.org)'s article
> Bartosz Milewski wrote:
> > Andrei Alexandrescu Wrote:
> >
> >
> >>> Some of the points are in my message from Sat, 05:19 pm. Especially
> >>> this point: Can a conforming implementation simply re-allocate on
> >>> every
On Mon, 23 Nov 2009 23:04:54 +0300, Pelle Månsson
wrote:
dsimcha wrote:
== Quote from retard (r...@tard.com.invalid)'s article
Mon, 23 Nov 2009 17:14:54 +, dsimcha wrote:
[snip]
as opposed to the
Java way of having to use 5 different classes just to read in a file
line by line in the d
> I am not talking about version(n) here, I am talking about a standard way to
> give a constant number to the compiler that can be used as a constant inside
> the code.
I meant one of more constant numbers, of course :-)
Bye,
bearophile
On Mon, Nov 23, 2009 at 12:34 PM, Pelle Månsson wrote:
> Bill Baxter wrote:
>>
>> On Mon, Nov 23, 2009 at 12:04 PM, Pelle M�nsson
>> wrote:
>>>
>>> dsimcha wrote:
== Quote from retard (r...@tard.com.invalid)'s article
>
> Mon, 23 Nov 2009 17:14:54 +, dsimcha wrote:
> [sn
On Mon, 23 Nov 2009 15:22:35 -0500, Bill Baxter wrote:
On Mon, Nov 23, 2009 at 12:11 PM, Steven Schveighoffer
wrote:
On Mon, 23 Nov 2009 12:49:01 -0500, Bill Baxter
wrote:
I think Walter had intended template mixins to take the place of
macros. They offer some features of macros but not a
Bill Baxter wrote:
On Mon, Nov 23, 2009 at 12:04 PM, Pelle M�nsson wrote:
dsimcha wrote:
== Quote from retard (r...@tard.com.invalid)'s article
Mon, 23 Nov 2009 17:14:54 +, dsimcha wrote:
[snip]
as opposed to the
Java way of having to use 5 different classes just to read in a file
line b
On Mon, Nov 23, 2009 at 12:11 PM, Steven Schveighoffer
wrote:
> On Mon, 23 Nov 2009 12:49:01 -0500, Bill Baxter wrote:
>
>> On Mon, Nov 23, 2009 at 5:32 AM, Steven Schveighoffer
>> wrote:
>>>
>>> On Mon, 23 Nov 2009 07:38:32 -0500, Bill Baxter
>>> wrote:
>>>
On Mon, Nov 23, 2009 at 3:12 AM
On Mon, 23 Nov 2009 11:10:48 -0500, Leandro Lucarella
wrote:
Steven Schveighoffer, el 23 de noviembre a las 07:34 me escribiste:
>Notice that you are using particular implementation detail (MRU
>cache) to explain the semantics of D arrays. There is a very
>important distinction between languag
On Mon, Nov 23, 2009 at 12:04 PM, Pelle Månsson wrote:
> dsimcha wrote:
>>
>> == Quote from retard (r...@tard.com.invalid)'s article
>>>
>>> Mon, 23 Nov 2009 17:14:54 +, dsimcha wrote:
>>> [snip]
as opposed to the
Java way of having to use 5 different classes just to read in a f
On Mon, 23 Nov 2009 12:49:01 -0500, Bill Baxter wrote:
On Mon, Nov 23, 2009 at 5:32 AM, Steven Schveighoffer
wrote:
On Mon, 23 Nov 2009 07:38:32 -0500, Bill Baxter
wrote:
On Mon, Nov 23, 2009 at 3:12 AM, Don wrote:
This sounds like a job for better mixin syntax.
.
So let "template#(ar
On Mon, Nov 23, 2009 at 11:50 AM, Travis Boucher
wrote:
> Denis Koroskin wrote:
>>
>> Travis Boucher has shown his interest in contribution, but he currently
>> has issues with D2 not working on FreeBSD. To quote him:
>>
>>> I have dmd working, and druntime (which was a quick hack to make work,
>>
dsimcha wrote:
== Quote from retard (r...@tard.com.invalid)'s article
Mon, 23 Nov 2009 17:14:54 +, dsimcha wrote:
[snip]
as opposed to the
Java way of having to use 5 different classes just to read in a file
line by line in the default character encoding.
That's a library issue. Has nothin
Denis Koroskin wrote:
Travis Boucher has shown his interest in contribution, but he currently
has issues with D2 not working on FreeBSD. To quote him:
I have dmd working, and druntime (which was a quick hack to make work,
but should work well enough). The problems I am having at the moment
is
On Mon, Nov 23, 2009 at 11:43 AM, Andrei Alexandrescu
wrote:
> Leandro Lucarella wrote:
>>
>> retard, el 23 de noviembre a las 17:34 me escribiste:
>>>
>>> Mon, 23 Nov 2009 14:18:05 -0300, Leandro Lucarella wrote:
>>>
Andrei Alexandrescu, el 22 de noviembre a las 17:11 me escribiste:
>
>>
On Mon, Nov 23, 2009 at 11:33 AM, Leandro Lucarella wrote:
> I'm just saying
> that the patch was mostly turned down because he didn't asked for other
> devs permission to make the patch, not because of the quality of the patch
> (or the feature) itself. That discourages people to make patches, an
Bartosz Milewski wrote:
Andrei Alexandrescu Wrote:
Some of the points are in my message from Sat, 05:19 pm. Especially
this point: Can a conforming implementation simply re-allocate on
every expansion? You make it sound like that would violate some
performance guarantees but there are no speci
yigal chripun pisze:
aarti_pl Wrote:
Walter Bright pisze:
Don wrote:
There's not many sensible operators anyway. opPow is the only missing
one that's present in many other general-purpose languages. The only
other ones I think are remotely interesting are dot and cross product.
Yup.
Anythi
Lutger pisze:
yigal chripun wrote:
aarti_pl Wrote:
There's nothing more hideous than all those frameworks in Java/C++ that
try to re-enginer SQL into functions, templates, LINQ, whatever. SQL *is*
a perfectly designed language for its purpose and it doesn't need to be
redisnged! The only
Don:
> I meant future D flexibility.
I am not talking about version(n) here, I am talking about a standard way to
give a constant number to the compiler that can be used as a constant inside
the code. This feature doesn't reduce future D flexibility.
> I'm not a computer scientist.
You seem
Leandro Lucarella wrote:
retard, el 23 de noviembre a las 17:34 me escribiste:
Mon, 23 Nov 2009 14:18:05 -0300, Leandro Lucarella wrote:
Andrei Alexandrescu, el 22 de noviembre a las 17:11 me escribiste:
Anyway, I think Chad's proposal has not been discussed here before
being implemented, whi
dsimcha, el 23 de noviembre a las 17:27 me escribiste:
> == Quote from Leandro Lucarella (llu...@gmail.com)'s article
> > Denis Koroskin, el 23 de noviembre a las 14:26 me escribiste:
> > > On Mon, 23 Nov 2009 13:48:05 +0300, dolive wrote:
> > >
> > > >dolive дµ½:
> > > >
> > > >>thank's ddmd ! i
Denis Koroskin, el 23 de noviembre a las 20:27 me escribiste:
> >I wonder how legal is this port. I'm not trying to start a flame, really,
> >I'm curious. Did you get some kind of permission from Walter? If
> >one would
> >like to contribute, it would get some special permission too?
> >
> >Thanks
Andrei Alexandrescu Wrote:
> > Some of the points are in my message from Sat, 05:19 pm. Especially
> > this point: Can a conforming implementation simply re-allocate on
> > every expansion? You make it sound like that would violate some
> > performance guarantees but there are no specifics.
>
>
retard, el 23 de noviembre a las 17:34 me escribiste:
> Mon, 23 Nov 2009 14:18:05 -0300, Leandro Lucarella wrote:
>
> > Andrei Alexandrescu, el 22 de noviembre a las 17:11 me escribiste:
> >> Anyway, I think Chad's proposal has not been discussed here before
> >> being implemented, which makes it
On Mon, Nov 23, 2009 at 11:13 AM, Don wrote:
> Some specifics -- it'd be nice to have a Windows version specified as an
> integer. It'd be nice to have a DirectX version number. Can't do it.
>
> version(int) is like a programming language with one variable. It's
> ridiculous.
One variable, and o
bearophile wrote:
Don:
There seems to be no point in having a *single* integer value, shared
between the app and all libraries! It's just reducing future flexibility.
It doesn't reduce flexibility at all,
I meant future D flexibility.
because if you need something more complex you don't us
== Quote from retard (r...@tard.com.invalid)'s article
> Mon, 23 Nov 2009 17:14:54 +, dsimcha wrote:
> [snip]
> > as opposed to the
> > Java way of having to use 5 different classes just to read in a file
> > line by line in the default character encoding.
> That's a library issue. Has nothing
Mon, 23 Nov 2009 17:14:54 +, dsimcha wrote:
[snip]
> as opposed to the
> Java way of having to use 5 different classes just to read in a file
> line by line in the default character encoding.
That's a library issue. Has nothing to do with the language.
Mon, 23 Nov 2009 12:37:27 -0500, bearophile wrote:
> dsimcha:
>> I think D is about the
>> only language on the planet that cares about both scaling up to huge
>> million line applications and scaling down to small 500-line scripts.
>
> "Scala" means "scalable language", it's supposed to be desig
On Mon, Nov 23, 2009 at 5:32 AM, Steven Schveighoffer
wrote:
> On Mon, 23 Nov 2009 07:38:32 -0500, Bill Baxter wrote:
>
>> On Mon, Nov 23, 2009 at 3:12 AM, Don wrote:
>>
This sounds like a job for better mixin syntax.
.
So let "template#(args)" be equivalent to "mixin(template!(ar
dsimcha:
> I think D is about the
> only language on the planet that cares about both scaling up to huge million
> line
> applications and scaling down to small 500-line scripts.
"Scala" means "scalable language", it's supposed to be designed to be able to
scale both up and down :-)
Removing the
Mon, 23 Nov 2009 14:18:05 -0300, Leandro Lucarella wrote:
> Andrei Alexandrescu, el 22 de noviembre a las 17:11 me escribiste:
>> Anyway, I think Chad's proposal has not been discussed here before
>> being implemented, which makes it more difficult to accept.
>
> I think the exact opposite. It's
yigal chripun wrote:
> aarti_pl Wrote:
...
>
> There's nothing more hideous than all those frameworks in Java/C++ that
> try to re-enginer SQL into functions, templates, LINQ, whatever. SQL *is*
> a perfectly designed language for its purpose and it doesn't need to be
> redisnged! The only proble
On Mon, 23 Nov 2009 20:22:18 +0300, Leandro Lucarella
wrote:
Denis Koroskin, el 23 de noviembre a las 14:26 me escribiste:
On Mon, 23 Nov 2009 13:48:05 +0300, dolive wrote:
>dolive дµ½:
>
>>thank's ddmd ! it¡¯s too great !
>>http://www.dsource.org/projects/ddmd
>>
>>
>>dolive
>
>may I ask
== Quote from Leandro Lucarella (llu...@gmail.com)'s article
> Denis Koroskin, el 23 de noviembre a las 14:26 me escribiste:
> > On Mon, 23 Nov 2009 13:48:05 +0300, dolive wrote:
> >
> > >dolive дµ½:
> > >
> > >>thank's ddmd ! it¡¯s too great !
> > >>http://www.dsource.org/projects/ddmd
> > >>
>
Denis Koroskin, el 23 de noviembre a las 14:26 me escribiste:
> On Mon, 23 Nov 2009 13:48:05 +0300, dolive wrote:
>
> >dolive дµ½:
> >
> >>thank's ddmd ! it¡¯s too great !
> >>http://www.dsource.org/projects/ddmd
> >>
> >>
> >>dolive
> >
> >may I ask how many people work for it now ? thank's !
>
Andrei Alexandrescu, el 22 de noviembre a las 17:11 me escribiste:
> Anyway, I think Chad's proposal has not been discussed here before
> being implemented, which makes it more difficult to accept.
I think the exact opposite. It's much easier to accept (or reject)
something that have an actual imp
== Quote from bearophile (bearophileh...@lycos.com)'s article
> Don:
> > There seems to be no point in having a *single* integer value, shared
> > between the app and all libraries! It's just reducing future flexibility.
> It doesn't reduce flexibility at all, because if you need something more
>
Don:
> There seems to be no point in having a *single* integer value, shared
> between the app and all libraries! It's just reducing future flexibility.
It doesn't reduce flexibility at all, because if you need something more
complex you don't use it and nothing bad happens. You can even ignore
bearophile wrote:
Don:
So weak that they're pretty much useless:
version(integer), debug(integer)
I have used that for something unrelated that deserves (as in Fortress) a
better standard implementation (to give numeric integer/float constants during
compilation):
http://www.digitalmars.com/
Bartosz Milewski wrote:
Andrei Alexandrescu Wrote:
I'm not sure I figure what the issue is, and I'd appreciate a
rehash of the few other issues brought up. (I thought they had been
responded to.)
Some of the points are in my message from Sat, 05:19 pm. Especially
this point: Can a conforming
Steven Schveighoffer, el 23 de noviembre a las 07:34 me escribiste:
> >Notice that you are using particular implementation detail (MRU
> >cache) to explain the semantics of D arrays. There is a very
> >important distinction between language specification and compiler
> >implementation. Andrei alrea
Don:
> So weak that they're pretty much useless:
> version(integer), debug(integer)
I have used that for something unrelated that deserves (as in Fortress) a
better standard implementation (to give numeric integer/float constants during
compilation):
http://www.digitalmars.com/webnews/newsgroups
Lars T. Kyllingstad wrote:
Bill Baxter wrote:
On Mon, Nov 23, 2009 at 3:12 AM, Don wrote:
This sounds like a job for better mixin syntax.
.
So let "template#(args)" be equivalent to "mixin(template!(args))".
Then you can do
auto statement = db.execute#(`select $visitcars.name from table whe
Bill Baxter wrote:
On Mon, Nov 23, 2009 at 3:12 AM, Don wrote:
This sounds like a job for better mixin syntax.
.
So let "template#(args)" be equivalent to "mixin(template!(args))".
Then you can do
auto statement = db.execute#(`select $visitcars.name from table where
$visitcars.id > 100 && $v
On Mon, 23 Nov 2009 07:38:32 -0500, Bill Baxter wrote:
On Mon, Nov 23, 2009 at 3:12 AM, Don wrote:
This sounds like a job for better mixin syntax.
.
So let "template#(args)" be equivalent to "mixin(template!(args))".
Then you can do
auto statement = db.execute#(`select $visitcars.name from
On Sat, 21 Nov 2009 17:19:08 -0500, Bartosz Milewski
wrote:
int[] a = [0];
auto b = a;
a ~= 1;
b ~= 2;
What is a[1]?
Is this considered "stomping" and requiring a re-allocation?
Can this question be answered without the recourse to implementation,
and the MRU cache in particular?
I tho
On Sun, 22 Nov 2009 21:19:15 -0500, Bartosz Milewski
wrote:
Andrei Alexandrescu Wrote:
I'm not sure I figure what the issue is, and I'd appreciate a rehash of
the few other issues brought up. (I thought they had been responded to.)
Some of the points are in my message from Sat, 05:19 pm.
On Mon, Nov 23, 2009 at 4:27 AM, Steven Schveighoffer
wrote:
> On Fri, 20 Nov 2009 19:32:10 -0500, Bill Baxter wrote:
>
>> On Fri, Nov 20, 2009 at 4:22 PM, Justin Johansson wrote:
>>>
>>> Bill Baxter wrote:
On Fri, Nov 20, 2009 at 3:36 PM, Walter Bright
wrote:
>
> And her
On Mon, Nov 23, 2009 at 3:12 AM, Don wrote:
>> This sounds like a job for better mixin syntax.
>>.
>> So let "template#(args)" be equivalent to "mixin(template!(args))".
>>
>> Then you can do
>>
>> auto statement = db.execute#(`select $visitcars.name from table where
>> $visitcars.id > 100 && $vi
On Mon, 23 Nov 2009 15:10:44 +0300, Don wrote:
Denis Koroskin wrote:
On Mon, 23 Nov 2009 13:48:05 +0300, dolive wrote:
dolive дµ½:
thank's ddmd ! it¡¯s too great !
http://www.dsource.org/projects/ddmd
dolive
may I ask how many people work for it now ? thank's !
dolive
Just me.
T
On Thu, 19 Nov 2009 17:58:15 -0500, Bartosz Milewski
wrote:
Steven Schveighoffer Wrote:
> In fact, even after reading 4.1.9 I don't know what to expect in some
> cases. Here's an example:
>
> int[] a = [0];
> auto b = a;
> a ~= 1;
> b ~= 2;
> What is a[1]?
>
> Is this considered "stomping"
On Fri, 20 Nov 2009 19:32:10 -0500, Bill Baxter wrote:
On Fri, Nov 20, 2009 at 4:22 PM, Justin Johansson wrote:
Bill Baxter wrote:
On Fri, Nov 20, 2009 at 3:36 PM, Walter Bright
wrote:
And here I was thinking perhaps opApply should just be dumped in
favor of
ranges.
I think the opA
Yigal Chripun wrote:
Based on recent discussions on the NG a few features were
deprecated/removed from D, such as typedef and C style struct initializers.
IMO this cleanup and polish is important and all successful languages do
such cleanup for major releases (Python and Ruby come to mind). I'
Denis Koroskin wrote:
On Mon, 23 Nov 2009 13:48:05 +0300, dolive wrote:
dolive дµ½:
thank's ddmd ! it¡¯s too great !
http://www.dsource.org/projects/ddmd
dolive
may I ask how many people work for it now ? thank's !
dolive
Just me.
Travis Boucher has shown his interest in contributi
On Sat, 21 Nov 2009 14:51:02 -0500, Walter Bright
wrote:
Nick Sabalausky wrote:
Yes! Capitalization consistency in the predefined versions! If it needs
to be worded as a "removal", then "Remove version's capitalization
inconsistencies" ;). The current state of that is absolutely
ridicul
Don Wrote:
> Chad J wrote:
> > Don wrote:
> >> I quite agree. What we can do already is:
> >>
> >> auto statement = db.execute!(`select $a from table where $b > 100 && $c
> >> Like "A*"`)(visitcars.name,visitcars.id, visitcars.surname);
> >>
> >> which I personally like much better than the propos
On Thu, 19 Nov 2009 13:54:04 -0500, dsimcha wrote:
The hook doesn't sound like a bad idea, but it raises a lot of issues
with the
implementation details. These are things I could figure out given
plenty of time.
I'd like weak refs, too. However, I don't think this makes the short
list f
On Mon, 23 Nov 2009 13:48:05 +0300, dolive wrote:
dolive дµ½:
thank's ddmd ! it¡¯s too great !
http://www.dsource.org/projects/ddmd
dolive
may I ask how many people work for it now ? thank's !
dolive
Just me.
Travis Boucher has shown his interest in contribution, but he currently
ha
Chad J wrote:
Don wrote:
yigal chripun wrote:
aarti_pl Wrote:
Walter Bright pisze:
Don wrote:
There's not many sensible operators anyway. opPow is the only
missing one that's present in many other general-purpose languages.
The only other ones I think are remotely interesting are dot and
cr
dolive дµ½:
> thank's ddmd ! it¡¯s too great !
> http://www.dsource.org/projects/ddmd
>
>
> dolive
may I ask how many people work for it now ? thank's !
dolive
On Sat, 21 Nov 2009 20:21:54 + (UTC), dsimcha
wrote:
>> I guess it is possible:
>> uint[] numbers = new uint[1_000];
>> pool.parallel_each!((size_t i){
>> numbers[i] = i;
>> })(iota(0, numbers.length));
>> Though I agree it's not as cute but it is faster since the delegate is
>> c
Don wrote:
> yigal chripun wrote:
>> aarti_pl Wrote:
>>
>>> Walter Bright pisze:
Don wrote:
> There's not many sensible operators anyway. opPow is the only
> missing one that's present in many other general-purpose languages.
> The only other ones I think are remotely interesting a
yigal chripun wrote:
aarti_pl Wrote:
Walter Bright pisze:
Don wrote:
There's not many sensible operators anyway. opPow is the only missing
one that's present in many other general-purpose languages. The only
other ones I think are remotely interesting are dot and cross product.
Yup.
Anythi
aarti_pl Wrote:
> Walter Bright pisze:
> > Don wrote:
> >> There's not many sensible operators anyway. opPow is the only missing
> >> one that's present in many other general-purpose languages. The only
> >> other ones I think are remotely interesting are dot and cross product.
> >
> > Yup.
> >
80 matches
Mail list logo
