Click here to Skip to main content
13,705,290 members
Rate this:
 
Please Sign up or sign in to vote.
See more:
import java.util.*;
class Product
{
     String name;
	 float price;
	 int qty;
	 float bill,disc,nbill;
}
class Rect
{
	public static void main(String[] args) 
	{
		Scanner sc=new Scanner(System.in);
		Product p=new Product();
	
		System.out.print("product name: ");
		String name=sc.nextLine();
		System.out.print("price:");
		float price=sc.nextFloat();
		System.out.print("quantity");
		int qty=sc.nextInt();
       
         p.bill=p.price*p.qty;
		p.disc=p.bill*5/100;
		p.nbill=p.bill-p.disc;
		
		System.out.println("Product name : "+p.name+"Price : "+p.price+"Quantity : "+p.qty+"Bill : "+p.bill+"Discount : "+p.disc+"Net bill : "+p.nbill);
		}
}


What I have tried:

it prints null instead of string name and zeros instead of values
Posted 11-Jul-18 6:37am
Updated 11-Jul-18 8:16am

1 solution

Rate this: bad
 
good
Please Sign up or sign in to vote.

Solution 1

Quote:
it prints null instead of string name and zeros instead of values

reread your code, and pay attention to the variables where you store the values against what you print. There is a surprise.

Your code do not behave the way you expect, and you don't understand why !

There is an almost universal solution: Run your code on debugger step by step, inspect variables.
The debugger is here to show you what your code is doing and your task is to compare with what it should do.
There is no magic in the debugger, it don't know what your is supposed to do, it don't find bugs, it just help you to by showing you what is going on. When the code don't do what is expected, you are close to a bug.
To see what your code is doing: Just set a breakpoint and see your code performing, the debugger allow you to execute lines 1 by 1 and to inspect variables as it execute.

The downside of this solution:
- It is a DIY, you are the one tracking the problem and finding its roots, which lead to the solution.
The upside of this solution:
- It is also a great learning tool because it show you reality and you can see which expectation match reality.

secondary effects
- Your will be proud of finding bugs yourself.
- Your learning skills will improve.

You should find pretty quickly what is wrong.

Debugger - Wikipedia, the free encyclopedia[^]
http://docs.oracle.com/javase/7/docs/technotes/tools/windows/jdb.html[^]
https://www.jetbrains.com/idea/help/debugging-your-first-java-application.html[^]
The debugger is here to only show you what your code is doing and your task is to compare with what it should do.
  Permalink  

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS
Top Experts
Last 24hrsThis month


Advertise | Privacy | Cookies | Terms of Service
Web05-2016 | 2.8.180920.1 | Last Updated 11 Jul 2018
Copyright © CodeProject, 1999-2018
All Rights Reserved.
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100