On 19/02/06 03:48, Jonathan Lang wrote:
I don't see why you'd need a universal anti-backwhack, any more than
you need universal quote delimiters.
Here-docs are usually safe to quote any amount of line noise,
but I take your point.
I could see introducing
On 2/18/06, The Perl 6 Summarizer <[EMAIL PROTECTED]> wrote:
> Smart match table
> Robin Houston had some questions/observations about the smart match
> table in synopsis 4. This is the table that describes how the smart
> match ("~~") operator does its comparisons. It turns out that
Brad Bowman wrote:
> I don't like the idea of sharing the adverb between escaping and
> force-interpolating since stacking other adverbs can turn q into qq
> and vice-versa. That's a minor quibble though.
And a reasonable one as well. I was trying to minimize the
proliferation of adverbs, but I
# New Ticket Created by Leopold Toetsch
# Please include the string: [perl #38593]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=38593 >
The JIT compiler tools/build/jit2h.pl creates src/{jit,exec}_cpu.c from
src/jit/*/c
Adam,
I have one more edgey case I'd like to see on this list:
>
> 13. Tests exist, but fail to be executed.
> There is tests, but the tests themselves aren't failing.
> It's the build-process that is failing.
>
> 14. Tests run, and some/all tests fail.
> The normal FAIL case
Tyler MacDonald <[EMAIL PROTECTED]> wrote:
> Adam,
> I have one more edgey case I'd like to see on this list:
> Tests run, but >50% (or maybe >80%?) are skipped.
>
> From what I've seen, the most common cause of this is that the
> package is untestable with the current build
I'm starting to get a bit closer (waiting on a test images and some last
testing to be done) to finishing the initial PITA test cycle (and thus
be able to do an initial release) and so I'm starting to do some prep
work now for the next stage, which is to start to assemble some
infrastructure ar
> On Sun, 19 Feb 2006 22:22:20 +1100, Adam Kennedy <[EMAIL PROTECTED]> said:
> 1. Broken or corrupt packaging.
> A bad tarball, MANIFEST files missing.
Make sure you verify that all files in the distro are readable. Reject
if the permissions are bogus. Recently we had an increasig nu
Tyler MacDonald wrote:
Tests run, but >50% (or maybe >80%?) are skipped.
From what I've seen, the most common cause of this is that the
package is untestable with the current build configuration. Eg; you
needed
to specify a webserver or database or something to get these tests
While an interesting idea, I forsee two challenges to doing this...
Firstly is that it might turn an otherwise normal result into something
else, with no clear rule. It makes a judgement call that some level of
testing is good or bad, which isn't really the place of an installer to
call.
The
On Sun, Feb 19, 2006 at 03:28:32PM -0800, Leopold Toetsch wrote:
> *) jit2h.pl doesn't create a .h file - a better util name couldn't harm
I've renamed it to jit2c.pl and added a JIT_BUILD_TOOL var in the root
makefile so the path of this utility is no longer repeated encoded.
-J
--
pgpKmgEPz
(Andreas J. Koenig) wrote:
On Sun, 19 Feb 2006 22:22:20 +1100, Adam Kennedy <[EMAIL PROTECTED]> said:
> 1. Broken or corrupt packaging.
> A bad tarball, MANIFEST files missing.
Make sure you verify that all files in the distro are readable. Reject
if the permissions are bogus. Recentl
12 matches
Mail list logo
