Supressing warnings & errors in CSIDE

In OScript I often do something like this:

// GetScript() returns a ScriptScript s = $MyModule.Utils.GetScript()// Execute itAssoc results = s()

This compiles and works fine. However, I get an error if I simplify the line to the following:

Assoc results = $MyModule.Utils.GetScript()()

It still compiles and runs, but CSIDE places a red error marker next to the line with the text funcReturnTypes is empty. Is there a way to surpress these error messages?

Another pattern I often use is something like this:

if IsDefined( value=$MyModule.Utils.GetValue() )    // do something with value, which is definedend

This results in a Assignment expression found in another expression. Did you mean == instead? warning. Same question: Is there a way to supress this?

Find more posts tagged with

Comments

eLink User

Just a thought does replacing the$ with the new syntax one with two colons have any effect

My package::my global::myscript thingy?

Ciao, Appu

On Oct 4, 2016, at 10:53 AM, eLink Entry: Content Server Development Forum <development@elinkkc.opentext.com> wrote:

eLink : Supressing warnings & errors in CSIDE
Supressing warnings & errors in CSIDE Posted byMeyer, ChrisOn 10/04/2016 11:50 AM

In OScript I often do something like this:// GetScript() returns a ScriptScript s = $MyModule.Utils.GetScript()// Execute itAssoc results = s()
This compiles and works fine. However, I get an error if I simplify the line to the following:
Assoc results = $MyModule.Utils.GetScript()()
It still compiles and runs, but CSIDE places a red error marker next to the line with the text funcReturnTypes is empty. Is there a way to surpress these error messages?
Another pattern I often use is something like this:
if IsDefined( value=$MyModule.Utils.GetValue() )    // do something with value, which is definedend
This results in a Assignment expression found in another expression. Did you mean == instead? warning. Same question: Is there a way to supress this?
[To post a comment, use the normal reply function]
Forum: Content Server Development Forum
Content Server: Knowledge Center CS16

David Templeton

Let’s do the easy one first….J when we developed the CSIDE plugin and source compiling it provided so many new capabilities that were not available to us previously. This one you pointed out:

if IsDefined( value=$MyModule.Utils.GetValue() )

    // do something with value, which is defined

end

This results in a Assignment expression found in another expression. Did you mean == instead? warning. Same question: Is there a way to suppress this?

Is a perfect example that we actually encountered as being a logic error in a lot of cases since the intention was to set the “==” comparator. While it could be added to suppress some warnings, I would be hesitant at this point since it is more of value to catch these and make sure.

This one is more interesting of course, what is the error that is coming up

// GetScript() returns a Script

Script s = $MyModule.Utils.GetScript()

// Execute it

Assoc results = s()

This compiles and works fine. However, I get an error if I simplify the line to the following:

Assoc results = $MyModule.Utils.GetScript()()

David

Hans Stoop

Hi Chris,

Changing the code so CSIDE will not complain anymore will actually make your code better readable and maintainable by somebody else.

Hans

From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Dienstag, 4. Oktober 2016 17:54
To: eLink Recipient
Subject: Supressing warnings & errors in CSIDE

Supressing warnings & errors in CSIDE

Posted by Meyer, Chris On 10/04/2016 11:50 AM

In OScript I often do something like this:

// GetScript() returns a Script

Script s = $MyModule.Utils.GetScript()

// Execute it

Assoc results = s()

This compiles and works fine. However, I get an error if I simplify the line to the following:

Assoc results = $MyModule.Utils.GetScript()()

It still compiles and runs, but CSIDE places a red error marker next to the line with the text funcReturnTypes is empty. Is there a way to surpress these error messages?

Another pattern I often use is something like this:

if IsDefined( value=$MyModule.Utils.GetValue() )

    // do something with value, which is defined

end

This results in a Assignment expression found in another expression. Did you mean == instead? warning. Same question: Is there a way to supress this?

[To post a comment, use the normal reply function]
Forum:	Content Server Development Forum
Content Server:	Knowledge Center CS16

