| 1 |
On 2017-10-07 17:03, Andreas K. Huettel wrote: |
| 2 |
> … |
| 3 |
> This release brings several incompatible changes, also as a |
| 4 |
> consequence of fixing a security problem [1]. |
| 5 |
|
| 6 |
This reads kind of awkwardly. Maybe something along this lines of: |
| 7 |
|
| 8 |
This release brings several incompatible changes as a result of |
| 9 |
deprecations coming to term [#] and mitigating a potential security |
| 10 |
issue [#]. |
| 11 |
|
| 12 |
I wouldn’t really consider the security risk eliminated, but |
| 13 |
mitigated as the vector of attack remains if program or module adds the |
| 14 |
current working directory to @INC on its own. The interpreter just isn’t |
| 15 |
adding it to @INC. |
| 16 |
|
| 17 |
> Typical errors are |
| 18 |
> "Can't locate inc/... in @INC (you may need to install the inc::... module)" |
| 19 |
> "error: ... has no member named ‘op_sibling’" |
| 20 |
> "Unescaped left brace in regex is illegal in ..." |
| 21 |
|
| 22 |
I would make this look more like a proper list. |
| 23 |
|
| 24 |
Typical errors are: |
| 25 |
* Can't locate inc/... in @INC (you may need to install the |
| 26 |
inc::... module) |
| 27 |
* error: ... has no member named ‘op_sibling’ |
| 28 |
* Unescaped left brace in regex is illegal in ... |
Archives