I believe the 'as' keyword would be more smooth:
def hello(name as String) as String:
var greeting as String
greeting = 'Hello '+name
return greeting Function hello(ByVal name As String) As String
Dim greeting As String
greeting = "Hello" + name
Return greeting
End Function def hello(String name) as String:
String greeting
greeting = 'Hello '+name
return greeting
greeting as String
greeting :: String
A good example of this case would be Java (like it or not):
String Hello(String name) {
String greeting;
greeting = "hello " + name;
return greeting;
}
Using a keyword to introduce entity definitions (variables, functions, packages, etc.) gives the language more space to grow in syntax without worrying about such ambiguities later. You can construct a grammar without any ambiguities that does not use such keywords - such as with your example of Java - but you're going to have to keep this pitfall in mind anytime you change the grammar.
It's possible to debate the positive side too, but I do agree that constructing a language with a verboser non-semantic grammar is easier.
LISTEN TO ME VERY CAREFULLY hello
I NEED YOUR CLOTHES YOUR BOOTS AND YOUR MOTORCYCLE name
GET TO THE CHOPPER greeting
. . .
ENOUGH TALK
GIVE THESE PEOPLE AIR
I'LL BE BACK greeting
HASTA LA VISTA, BABY
Of course, the comparison may not be very illuminating given that all ArnoldC variables are Int16s.
You are as brave as the sum of a fat little stuffed misused dusty old rotten codpiece and a beautiful fair warm peaceful sunny summer's day
def hello(name : String) -> io String:
def hello(name : string) : io String