Chris Meyer

Appu wrote:

Just a thought does replacing the$ with the new syntax one with two colons have any effect

No difference.

David wrote:

While it could be added to suppress some warnings, I would be hesitant at this point since it is more of value to catch these and make sure.

I understand your point. Unfortunately, I have hundreds of these and worry it'll obscure errors I need to see.

This one is more interesting of course, what is the error that is coming up

Sorry, I messed up the formatting in the original post. The error message is funcReturnTypes is empty.

Hans wrote:

Changing the code so CSIDE will not complain anymore will actually make your code better readable and maintainable by somebody else.

My examples were a little simplified. My actual use case looks more like this, which I think is quite readable:

function Assoc Execute(Object prgCtx, Record request)    Assoc results = .super('Execute')(prgCtx, request)    if results.ok        results = ...    end    return resultsend

I often use this super function when overriding scripts to fetch and execute the original script. Unfortunately, it's causing these funcReturnTypes is empty errors in CSIDE.

The other example is also simplified. I have an iterator class that works as follows:

while IsDefined( node=iterator.next() )    // do something with nodeend

There's probably room for improvement here (perhaps use a syntax similar to Java). I'll give it some thought.

Thanks for your comments.

Hans Stoop

Hi Chris,

Your super example is now part of the language:

functionvoid SetupPrototypes(

ObjRef self,

Boolean followAncestors = TRUE )

ObjRef prototype

if ( followAncestors )

super.SetupPrototypes( self )

end

prototype = self.AddPrototype("category_id", IntegerType )

prototype.name =[CSNODE_LABEL.Categories]

prototype.multi_value = TRUE

prototype.persona ="node"

end

From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Dienstag, 4. Oktober 2016 21:52
To: eLink Recipient
Subject: RE Supressing warnings & errors in CSIDE

RE Supressing warnings & errors in CSIDE

Posted by Meyer, Chris On 10/04/2016 03:48 PM

Appu wrote:

Just a thought does replacing the$ with the new syntax one with two colons have any effect

No difference.

David wrote:

While it could be added to suppress some warnings, I would be hesitant at this point since it is more of value to catch these and make sure.

I understand your point. Unfortunately, I have hundreds of these and worry it'll obscure errors I need to see.

This one is more interesting of course, what is the error that is coming up

Sorry, I messed up the formatting in the original post. The error message isfuncReturnTypes is empty.

Hans wrote:

Changing the code so CSIDE will not complain anymore will actually make your code better readable and maintainable by somebody else.

My examples were a little simplified. My actual use case looks more like this, which I think is quite readable:

function Assoc Execute(Object prgCtx, Record request)

    Assoc results = .super('Execute')(prgCtx, request)

    if results.ok

        results = ...

end

    return results

end

I often use this super function when overriding scripts to fetch and execute the original script. Unfortunately, it's causing thesefuncReturnTypes is empty errors in CSIDE.

The other example is also simplified. I have an iterator class that works as follows:

while IsDefined( node=iterator.next() )

    // do something with node

end

There's probably room for improvement here (perhaps use a syntax similar to Java). I'll give it some thought.

Thanks for your comments.

[To post a comment, use the normal reply function]
Topic:	Supressing warnings & errors in CSIDE
Forum:	Content Server Development Forum
Content Server:	Knowledge Center CS16

Chris Meyer

Hi Hans,

Your super example is now part of the language:

In the example you posted you'll notice two things:

the function requires a self parameter (sort of how it's done in python); and
feature references are done as self.AddPrototype(...) and not .AddPrototype(...)).

This works fine, but requires every method you might want to override to adopt this convention (and change all calls to these functions to pass a value to self). This is impractical given how much code is already out there.

The super keyword can be used in other ways (e.g., without having to pass self around as a parameter), but has other limitations which forced me to do it differently.

Do you know anywhere else super is commonly used besides CSNODE?

Chris Meyer

As a follow-up, I found a way to hide these errors from the "Problems" tab under the "View Menu".