BlindWanderer/lslint — comment on commit 06977c8cefa28b76ef8ae7d9d16a6c0d30f1f01a
File:  line 0
By BlindWanderer:

(reposting of response made on pull, forgot that we were having the conversation here and not there, with some modifications)

It was a goal to make an article for every constant however...

1) When do you make articles for constants for functions that are pre-release/preview only? You don't want to be too proactive when documenting constants (especially when you don't know their values).
2) Some of the constants share an article. I can't confirm this right now but I believe TEXTURE_BLANK and TEXTURE_PLYWOOD share an article. For some constants it makes no sense to have two separate articles. There are maybe 4 or 5 of these articles (when it comes to the wiki templates, they are a poorly handled edge case).

I'll add a (hidden?) section to the articles that contain just the signature. It's easy enough to add and we can put undocumented constants into it on the function/event articles. lslint won't be the only software that could benefit from this. Then you just need to search for the pre tag with the id "lsl-signature".

Q1: How much do we want to advertise this information? Should it be hidden, collapsed or visible?
Q2: If it is not hidden, should it be in Deep Notes or a separate section?

I'm leaning towards a collapsed Deep Notes sub-section.

The format will be something like:

//Comment - Because comments may be needed.
//The first line will naturally autogenerated by the page template.
function integer llSubStringIndex(string str, string find);//Optional description
event void state_entry();//Optional description
integer PRIM_TYPE = 9;//Optional description

//the user can of course supply extras with the "signature" template variable.
integer PRIM_WHAT //Note: Value not included, it may not be known.
//I don't see a reason to penalize people for not using the ";"

In case you are wondering, I'm Strife Onizuka. It will be a couple of days before I can implement this.