On 02/02/2015 03:25 AM, sebb wrote:
> I would not wish to move away from Java RE *unless* the RE syntax was
> the same *and* the implementation was better performing *and* the
> existing code suffered from poor performance.
>
> It might be OK if the alternate implementation was missing some
> esot
Hi
I have a patch waiting to be committed to commons-imaging which uses
the LZW stuff in commons-compress (brief mention of it by me on
IMAGING-126), so it could break with these changes. My hope was to
wait for the next release of compress before committing, so I could
use that version of compres
I would not wish to move away from Java RE *unless* the RE syntax was
the same *and* the implementation was better performing *and* the
existing code suffered from poor performance.
It might be OK if the alternate implementation was missing some
esoteric features, but I would be very wary of using
To be clear, I am not advocating this approach. I was merely trying to
illustrate what a nightmare such an endeavor would be. :)
On Sunday, February 1, 2015, James Carman
wrote:
> You would basically have to pick a canonical regex language if you want a
> facade and be able to swap the regex li
On 1 February 2015 at 18:33, Jochen Wiedmann wrote:
> On Sun, Feb 1, 2015 at 7:04 AM, Stefan Bodewig wrote:
>
>> * (Internal)LZWInputStream has a bunch of protected fields that slipped
>> through a few releases ago. We should add getter/setter pairs and
>> deprecate using the fields. Sebb w
On 02/01/2015 08:47 PM, Gonçalo Marques wrote:
> On Sun, Feb 1, 2015 at 7:12 PM, Thomas Neidhart
> wrote:
>>
>> On 02/01/2015 07:44 PM, sebb wrote:
>>> On 31 January 2015 at 18:40, Gonçalo Marques
>>> wrote:
Hi,
I've sent a pull request containing CollectionUtils refactor for revie
On 1 February 2015 at 07:45, Reto Gmür wrote:
> In the clerezza code and in the SVN commons proposal code along the
> following lines will works as expected.
>
> {a,b,c,d,e} is a set of 5 BlankNodes (i.e. we have 5 objects, no two of
> them are equals).
>
> g.add(a, RDF.type, EX.Sphere);
> g.add(b
Are you all familiar with the expression, 'excessive fascination with
the Apache brand?' Here I am expressing the exact opposite. If there
are people out there reading this who have a potential use for this
thing, I encourage them to kick its tires. If that leads to some
enthusiasm, I'm willing to
On Sun, Feb 1, 2015 at 7:12 PM, Thomas Neidhart
wrote:
>
> On 02/01/2015 07:44 PM, sebb wrote:
> > On 31 January 2015 at 18:40, Gonçalo Marques
> > wrote:
> >> Hi,
> >>
> >> I've sent a pull request containing CollectionUtils refactor for review
> >> (COLLECTIONS-551).
> >>
> >> Since the next re
On 02/01/2015 07:44 PM, sebb wrote:
> On 31 January 2015 at 18:40, Gonçalo Marques
> wrote:
>> Hi,
>>
>> I've sent a pull request containing CollectionUtils refactor for review
>> (COLLECTIONS-551).
>>
>> Since the next release version is 4.1, I'm wondering if methods that were
>> deprecated which
Sorry for those who already reviewed the release candidate, I'm going to
cut a new RC once we've figured out what to do about LZWInputStream.
Stefan
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional comm
On 31 January 2015 at 18:40, Gonçalo Marques
wrote:
> Hi,
>
> I've sent a pull request containing CollectionUtils refactor for review
> (COLLECTIONS-551).
>
> Since the next release version is 4.1, I'm wondering if methods that were
> deprecated which are tagged with "@since 4.1" shouldn't be prom
You would basically have to pick a canonical regex language if you want a
facade and be able to swap the regex library out. Most of them are very
similar but they are not the same.
On Sunday, February 1, 2015, Gary Gregory wrote:
> I think we'll need some clear performance advantages documented
On 02/01/2015 02:06 PM, Alina Ciobanu wrote:
> Hello everyone,
> My name is Alina Ciobanu. I'm a first-year Ph.D. student in computer science
> (NLP) at the Faculty of Mathematics and Computer Science, University of
> Bucharest, Romania. I am interested in contributing to the Apache Commons
> Ma
On Sun, Feb 1, 2015 at 7:04 AM, Stefan Bodewig wrote:
> * (Internal)LZWInputStream has a bunch of protected fields that slipped
> through a few releases ago. We should add getter/setter pairs and
> deprecate using the fields. Sebb would like to even make the fields
> private assuming the
All I care about is binary compatibility in a minor release for most cases
(not 80% of the cases, but more like 99.9%). I do not want to be in jar
hell.
Gary
On Sun, Feb 1, 2015 at 1:04 AM, Stefan Bodewig wrote:
> Hi
>
> I'm trying to bring together two separate discussions from two different
>
I think we'll need some clear performance advantages documented as well as
any compatibility issues.
This begs for a facade API IMO. I would not want to recode my app just to
test one vs. the other, it should be pluggable.
Gary
On Sat, Jan 31, 2015 at 10:58 AM, Benson Margulies
wrote:
> So, on
Send from my mobile device
> Am 01.02.2015 um 07:04 schrieb Stefan Bodewig :
>
> Hi
>
> I'm trying to bring together two separate discussions from two different
> [VOTE]-threads. It seems as if I should cancel the RC2 vote and before
> I rush another RC maybe we can get consensus on what to d
Hello everyone,
My name is Alina Ciobanu. I'm a first-year Ph.D. student in computer science
(NLP) at the Faculty of Mathematics and Computer Science, University of
Bucharest, Romania. I am interested in contributing to the Apache Commons Math
library. My idea is to work on the clustering module
Github user berndhopp closed the pull request at:
https://github.com/apache/commons-io/pull/5
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user berndhopp opened a pull request:
https://github.com/apache/commons-io/pull/5
initial commit
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/berndhopp/commons-io
introduce_threadlocal_buffers_to_avoid_memory_allocatio
21 matches
Mail list logo
