4 ms·

>I don't know of any programming language that will auto-correct typos for you. I know of many compilers that will point them out to you, and IDEs that will of

by batista 14y ago

>I don't know of any programming language that will auto-correct typos for you. I know of many compilers that will point them out to you, and IDEs that will offer to auto-correct them (Eclipse, XCode and Visual Studio for example). >If you don't write spaghetti code, you won't have a problem Yes. And if you don't make any memory allocation errors you don't need a GC. Hell, if you don't make any errors period, you can just program in hex, building the executable code directly and skip assembly. The thing is, different languages have different inherent characteristics (syntax, features) and different cultures (pertaining to libs, common practices, frameworks, etc), so one can tend to create more spaghetti code than the other, the programmer being equal.

stephenr 14y ago
>I know of many compilers that will point them out to you, and IDEs that will offer to auto-correct them PHP's lint option will identify syntax errors, and an IDE can identify or auto-correct typos in any language - it's not a Go specific thing. >And if you don't make any memory allocation errors you don't need a GC. Memory allocation is a feature. Spaghetti code is a symptom of a poor developer/team. They are not comparable. > Hell, if you don't make any errors period spaghetti code is not a "mistake" like a typo, missing function reference etc.
lobo_tuerto 14y ago
"The thing is, different languages have different inherent characteristics (syntax, features) and different cultures (pertaining to libs, common practices, frameworks, etc), so one can tend to create more spaghetti code than the other, the programmer being equal." That's simply not true. If you are organized, you will use whatever structures the language you are using provides to you (classes, modules, namespaces, etc.) to NOT write spaguetti code. Spaguetti code it's not inherent to the language, it's inherent to the programmer.

by batista 14y ago

stephenr 14y ago

>I know of many compilers that will point them out to you, and IDEs that will offer to auto-correct them PHP's lint option will identify syntax errors, and an IDE can identify or auto-correct typos in any language - it's not a Go specific thing. >And if you don't make any memory allocation errors you don't need a GC. Memory allocation is a feature. Spaghetti code is a symptom of a poor developer/team. They are not comparable. > Hell, if you don't make any errors period spaghetti code is not a "mistake" like a typo, missing function reference etc.

lobo_tuerto 14y ago

"The thing is, different languages have different inherent characteristics (syntax, features) and different cultures (pertaining to libs, common practices, frameworks, etc), so one can tend to create more spaghetti code than the other, the programmer being equal." That's simply not true. If you are organized, you will use whatever structures the language you are using provides to you (classes, modules, namespaces, etc.) to NOT write spaguetti code. Spaguetti code it's not inherent to the language, it's inherent to the programmer.