#variable assignment

How do we know who "he" is? And how does "he" differ from "himself" when we interpret it? In this week's episode, we talk about the syntax and semantics of pronouns: how we can place them in sentences, how they link up to variables, and the role of context in how we interpret them.

New Post has been published on http://www.varindersandhu.in/2012/05/04/sql-server-2008-inline-variable-assignment-declare-and-assign-variable/

SQL SERVER – 2008 – Inline Variable Assignment – Declare and Assign Variable

Inline variable assignment is available in SQL Server 2008 or higher version. Beside this is very simple but very useful feature. Many of the programming languages have this feature. But now SQL Server 2008 or higher version has this feature.

<!-- google_ad_client = "pub-2404605494811633"; google_alternate_color = "FFFFFF"; google_ad_width = 468; google_ad_height = 60; google_ad_format = "468x60_as"; google_ad_type = "text_image"; google_ad_channel =""; google_color_border = "FFFFFF"; google_color_link = "0000FF"; google_color_bg = "FFFFFF"; google_color_text = "000000"; google_color_url = "008000"; google_ui_features = "rc:6"; //-->

Example:

---- SQL Server 2005 or earlier versions DECLARE @var1 INT SET @var1 = 100 SELECT @var1 AS myVar GO

---- SQL Server 2008 or Higher Version (Inline Variable Assignment) DECLARE @var1 INT = 100 SELECT @var1 AS myVar GO

Today we learned about code smell, some finer details on ruby's objects and variable assignment, and default hash value assignment. My partner and I worked on a couple of games today (Mastermind and hangman), and definitely used this knowledge for coding and debugging.

code smells some of the ones that were highlighted in today's lecture were duplicate code, long methods, speculative generality (coding for potential future needs rather than focusing on the current requirements of a project), and god objects (classes that know too much about other classes).

immutable vs mutable objects -- some object types are immutable (fixnums and symbols), meaning they cannot be changed. Others (e.g. strings and arrays) can be changed by certain methods so you must be careful not to haphazardly change things out from under your variables.

assignment vs mutation -- when variables are assigned a value, this means that they point at an object id. When the variable is later referenced, ruby retrieves the object whose id the variable points to. When some methods are called upon a variable, they create a new object_id and reassign the variable to this. Since fixnums and symbols are immutable, all of their methods will create new object ids. However, other methods may actually mutate the object that the variable points to and could cause unintended consequences. Here's an example:

a = 'small' b = a puts a # => 'small' puts b # => 'small' a[2] = 'e' # mutates the string (which a and b both point to) puts a # => 'smell' puts b # => 'smell' a += 'y cat' #reassigns a (a = a + 'y cat') puts a # => 'smelly cat' puts b # => 'smell'

default hash values -- if your default hash value is an immutable type, pass the value as an argument. If your default value is mutable, you must pass it in as a block. This will create a new object each time a new key is called rather than the same object. For instance: