Possible Duplicate:
what is the difference between match_parent and fill_parent property in android
FILL_PARENT and MATCH_PARENT
I have go through android developer site where they give following difference :
Note: Beginning with Android 2.2 (API level 8), “fill_parent” has been renamed “match_parent” to better reflect the behavior. The reason is that if you set a view to “fill_parent” it does not expand to fill the remaining space after sibling views are considered, but instead expands to match the size of the parent view no matter what—it will overlap any sibling views.
But anyone explain with example.so that things may clear.
They’re the same thing (in API Level 8+). Use match_parent.
fill_parent(renamedMATCH_PARENTin API Level 8 and higher), which means that the view wants to be as big as its parent (minus padding)fill_parent: The view should be as big as its parent (minus padding). This constant is deprecated starting from API Level 8 and is replaced bymatch_parentFor Android API 1.6 to 2.1
match_parentwill throw you an error, so use fill_parent in these cases. To support backward compatibility, it’s better to usefill_parentI remember that Roman Guy (Android Developer at Google) said, that they have changed the name because
"fill_parent"was confusing for developers. As matter of the fact,"fill_parent"does not fill the remaining space (for that you use the weight attribute) but it takes as much space as its layout parent. That’s why the new name is"match_parent"