No OUTPUT/INPUT CLOSE

If I have:

OUTPUT TO "/v/my-file.dat".

I would like to know I don't have an OUTPUT CLOSE statement. Did I miss this rule?


Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Hmmm, something is not

Hmmm, something is not right. I have a message stating a stream is defined but never used. It is used, however, it is not closed. This is misleading.


sample code

Do you have sample code producing this misleading message?


Ready!

We have finished the rule.
Jurjen found it usefull enough to add to the standard rules.
It is also attached to this comment (including faulty testfile) if you don't want to wait for a new release.


Released

The new rule that Niek made (streamclose) is in the new Prolint release that is now available at page http://www.oehive.org/prolint/download.

Since the release is available I have removed the attachment from the previous post in this forum-thread.


I am just starting with

I am just starting with ProLint and need to practise.
I am working on this rule and will donate it when ready.

If you haven't build it yet yourself and if anyone's interested.


Niek, That would be awesome!

Niek, That would be awesome! If you wouldn't mind sharing how you do it, that would be great too. I'm getting a team of about 10 onboard using Prolint and would love to start customizing.


I have programmed the rule

I have programmed the rule as far as I could, but got stuck on named streams. I have mailed the code to Jurjen for help.

On "How I did it"? Trial and error, read and copy some from other rules, read the ProParse API-reference and some knowledge on nodes-childs-siblings which I had from XML.
I can't really explain any better.


jurjen's picture

Hi Jay, You are right, I

Hi Jay,

You are right, I don't think we currently have a rule that checks if streams are closed.