The Insider News

Marc Clifton wrote:

A null int would be expressed as an empty array [] whereas an int with a value would be expressed as a single item array [42]

selectItems(propertyName, arrayOfItems, propertyValue){
// #### Get the object(s) 
// #### from the arrayOfItems
// #### where value of propertyName is equal to the propertyValue
// #### Returns an array of 0 or more items
var outItems = [];
for (var x = 0; x < arrayOfItems.length; x++){
//console.log("arrayOfItems[x][idPropertyName] : " + arrayOfItems[x][idPropertyName]);
	   if (propertyValue === undefined){
                // this is a cheat to allow me to get a subset of all the objects when I don't 
                // care what the propertyValue is.    If you call the method with no 3rd param
                // it will run this code
		outItems.push(arrayOfItems[x]);
   	   }
   	   if (arrayOfItems[x][propertyName] === propertyValue){
		//console.log(arrayOfItems[x][propertyName]);
		outItems.push(arrayOfItems[x]);
	   }
	}
	return outItems;
}

BillWoodruff wrote:

figured out today how to make my generic hierarchy utility library more orthogonal by having all methods return an IEnumerable<TNode>

raddevus wrote:

Anyways, the cool thing is that I thought it seemed most elegant to always return an array also.

Quote:

It took thousands of years to accept the concept of zero, and even longer for the Vatican because of the moral implications of nothingness.

Marc Clifton wrote:

In contrast, the idea of "nullable" arrived rather quickly after the invention of computers and I databases in particular (I haven't researched it, so I'm just guessing.)

BillWoodruff wrote:

Extremely misleading generalities.

public bool DoesCommunityHaveElephantingSunshines()
{
    return true;
}