*Error* def : function is write protected and cannot be rede

R

RC MURALI

Guest
Hi,

I am getting the following message in icfb CIW, if I try to reload any
of my skill utilites.

*Error* def : function is write protected and cannot be redefined

How to get rid of this?

Thanks & Regards,
Murali RC
 
RC MURALI wrote, on 01/18/10 10:11:
Hi,

I am getting the following message in icfb CIW, if I try to reload any
of my skill utilites.

*Error* def : function is write protected and cannot be redefined

How to get rid of this?

Thanks & Regards,
Murali RC
Click to expand...
I'm guessing you have:

sstatus(writeProtect t)

in your .cdsinit or in your code somewhere. If you don't add this, then
functions will not be write protected.

Note that write protection is stored on the function at the time it is created -
so it's no good to just enter:

sstatus(writeProtect nil)

after the function is defined - it honours whatever status it was at definition
time.

You can also switch to debug mode, and then write protected functions can be
overwritten:

sstatus(debugMode t)

Regards,

Andrew.
 
On Jan 18, 7:06 pm, Andrew Beckett <andr...@DcEaLdEeTnEcTe.HcIoSm>
wrote:
RC MURALI wrote, on 01/18/10 10:11:

Hi,

I am getting the following message in icfb CIW, if I try to reload any
of my skill utilites.

*Error* def : function is write protected and cannot be redefined

How to get rid of this?

Thanks & Regards,
Murali RC

I'm guessing you have:

sstatus(writeProtect t)

in your .cdsinit or in your code somewhere. If you don't add this, then
functions will not be write protected.

Note that write protection is stored on the function at the time it is created -
so it's no good to just enter:

sstatus(writeProtect nil)

after the function is defined - it honours whatever status it was at definition
time.

You can also switch to debug mode, and then write protected functions can be
overwritten:

sstatus(debugMode t)

Regards,

Andrew.
Click to expand...

Thanks Andrew. It worked.

Where can I find the name of the different Internal System Variables?

Say in this case, we have used "debugMode" "writeProtect".
 
RC MURALI wrote, on 01/19/10 04:50:
Thanks Andrew. It worked.

Where can I find the name of the different Internal System Variables?

Say in this case, we have used "debugMode" "writeProtect".
Click to expand...
Open the documentation (cdnshelp in IC61X, and cdsdoc in IC5141) and search for
"sstatus". Or search for writeProtect.

Or look in <ICinstDir>/doc/sklangref/sklangref.pdf or
<ICinstDir>/doc/sklanguser/sklanguser.pdf (the same manuals that the search
above will use).

Did you try looking in the documentation?

Regards,

Andrew.
 
On Jan 19, 5:44 pm, Andrew Beckett <andr...@DcEaLdEeTnEcTe.HcIoSm>
wrote:
RC MURALI wrote, on 01/19/10 04:50:



Thanks Andrew. It worked.

Where can I find the name of the different Internal System Variables?

Say in this case, we have used "debugMode" "writeProtect".

Open the documentation (cdnshelp in IC61X, and cdsdoc in IC5141) and search for
"sstatus". Or search for writeProtect.

Or look in <ICinstDir>/doc/sklangref/sklangref.pdf or
ICinstDir>/doc/sklanguser/sklanguser.pdf (the same manuals that the search
above will use).

Did you try looking in the documentation?

Regards,

Andrew.
Click to expand...
Thanks. I got it.
 
You must log in or register to reply here.

Welcome to EDABoard.com

Sponsor

Back
Top