Re: More descriptive error messages from Inline.

It is a rare module that gives *too much* diagnostic output, and I doubt
that Inline is one of them. I endorse the idea, though I don't have any
tuits to help with the effort. My use of Inline is uncommon enough that I
don't encounter this pain point.

David
On Nov 3, 2012 7:51 PM, "David Oswald" <[email protected]> wrote:

> I was doing some maintenance work on the meta-stuffs for
> Math::Prime::FastSieve the other day.  (Inline::CPP is one of its
> dependencies, and indirectly Inline and Inline::C).   Along the way I made
> a couple of minor mistakes that generated errors from Inline.  I think at
> one point it was that my _Inline folder was stale as related to the bump in
> Math::Prime::FastSieve version number, and the second was that I changed
> the version number only in one place in M::P::FS, and got a message
> reminding me it needed to be changed in two places in modules that are
> based on Inline::*.
>
> It was quick enough tracking down the source of the trouble.  But I noticed
> that the error messages weren't telling me who was generating them.  It
> might have been more convenient if the Inline messages started out like
> this:  "Inline error: .....message here....".
>
> Perhaps we should be looking at our Inline and Inline::Language modules to
> see that we're providing messages that identify who generated the error
> message.
>
> Dave
>
> --
>
> David Oswald
> [email protected]
>