Hi,
Someone said very correctly - 'Try to analyze the program logic not the logic of the previous developer'.
This can be done only by good naming convention skills. ya thats true that most of the develpoer are not bothered about it.Â
and there is no any hard and fast rule for naming convention. but Reusabilty is the one of main and most useful feature ofÂ
any programming logic. so each language has their own naming convention for standard compliance.
Â
Many times it happens with a programmer that he stops for a while just to think about the name of a variable, if he finds inÂ
short time its okey otherwise he just ingores it and takes any name thinking that in future he will verify. but at the end
he finds that there are long list of variable whose name are not correct.
Before encountring such problem its better to go through the naming convention before writing code in that lagnguage.
it hardly takes few minutes and save lots of programming time later.
Â
Here are the basic naming convention in ABAP:
|
Class in the class library
|
CL_
|
|
Interfaces in the class library
|
IF_
.
|
|
Local classes in programs
(recommendation)
|
LCL_
|
|
Local interfaces in programs
(recommendation)
|
LIF_
|
|
Method name
|
_
|
|
Events
|
|
|
Local type definitions within a classÂ
(recommendation)
|
TY_
|
|
Data definitions (variables)
|
|
|
Data definitions (constants)
(recommendation)
|
CO_
|
|
IMPORTING parameters
|
IM_
|
|
EXPORTING parameters
|
EX_
|
|
CHANGING parameters
|
CH_
|
|
RESULT
|
RE_
|
|
Attribute access
|
SET_, GET_
|
|
Event handler methods
|
ON_
|
|
Methods that perform type conversions
|
AS_
|
|
Methods that return a Boolean value
|
IS_
|
|
Check methods
|
CHECK_
|
Â
Â
Â
Â
Thanks,
jain.neels@gmail.com
Â
Â