Is there a programming language...
-
I wouldn't get too excited about it though, its really one of the more horrible C# "features". Try the little program out once, then type out a function that has int's as parameters, Intellisense replaces any occurrence of the type with AgeInYears. And while you can define more than one alias for the same type, Intellisense will pick the last defined one to replace in the preview window. Its also a really good way of making code impossible to follow.
Ron Beyer wrote:
Its also a really good way of making code impossible to follow.
No worse than using "var" implicit types, I suspect. ;) Marc
-
...that works "easily" with semantic types? For example, I may have:
int age = 51;which completely loses the concept that 51 is an age (in years). What I want is something like:AgeInYears myAge = 51;and yet still be able to specify that I can perform, say, arithmetic operations on "myAge". For example, in C#, I could write:class AgeInYears
{
public int Value {get;set;}
}... implement operators on AgeInYears
But that gets messy real fast - every "semantic type" needs these operators, etc. Furthermore, the unit of measurement is still not handled very elegantly. So, as the question states, are there programming languages out there that are more expressive of semantic types? Marc
Annoyingly,
intis asealedtype in C#, or all you would have to do is provide the implicit cast operators:class AgeInYears : int
{
public static implicit operator AgeInYears(int i)
{
return (AgeInYears)i;
}
public static implicit operator int(AgeInYears a)
{
return (int)a;
}
}But...what is an age plus an age? It's not really anything useful if you think about it. What you should be thinking of here is an Age plus a Timespan equals a DateTime, but then an Age can't really be assigned an integer value unless it already has a Datetime component - perhaps it is relative to the time at which the Age object is instantiated? And don't forget that an Age is not a constant value: it will vary as the application runs... :laugh:
-
Annoyingly,
intis asealedtype in C#, or all you would have to do is provide the implicit cast operators:class AgeInYears : int
{
public static implicit operator AgeInYears(int i)
{
return (AgeInYears)i;
}
public static implicit operator int(AgeInYears a)
{
return (int)a;
}
}But...what is an age plus an age? It's not really anything useful if you think about it. What you should be thinking of here is an Age plus a Timespan equals a DateTime, but then an Age can't really be assigned an integer value unless it already has a Datetime component - perhaps it is relative to the time at which the Age object is instantiated? And don't forget that an Age is not a constant value: it will vary as the application runs... :laugh:
OriginalGriff wrote:
Annoyingly,
intis asealedtype in C#, or all you would have to do is provide the implicit cast operators:Exactly!
OriginalGriff wrote:
And don't forget that an Age is not a constant value: it will vary as the application runs...
I know. :) It was a contrived example.
OriginalGriff wrote:
But...what is an age plus an age?
Yeah, this stuff gets one to really think about the meaning of things. :) Marc
-
I wouldn't get too excited about it though, its really one of the more horrible C# "features". Try the little program out once, then type out a function that has int's as parameters, Intellisense replaces any occurrence of the type with AgeInYears. And while you can define more than one alias for the same type, Intellisense will pick the last defined one to replace in the preview window. Its also a really good way of making code impossible to follow.
That's a problem with Intellisense then, not the language. Defining aliases is the one best use for the
usingdirective, but I limit it to complex types like Dictionary-of-Dictionary-of-List kinds of things. Or, you can make a more general alias for a particular type, likeusing Connection=System.Data.SqlClient.SqlConnection. -
...that works "easily" with semantic types? For example, I may have:
int age = 51;which completely loses the concept that 51 is an age (in years). What I want is something like:AgeInYears myAge = 51;and yet still be able to specify that I can perform, say, arithmetic operations on "myAge". For example, in C#, I could write:class AgeInYears
{
public int Value {get;set;}
}... implement operators on AgeInYears
But that gets messy real fast - every "semantic type" needs these operators, etc. Furthermore, the unit of measurement is still not handled very elegantly. So, as the question states, are there programming languages out there that are more expressive of semantic types? Marc
A long time ago, at a defense contractor far, far defunct... The Ada programming language provided a semblance of semantic typing. You could create an 'Age' type that was a subtype of integer. I'm sure the computer scientists would scoff at Ada's limitations, but it does somewhat fit the bill. I don't know the modern language definition (I used it back in the 80's), so it might be more capable now.
Software Zen:
delete this; -
Ron Beyer wrote:
Its also a really good way of making code impossible to follow.
No worse than using "var" implicit types, I suspect. ;) Marc
varhas its place. Too many programmers let it escape that place, unfortunately.Software Zen:
delete this; -
Annoyingly,
intis asealedtype in C#, or all you would have to do is provide the implicit cast operators:class AgeInYears : int
{
public static implicit operator AgeInYears(int i)
{
return (AgeInYears)i;
}
public static implicit operator int(AgeInYears a)
{
return (int)a;
}
}But...what is an age plus an age? It's not really anything useful if you think about it. What you should be thinking of here is an Age plus a Timespan equals a DateTime, but then an Age can't really be assigned an integer value unless it already has a Datetime component - perhaps it is relative to the time at which the Age object is instantiated? And don't forget that an Age is not a constant value: it will vary as the application runs... :laugh:
You could argue that
AgeInYearsshould be implemented something like this:class AgeInYears
{
public AgeInYears(DateTime birthdate)
{
_Birthdate = birthdate;
}
private DateTime _Birthdate;
public int Years
{
get
{
return (DataTime.Now - _Birthdate).Days / 365; // yes, I know 365 isn't right; it's just an example, for gosh sakes
}
}
}Software Zen:
delete this; -
You could argue that
AgeInYearsshould be implemented something like this:class AgeInYears
{
public AgeInYears(DateTime birthdate)
{
_Birthdate = birthdate;
}
private DateTime _Birthdate;
public int Years
{
get
{
return (DataTime.Now - _Birthdate).Days / 365; // yes, I know 365 isn't right; it's just an example, for gosh sakes
}
}
}Software Zen:
delete this;*cough* :-O I did... Working with Age: it's not the same as a TimeSpan![^]
-
*cough* :-O I did... Working with Age: it's not the same as a TimeSpan![^]
Yeah, this reeked of prior art but I couldn't be arsed to go looking just to comment on a casual question. :-D
Software Zen:
delete this; -
...that works "easily" with semantic types? For example, I may have:
int age = 51;which completely loses the concept that 51 is an age (in years). What I want is something like:AgeInYears myAge = 51;and yet still be able to specify that I can perform, say, arithmetic operations on "myAge". For example, in C#, I could write:class AgeInYears
{
public int Value {get;set;}
}... implement operators on AgeInYears
But that gets messy real fast - every "semantic type" needs these operators, etc. Furthermore, the unit of measurement is still not handled very elegantly. So, as the question states, are there programming languages out there that are more expressive of semantic types? Marc
Well This c++ 11 trick is very powerfull, really! I prefer to do all the hard work from scratch (ok, have R #). I believe that this threshold "semantic" is outside the domain of a programming language (commonly, it is a "system domain" concept), because it is difficult to predict the particularities of a user-defined (conversion, comparison, integrity, serialization, etc.).
-
I wouldn't get too excited about it though, its really one of the more horrible C# "features". Try the little program out once, then type out a function that has int's as parameters, Intellisense replaces any occurrence of the type with AgeInYears. And while you can define more than one alias for the same type, Intellisense will pick the last defined one to replace in the preview window. Its also a really good way of making code impossible to follow.
Hi Ron, fyi: Visual Studio 2013 IntelliSense does not suggest, or replace, an int Type with an alias defined in a Using statement.
If you seek to aid everyone that suffers in the galaxy, you will only weaken yourself … and weaken them. It is the internal struggles, when fought and won on their own, that yield the strongest rewards… If you care for others, then dispense with pity and sacrifice and recognize the value in letting them fight their own battles." Darth Traya
-
I wouldn't get too excited about it though, its really one of the more horrible C# "features". Try the little program out once, then type out a function that has int's as parameters, Intellisense replaces any occurrence of the type with AgeInYears. And while you can define more than one alias for the same type, Intellisense will pick the last defined one to replace in the preview window. Its also a really good way of making code impossible to follow.
Upvoted ! Before I read your response, I had opened VS 2013, and typed: using AgeInYears = System.Int32; Any time my mind works like yours, I feel better :) bill
If you seek to aid everyone that suffers in the galaxy, you will only weaken yourself … and weaken them. It is the internal struggles, when fought and won on their own, that yield the strongest rewards… If you care for others, then dispense with pity and sacrifice and recognize the value in letting them fight their own battles." Darth Traya
-
Upvoted ! Before I read your response, I had opened VS 2013, and typed: using AgeInYears = System.Int32; Any time my mind works like yours, I feel better :) bill
If you seek to aid everyone that suffers in the galaxy, you will only weaken yourself … and weaken them. It is the internal struggles, when fought and won on their own, that yield the strongest rewards… If you care for others, then dispense with pity and sacrifice and recognize the value in letting them fight their own battles." Darth Traya
-
Hi Ron, fyi: Visual Studio 2013 IntelliSense does not suggest, or replace, an int Type with an alias defined in a Using statement.
If you seek to aid everyone that suffers in the galaxy, you will only weaken yourself … and weaken them. It is the internal struggles, when fought and won on their own, that yield the strongest rewards… If you care for others, then dispense with pity and sacrifice and recognize the value in letting them fight their own battles." Darth Traya
-
Phil Martin wrote:
Units are lost at runtime
Which is unfortunate because I'd possibly like to be able to reflect on the unit of measure. But it's an interesting avenue to explore. Thanks! Marc
Yeah, it is unfortunate. In the engineering applications I write, I've created a ScalaryQuantity and a VectorQuantity class. They are just the usual numeric structures which support all the normal arithmetic, but supports keeping track of units, and converting units when necessary. There's a big run time overhead involved, but for me it is worth it because it has helped me catch many errors far earlier in the process of developing new calculations.
-
A long time ago, at a defense contractor far, far defunct... The Ada programming language provided a semblance of semantic typing. You could create an 'Age' type that was a subtype of integer. I'm sure the computer scientists would scoff at Ada's limitations, but it does somewhat fit the bill. I don't know the modern language definition (I used it back in the 80's), so it might be more capable now.
Software Zen:
delete this;Gary Wheeler wrote:
The Ada programming language provided a semblance of semantic typing.
Ah, it does indeed. I've been reading the Ada type stuff - very slick. It's a pity these constructs aren't in other languages. I wonder why not - it seems like it would really help bullet proof code. Then again, like anything else, I bet it can be horribly abused as well. Marc
-
...that works "easily" with semantic types? For example, I may have:
int age = 51;which completely loses the concept that 51 is an age (in years). What I want is something like:AgeInYears myAge = 51;and yet still be able to specify that I can perform, say, arithmetic operations on "myAge". For example, in C#, I could write:class AgeInYears
{
public int Value {get;set;}
}... implement operators on AgeInYears
But that gets messy real fast - every "semantic type" needs these operators, etc. Furthermore, the unit of measurement is still not handled very elegantly. So, as the question states, are there programming languages out there that are more expressive of semantic types? Marc
"which completely loses the concept that 51 is an age (in years)." so write int ageInYears = 51; There are many ways to do it in c# (pass the int value in constructor, make an implicit cast operator, ...), but imho the best way is sticking with plain int, as that what "age in years" exactly is.
-
My mind doesn't work. So I would use Python. :zzz:
-
varhas its place. Too many programmers let it escape that place, unfortunately.Software Zen:
delete this; -
I hate myself for typing this:
namespace TestApp1
{
using AgeInYears = System.Int32;class Program { static void Main(string\[\] args) { AgeInYears myAge = 10; AgeInYears oldAge = 50; AgeInYears timeUntilOldAge = oldAge - myAge; } }}
Yes, that's perfectly legal C# code. Its technically an int, works the same way that #define does in c++ to replace types. It only works in single code files though.
It fails totally though for type safety.
using AgeInYears = System.Int32;
using AgeInDays = System.Int32;...
AgeInYears yearAge = 10;
AgeInDays dayAge = 3650;var myAge = yearAge + dayAge; // OOPS!
(A better example may involve standard units of measure: inches, miles, meters, temperatures, etc.) The system should at least prevent naive attempts to assign to incorrect types. Ideally, the system should be able to perform conversions where possible. Smalltalk and C++ both offer enough flexibility. In C#, a struct could be declared, but I think you'd struggle to make it semantically sound.
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
