C#

Pete O`Hanlon wrote:

It seems that he wants to redefine how mathematics works.

double d = 9.5;<br />
      d = Math.Floor(d) + ((Math.Floor(d) + 1) - d) / 10;<br />

jgasm wrote:

I simply want to count
how many decimals are in the string, unfortunately everything in regex seems to involve
replacing the decimals...and regex seems really heavy way of doing something that should
be simple.

Int32 decimalCount = text.Split('.')[1].Length

Int32 decimalCount = text.IndexOf('.') > -1 ? text.Split('.')[1].Length : 0;

[System.STAThreadAttribute]
static void Main(string[] args)
{
    int d ;
 
    args [ 0 ] = args [ 0 ].Trim( new char[] { '0' } ) ;
    d = args [ 0 ].IndexOf ( '.' ) ;
 
    if ( d >= 0 )
    {
        d = args [ 0 ].Length - d - 1 ;
    }
    else
    {
        d = 0 ;
    }
 
    System.Console.WriteLine ( d ) ;
}

int d ;

args [ 0 ] = args [ 0 ].Trim( new char[] { '0' } ) ;

System.Console.WriteLine
(
    ( d = args [ 0 ].IndexOf ( '.' ) ) == -1 ? 0 : args [ 0 ].Length - d - 1
) ;

int pos = text.IndexOf('.');
int decimalCount;
if (pos == -1) {
   decimalCount = 0;
} else {
   decimalCount = value.Length - pos - 1;
}

int pos = text.IndexOf('.');
int decimalCount = (pos == -1) ? 0 : value.Length - pos - 1;

fuziononline wrote:

Before going throught the hassle of creating ours from cradle to grave I was hoping to see what others have already created?

fuziononline wrote:

I work in a application design department that designs in c#

1. Define the business requirements (high level, business-oriented requirements). This is what the software needs to do, problems it needs to solve, etc. in order for it to be competitive in the market.
   
2. Define the technical requirements for each business requirement. The technical requirements define how the business requirement will be met by the software. Each business requirement can map to one or more technical requirement, but generally one technical requirement should map to one business requirement. This also should cover any integration points to other systems that might be needed.
   
3. (Optional)Define a lower-level set of technical requirements that map to a single higher-level technical requirements. Again, one high-level technical requirement could have multiple lower-level technical requirements.