[erlang-questions] Fwd: Suggestion: New Info item for process_info/2

Edwin Fine erlang-questions_efine@REDACTED
Fri May 16 17:46:08 CEST 2008


Actually, Bengt, that is *exactly* what I would like. Great suggestion.
Ed

On Fri, May 16, 2008 at 3:07 AM, Bengt Kleberg <bengt.kleberg@REDACTED>
wrote:

> Greetings,
>
> There is probably a reason for process_info/1 being restricted to
> debugging (it might not be possible to interrupt and takes too much
> time?). Adding 'all' to process_info/2 should turn it into
> process_info/1 (or a super set of it) and make it as ''bad''.
> What you probably want is process_info_available/0 which returns a list
> of atoms.
>
>
> bengt
>
> On Thu, 2008-05-15 at 13:13 -0400, Edwin Fine wrote:
> > LOL. I probably deserved that. Thanks for the replies - SOMEONE is out
> > there!
> >
> > Matt, the solution is workable, and I avoid pain as much as the next
> > guy, but I really want to have something that will TELL me what all
> > the valid process_info items are. process_info/1 only gives me SOME of
> > them and is for debugging only.
> >
> > Ok, then; here's a suggestion:
> >
> > Erlang team, How about adding an info item of "all" for
> > process_info/2? It won't break the interface, and it will allow people
> > like me to "query" process_info for which items are valid.
> >
> > Regards,
> > Edwin Fine
> >
> > On Thu, May 15, 2008 at 5:01 AM, Matthias Lang <matthias@REDACTED>
> > wrote:
> >         Edwin Fine writes:
> >
> >          > I don't know if my first post just didn't make it, or got
> >         ignored because I
> >          > inadvertently offended someone, or perhaps it asked too
> >         boring a
> >          > question.
> >
> >
> >         I thought "the guy's figured out a perfectly workable solution
> >         but is
> >         tying himself in knots to avoid using it because it doesn't
> >         seem
> >         painful enough." Either that, or he hasn't managed to explain
> >         what he
> >         really wants to do.
> >
> >         Matt
> >
> >
> >
> >
> > _______________________________________________
> > erlang-questions mailing list
> > erlang-questions@REDACTED
> > http://www.erlang.org/mailman/listinfo/erlang-questions
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://www.erlang.org/mailman/listinfo/erlang-questions
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20080516/e79d96d5/attachment.htm>


More information about the erlang-questions mailing list