I am trying to figure out how to make a paging script and the section of code below is from a code that i am learning it from now when i put this code in my test page it gives me the following error.Notice: Undefined index: start in C:\wamp\www\firstpage.php on line 3

and i do not understand why i am getting his error and i do not understand how to fix it any help would be appreciated.

~~~this is the actual code snippet~~~

PHP Code:

 <?php
$pagesize = 10;
$start = (int)$_GET['start'];
$start = (isset($_GET['start'])) ? $start : 0;
?>

Do you have strict error reporting on? The code you wrote should work even though you get the notice. This should accomplish the same thing without the notice:

PHP Code:

<?php
$pagesize = 10;
$start = (isset($_GET['start'])) ? $_GET['start'] : 0;
?>

This will not cause a notice because if $_GET['start'] is not set, you never try to access it.

my error reporting is on E_ALL and the code does work i just get that notice warning, is that warning something i can suppress with the @ symbol or is it something i need to fix?

The default is E_ALL & ~E_NOTICE (everything except notices). Suppressing the line would work, but ideally you don't want to suppress lines unless you have to. Personally, I don't like throwing error messages away. You may want to look into custom error handlers so you can choose how to deal with error messages. This allows you to track the errors your users get without giving them the error message.

Matt's right. I admit to being lazy. Notices shouldn't be on (in my never humble opinion) on a live server. However, best practices being followed means it won't matter and that's what Matt is suggesting. PHP let's you do a lot without requiring academic-level formality, but with notices on, you are expected to be more rigorous. If I were you, I'd use Matt's code with 1 modification I'm sure he just overlooked:

PHP Code:

<?php 
$pagesize = 10; 
$start = (isset($_GET['start'])) ? (int)$_GET['start'] : 0; 
?>

Then, everywhere else in your code, you'll want to be very careful about ensuring that you're abiding by all the best practices (no, I don't have a list ).

Lazy 'ole me just turns off notices.

Sorry that i do not understand guys but are you saying that notices are unimportant and that is why i should turn them off?

I am still fairly new at php and i do not want to get into a position where i am writing bad code,

but if notices are just minor things that do not ever effect a php script then i will turn the notices off because i am always getting notices like that.

Notices will typically inform you of problems with your method. Most of the time they don't indicate that your script isn't working as intended. If you're not working on a live site, leaving them on couldn't hurt. A lot of things PHP generate notices for would cause an error in a more strict language. In addition to that I assume a script with no notices would be more effecient than an equivalent one with them.

Ok thanks alot guys.