Making the PSI stable...

Are there any plans to make the PSI a stable part of the product. I understand that the current situation is that it can change without notice or fanfare and that it's not documented or supported on purpose.

However, I love some of the plugins that rely on it and I'd hate to think of them breaking periodically.

Is it time to recognize that the plugins are a significant part of the IDE (as the Plugin Manager implies) and document and support the PSI and manage its changes like a regular API.

What are other people's thoughts on this?

4 comments

If the next version includes anything like as many Psi-impacting changes as Aurora (generics, aspects, modules), then there's no real chance of the Psi stabilizing.

--Dave

0

Presumably it will be stabilised for the -release- of Aurora. Bear in mind
that what we're using at the moment is an early access preview version.
Hopefully they'll provide documentation for it with the release, too.

Vil.

joe martinez wrote:

Are there any plans to make the PSI a stable part of the product. I understand that the current situation is that it can change without notice or fanfare and that it's not documented or supported on purpose.

However, I love some of the plugins that rely on it and I'd hate to think of them breaking periodically.

Is it time to recognize that the plugins are a significant part of the IDE (as the Plugin Manager implies) and document and support the PSI and manage its changes like a regular API.

What are other people's thoughts on this?


--
Vilya Harvey
vilya.harvey@digitalsteps.com / digital steps /
(W) +44 (0)1483 469 480
(M) +44 (0)7816 678 457 http://www.digitalsteps.com/

0

Declaring an API stable early is evil.
Declaring an API stable late is evil.
Declaring an API stable very late is evil.

Wait for the release... Everything else would be "a shoot in your knee"...


0

Please sign in to leave a comment.