Re: Fwd: Are there any rules to follow when naming pointer variables?

It doesn't matter what you name your variables.  Remember: The names don't exist when the program is running, they are just "source code".

One of the dangers of using pointers is that its easy to have a coding error that "seems" to work, but its not actually behaving correctly.  For example, it might be referring to memory that you don't have the right to use, and that may seem to be fine because it happens to be unused memory, but then later when you don't expect it, something fails.

Its hard to tell if something like that might be happening here when you haven't provided any code showing what you've done.

It is very important when working with pointers that you understand quite clearly how the pointer works, how it is set, how it is used, etc.  If its not clear in your head, you are prone to having problems you don't expect.   If you aren't 100% clear on how all of this is working, I would strongly recommend using an alternative to pointers.



On 3/21/19 5:39 PM, Mohammad Tanveer wrote:

Ran into some strange issue when naming *Pointer variables. V7R2

Program A SQL RPGLE calling Program B service program with parameters. One
of the parameter is Pointer.

If we name a pointer parameter variable in Program A --> vMyPointer we get
unexpected data in service program B or MCH exceptions for memory.

If we change the same variable to pMyPointer or svMyPointer everything
works fine.