PDL/BUGS at master · dkogan/PDL · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
REPORTING BUGS
--------------

Please submit bug reports via the sourceforge bug tracker
interface at

   http://sourceforge.net/tracker/?group_id=612&atid=100612

where you can review the previously submitted bug reports.
Click on "Add new" to generate a bug report.  If you do not
already have a sourceforge.net account, you will need to
get one to submit the report:

   http://sourceforge.net/account/registration/

Please provide a way for the PDL developers to contact you
regarding the problem.

Try to include any information you think might help someone
isolate, reproduce, and fix your problem.

At a *minimum*, include the following information:

    * PDL version number (e.g. PDL-2.4.7)

    * Perl version information
      (output from "perl -v" or "perl -V", even better!)

    * Operating System
      (run the "uname -a" command on many unix systems)

    * If you are reporting a bug with an installed PDL,
      please include the full output of "perldl -V"

      If the PDL has compiled and built but not been
      installed, you may run "perl -Mblib perldl -V"
      from the top level of the PDL build directory.

    * The bug description and how to reproduce it.
      Short examples using the PDL shell, pdl2 (or
      perldl), are excellent!


Other things that are often helpful:

    * Details about your operating environment
      that might be related to the problem

    * Exact cut and pasted error or warning messages

    * The shortest, clearest code you can manage
      to write which reproduces the bug described.

    * A patch against the latest released version
      of this distribution which fixes this bug.


Alternatively, send an e-mail report with the above
information (including the output of 'perldl -V')
to pdl-porters@jach.hawaii.edu . See

   http://pdl.sourceforge.net/maillists/

for info on how to subscribe to this list.


BEFORE YOU SEND A REPORT
------------------------

BEFORE you report a bug make sure you got the latest
release version of PDL (always available from CPAN,
check http://search.cpan.org/search?dist=PDL). Also
check the FAQ (http://pdl.sourceforge.net/FAQ) and
the mailing list archives for hints. You can find
links to the searchable archives at

   http://pdl.sourceforge.net/maillists/


PATCHES
-------

Patches can be sent to the pdl-porters mailing list
(see above) or can be directly submitted to the
patch manager

   http://sourceforge.net/tracker/?atid=300612&group_id=612

Patches should be made against the latest released
PDL or, ideally, against the current git sources
which you can browse and check out at

   git://pdl.git.sourceforge.net/gitroot/pdl/pdl


Thanks,
The pdl-porters team.