![]() ![]() And a type-strict language doesn’t let you pass a number when a string is needed, and that’s GOOD because sometimes you make a mistake and then the compiler won’t compile your code. After you program for awhile, who start learning you make a lot more mistakes than you think you do. It promotes discipline by catching errors in your codes whereas a type-tolerant language doesn’t. ![]() However: having a type-strict language becomes it’s own advantage. Although remember this sort of thing slows down a program, it still makes things easier. As languages like PERL prove, such information is not intrinsically important to the programmer, that is if you have functions that accept ANYTHING and do the conversions within themselves. Many programs - think PERL - are designed to do away with as much pre-knowledge as possible and just allow you to write code without remember supplementary details like “what type is this variable”?Īll “types” are is a little piece of information that travels with a variable that dictates how it should be used. ![]() VB and REAL/Xojo are RAD tools so why not make it easier?īut, as you program longer, you start understanding what “types” are and how they help you in programming. I know where you are coming from, I used VB for a long time and enjoying the “type coercion” where you could pass a number and it would be converted into a string automatically. This seems a larger irritant - just my opinion. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |