Yeah, I kind of forgot about interface - they are very nice too. Overloading would be awesome.
Generics, well, generics are very cool. However, they are probably the most difficult things to implement, and they are mainly used to make collections specific.
I think generics would take too much effort on mark's part. Constructors with parameters, private, protected, overloading, interfaces should take a week or so. Perhaps I am optimistic - I don't know how much time mark has in a week, what his usuall per day hourage is.
The only language I've ever messed around with the insides had one of the best structures possible. You could even swap out certain sections of code and get it to compile other languages.
I'd be glad if you could just implement privates, mark
I'd be very glad, maybe exstatic if you could implement all the other stuff as well.
Flameduck:
Consider these two examples, which looks better? Properties are all about syntax sweetness.
a.Speed += 1
a.SetSpeed(a.GetSpeed() + 1)
Generics, well, generics are very cool. However, they are probably the most difficult things to implement, and they are mainly used to make collections specific.
I think generics would take too much effort on mark's part. Constructors with parameters, private, protected, overloading, interfaces should take a week or so. Perhaps I am optimistic - I don't know how much time mark has in a week, what his usuall per day hourage is.
The only language I've ever messed around with the insides had one of the best structures possible. You could even swap out certain sections of code and get it to compile other languages.
I'd be glad if you could just implement privates, mark
I'd be very glad, maybe exstatic if you could implement all the other stuff as well.
Flameduck:
Consider these two examples, which looks better? Properties are all about syntax sweetness.
a.Speed += 1
a.SetSpeed(a.GetSpeed() + 1)