What is strong-typing versus weak-typing? Which is
preferred? Why?
Answers were Sorted based on User's Feedback
Answer / vetri
Strong type is checking the types of variables as soon as
possible, usually at compile time. While weak typing is
delaying checking the types of the system as late as
possible, usually to run-time. Which is preferred depends
on what you want. For scripts & quick stuff you’ll usually
want weak typing, because you want to write as much less
(is this a correct way to use Ensligh?) code as possible.
In big programs, strong typing can reduce errors at compile
time.
Is This Answer Correct ? | 8 Yes | 1 No |
Answer / kirti
Strong typing implies that the types of variables involved in operations are associated to the variable, checked at compile-time, and require explicit conversion; weak typing implies that they are associated to the value, checked at run-time, and are implicitly converted as required. (Which is preferred is a disputable point, but I personally prefer strong typing because I like my errors to be found as soon as possible.)
Is This Answer Correct ? | 0 Yes | 0 No |
How information about the user's locale can be accessed?
1.What r collections? 2.What is .pdb file? 3.Is it possible to provide access to users in master page? 4.What is dirty n Phantom Read(SQL)? 5.What r different isolation levels(SQL)? 6.How to set authentication mode in web.config file?
Why will you usually create an aspnet user account in the database for an asp.net web application?
Difference between ASP & ASP.NET Session State
Give a few examples of page life cycle events.
What is difference between viewstate and session in asp net?
How to make sure that contents of an updatepanel update only when a partial postback takes place (and not on a full postback)?
How to do Caching in ASP?
Explain the overview of asp.net?
How do you perform validations ?
How to handle error while project running on live
What are sql notifications and sql invalidations?