Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
perl.inline
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion More descriptive error messages from Inline.
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
David Mertens  
View profile  
 More options Nov 6 2012, 10:15 am
Newsgroups: perl.inline
From: dcmertens.p...@gmail.com (David Mertens)
Date: Tue, 6 Nov 2012 09:09:10 -0600
Local: Tues, Nov 6 2012 10:09 am
Subject: Re: More descriptive error messages from Inline.
Print | View thread | Show original | Report this message | Find messages by this author
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" <daosw...@gmail.com> 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
> daosw...@gmail.com


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google