kai_itz me's Profile
Reputation: 18 Tradesman
- Active Members
- Active Posts:
- 138 (0.48 per day)
- 03-August 12
- Profile Views:
- Last Active:
- May 16 2013 10:03 PM
- Who Cares
- OS Preference:
- Favorite Browser:
- Favorite Processor:
- Favorite Gaming Platform:
- Your Car:
- Who Cares
- Dream Kudos:
Posts I've Made
Posted 16 May 2013Firstly it does not seems to be vb.net.
i think(not sure) this line can be used as specifying any condition e.g validating text boxes etc.
Have a look at this
Posted 14 May 2013
Posted 14 May 2013Can you please tell us about the error you are getting ?
Posted 14 May 2013
Dim years As Integer Dim rain As Integer = 0 Dim average As Integer = 0 Dim total As Integer = 0 Console.WriteLine("Please enter the number of years.") years = Console.ReadLine() Do Until years = 0 For months As Integer = 0 To 11 Step 0 If months <= 11 Then Console.WriteLine("Please enter amount in inches.") months = months + 1 rain = Console.ReadLine() total = total + rain average = total / months End If Console.WriteLine("Total Rainfall " & total & " average " & average & " months " & months & "") Console.ReadLine() Next years = years - 1 Console.WriteLine("now year is " & years & "") Loop
for the calculation purpose (as your amount may vary) you have to enter amount every time...
Posted 18 Apr 2013i got it from somewhere
The difference between compile time and run time is an example of what pointy-headed theorists call the phase distinction. It is one of the hardest concepts to learn, especially for people without much background in programming languages. To approach this problem, I find it helpful to ask
What invariants does the program satisfy?
What can go wrong in this phase?
If the phase succeeds, what are the postconditions (what do we know)?
What are the inputs and outputs, if any?
1.The program need not satisfy any invariants. In fact, it needn't be a well-formed program at all. You could feed this HTML to the compiler and watch it barf...
2.What can go wrong at compile time:
(Rarely) compiler crashes
3.If the compiler succeeds, what do we know?
The program was well formed---a meaningful program in whatever language.
It's possible to start running the program. (The program might fail immediately, but at least we can try.)
4.What are the inputs and outputs?
Input was the program being compiled, plus any header files, interfaces, libraries, or other voodoo that it needed to import in order to get compiled.
Output is hopefully assembly code or relocatable object code or even an executable program. Of if something goes wrong, output is a bunch of error messages.
1.We know nothing about the program's invariants---they are whatever the programmer put in. Run-time invariants are rarely enforced by the compiler alone; it needs help from the programmer.
2.What can go wrong are run-time errors:
Division by zero
Deferencing a null pointer
Running out of memory
Also there can be errors that are detected by the program itself
Trying to open a file that isn't there
Trying find a web page and discovering that an alleged URL is not well formed
3.If run-time succeeds, the program finishes (or keeps going) without crashing.
4.Inputs and outputs are entirely up to the programmer. Files, windows on the screen, network packets, jobs sent to the printer, you name it. If the program launches missiles, that's an output, and it happens only at run time :-)
- Member Title:
- D.I.C Head
- Age Unknown
- Birthday Unknown
- Full Name:
- kai ryan
- Programming Languages:
- vb.net & sql novice , java , c++