summaryrefslogtreecommitdiff
path: root/t/porting
Commit message (Collapse)AuthorAgeFilesLines
* Test for +x bits for all the files in exec-bit.txtFlorian Ragwitz2010-08-191-4/+4
| | | | The globbing only works when done in the right directory.
* Remove invalid version object from diag.t exceptionsDavid Golden2010-08-121-1/+0
|
* Refactor porting/diag.t and improve output formatDavid Golden2010-08-121-20/+35
| | | | | | | | | | Adds a subroutine to standardize messages variants into a form that appears in perldiag.pod. Standardizes "panic: ..." instead of skipping it. Tests files in sorted order; improves diagnostic output format for readability; only shows pass/fail once for each diagnostic message
* Add perldiag entries for new version format errorsDavid Golden2010-08-121-0/+9
| | | | | Also updates porting/diag.t to standardize the detected messages into the format used in perldiag.pod
* Improve diag.t to detect BADVERSION diagnosticsDavid Golden2010-08-121-17/+20
|
* Fix file name in commentDavid Cantrell2010-08-021-1/+1
|
* Improve Porting/checkAUTHORS.plDavid Golden2010-07-301-1/+1
| | | | | | | Rationalized options and usage message. The new "--who" option now gives full names as provided in the AUTHORS file. Updated t/porting/authors.t for the new option syntax.
* Keep test output pretty by actually using skip_all()'s message...George Greer2010-07-261-3/+2
|
* MSWin32's "-x" checks file extension, so it isn't useful for exec-bit.tGeorge Greer2010-07-261-0/+4
|
* Add filename with spurious +x bit to diag in t/porting/exec-bit.tGeorge Greer2010-07-261-1/+1
| | | | | This is for the benefit of smoke logs where the "not ok" aren't shown but the diag() output is.
* Make the success and failure messages of t/porting/diag.t more clear, and ↵James Mastros2010-07-261-4/+19
| | | | add comments
* Document "Ambiguous use of -%s resolved as -&%s()"James Mastros2010-07-261-1/+0
|
* Document "Ambiguous use of %c{%s%s} resolved to %c%s%s"James Mastros2010-07-261-1/+0
|
* Document "Ambiguous use of %c{%s} resolved to %c%s"James Mastros2010-07-261-1/+0
|
* Document "Ambiguous use of %c resolved as operator %c"James Mastros2010-07-261-1/+0
|
* Stick a comment in t/porting/diag.t begging people not to abuse the ignore listJames Mastros2010-07-261-0/+3
|
* Normalize formatting of "Ambiguous call resolved as CORE::%s(), qualify as ↵James Mastros2010-07-261-1/+0
| | | | such or use &" in toke.c, so t/porting/diag.t can find it.
* Port dual-life.t to VMS.Craig A. Berry2010-07-241-2/+5
| | | | | The utils have a .com extension and filename case may not be preserved.
* Global executable bit cleanupDavid Golden2010-07-242-0/+43
| | | | | | | | | | | | | | | | | | | | When porting/makerel runs, all files copied into the directory for the tarball have the executable bit stripped and then only a specific set of files have the executable bit restored. There are many files in the repo that have the executable bit set in the repo that will be stripped. So that the state of files in the repo is as close as possible to the state of files in the release tarball, the executable bit has been stripped from such files. In one recent case, a file added from a dual-life module needed the executable bit set. Because it had the bit in the repo but was not listed in makerel to get an executable bit, tests using it passed in the repo and failed in the tarball. This commit refactors the list into a new file, Porting/exec-bit.txt and add tests to detect a mismatch between files listed there and actual executable bits in the repo.
* Use .\ instead of ./ on WindowsJan Dubois2010-07-201-1/+2
|
* don't use Test::More in dual-life.tDavid Golden2010-07-201-1/+4
|
* Add exceptions to dual-life.tDavid Golden2010-07-191-1/+12
|
* Added t/porting/dual-life.tDavid Golden2010-07-181-0/+29
| | | | | | Because we manually generate Makefiles, any executables need to be generated from .PL files in utils/. This test checks if dual-life executables show up in utils/.
* Make checkAUTHORS a test to further reduce the release burdenJesse Vincent2010-07-041-0/+19
|
* Allow the "diag_listed_as" annotation to work on multi-line function calls.Nicholas Clark2010-06-291-1/+3
| | | | | | Previously it would only work if the comment was on the line immediately preceding the closing /\);/, which was fine for croak()/die()/etc function calls all on one line, but not so useful for longer calls.
* Better diagnostics on detecting case sensitive file name clashes.Nicholas Clark2010-06-121-1/+2
|
* PATCH: teach diag.t new warning function namesKarl Williamson2010-06-011-21/+63
| | | | | | | | | | | | | | | | | A number of function names that do warnings have been added, but diag.t hasn't kept up. This patch changes it to look for likely function names in embed.fnc, so it will automatically keep up in the future. There's no need to worry about it looking for inappropriate functions, as the syntax of messages that it looks for is so restrictive, that there won't be false positives. Instead there are still many messages it fails to catch. As a result of it's falling behind several issues have crept in. I resolved the couple I thought were clear (including one in a comment; diag.t doesn't strip comments, but mostly it doesn't matter), and added the others to the <DATA> section to ignore. are
* Don't require doubled backslashes in perldiag.podKarl Williamson2010-05-301-8/+9
| | | | | Prior to this patch, messages in perldiag.pod had to have \\ instead of the correct single backslash in order for diag.t to not complain.
* Fix the regexp in t/porting/args_assert.t, and add 3 missing macros.Nicholas Clark2010-05-291-2/+2
| | | | Resolves RT #72800.
* PATCH: Clean up EBCDIC handling of \cXKarl Williamson2010-05-171-1/+0
| | | | | | | | | | The function perl_ebcdic_control() is unnecessary, as the toCTRL macro that calls it can be changed to just map EBCDIC to ASCII first, and then doing the normal procedure. This means that EBCDIC and ASCII will no longer diverge. Currently, EBCIDIC gives a syntax error for inputs outside its domain, whereas the ASCII version accepts some of them.
* Deal with "\c{", and its kinKarl Williamson2010-04-261-0/+1
| | | | | | | | | | | | | | | | | | make regen is needed This patch forbids non-ascii following the "\c". It also terminates for "\c{" with a message to contact p5p if there is need for continuing its current definition. And if the character following the "\c" causes the result to not be a control character, a warning is issued. This is currently 'deprecated', which by default is turned on. This can easily be changed later. This patch is the initial patch. It does not do any fancy showing the context where the problematic construct occurs. This can be added later. It gathers the 3 occurrences of evaluating \c and puts them in one common routine.
* Omnibus strict and lax version parsingDavid Golden2010-01-131-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Authors: John Peacock, David Golden and Zefram The goal of this mega-patch is to enforce strict rules for version numbers provided to 'package NAME VERSION' while formalizing the prior, lax rules used for version object creation. Parsing for use() is unchanged. version.pm adds two globals, $STRICT and $LAX, containing regular expressions that define the rules. There are two additional functions -- version::is_strict and version::is_lax -- that test an argument against these rules. However, parsing of strings that might contain version numbers is done in core via the Perl_scan_version function, which may be called during compilation or may be called later when version objects are created by Perl_new_version or Perl_upg_version. A new helper function, Perl_prescan_version, has been added to validate a string under either strict or lax rules. This is used in toke.c for 'package NAME VERSION' in strict mode and by Perl_scan_version in lax mode. It matches the behavior of the verison.pm regular expressions, but does not use them directly. A new test file, comp/packagev.t, validates strict and lax behaviors of 'package NAME VERSION' and 'version->new(VERSION)' respectively and verifies their behavior against the $STRICT and $LAX regular expressions, as well. Validating these two implementation should help ensure they each work as intended. Other files and tests have been modified as necessary to support these changes. There is remaining work to be done in a few areas: * documenting all changes in behavior and new functions * determining proper treatment of "," as decimal separators in various locales * updating diagnostics for new error messages * porting changes back to the version.pm distribution on CPAN, including pure-Perl versions
* With $PERL_UNICODE we still need to find utf8.pmH.Merijn Brand2010-01-121-0/+1
|
* Run t/porting/diag.t from the top-level directory.Nicholas Clark2009-12-191-5/+7
| | | | | | | | | The home-grown glob on VMS does not properly handle relative paths containing C<../> so this test has been failing for reasons having nothng to do with what's being tested. For now, just avoid the problem by running from one level up. Message-id: <20091219161943.GQ2582@plum.flirble.org>
* Fix -DPERL_NO_UTF16_FILTEREric Brine2009-11-301-4/+4
|
* Inline PL_no_symref into pp_entersub. Deprecate the visible global variable.Nicholas Clark2009-11-151-0/+1
| | | | | | | | | | | As the core no longer needs this fixed string in more than one place, it seems daft to go to the overhead (and cost) of making it public in case any module wants to use it. Modules that do want to use it should provide their own inline copy in future. Also restore the visible global PL_no_symref back to the original format specification (of 5.10.0 and earlier), as an extra %s has the potential to cause SEGVs or worse if not spotted at compile time.
* Documentation for the 'qr' overload.Ben Morrow2009-11-011-1/+0
|
* ../lib isn't valid after a chdir "..";H.Merijn Brand2009-10-221-0/+1
|
* Normalise 3 fatal pack/unpack error messages to "panic: %s"Nicholas Clark2009-10-121-3/+0
|
* porting/manifest.t now tests that all files listed in MANIFEST are present.Nicholas Clark2009-10-111-0/+2
|
* Add a test for the bootstrap rules for tests in t/Nicholas Clark2009-10-091-0/+47
|
* Makefile and makefile only exist on case-sensitive file systems, so allow them.Nicholas Clark2009-10-071-2/+4
|
* Remove BEGIN{}, use '..', part deuxMax Maischein2009-10-072-16/+1
|
* sort @files once, outside the loop.Nicholas Clark2009-10-061-1/+1
|
* Standarise t/porting/*.t on ./test.pl, and remove BEGIN boilerplate.Nicholas Clark2009-10-063-13/+16
|
* podcheck.t now uses MANIFEST to choose which files it should checkJesse Vincent2009-10-051-14/+16
|
* We don't actually want to check .PL filesJesse Vincent2009-10-051-2/+2
|
* Check POD in lib/, ext/ and pod/Max Maischein2009-10-051-0/+85
|
* Remove :raw open mode from testsMax Maischein2009-10-051-2/+2
| | | | Message-ID: <4ACA2753.4080100@corion.net>
* Change warning "Unicode character is illegal" to more accurate descriptionRafael Garcia-Suarez2009-10-031-1/+1
| | | | | That now reads "Unicode non-character is illegal in interchange" and the perldiag documentation is expanded a bit.
View Lorry Controller Status