Perl6 RFC Librarian wrote:
[...]
> =head1 TITLE
>
> All perl generated errors should have a unique identifier
>
[...]
> An id string could have some structure associated to enable
> better handling. One suggestion was to follow the lead of VMS.
>
> facility:
> The program (or, in perl's case, the thing that errored)
> status:
> I=information, W=warning, E=error, S=Severe error
> message-code:
> A one word abbreviation for the text message
>
> text message:
> A human readable string with more detail
>
> A sample error:
>
> %APPEND-I-CREATED, MEM.SUM;1 created
>
> For perl the actual text would be in $@.
>
As an aside here, on VMS message text is kept in sharable images, which
are dynamically linked to executables. This means that, for example,
the same executable can run on one machine with English messages, and
a different machine with French messages, without needing to recompile
or relink.
[...]
> =head1 REFERENCES
>
> IBM Messages and Codes
>
> VMS (anyone have a reference)
http://www.openvms.compaq.com:8000/72final/6100/6100pro_contents.html#toc_chapter_3
>
> SCCS
