Re: sharing perl data structures across tests

2010-04-02 Thread Erik Osheim
On Fri, Apr 02, 2010 at 09:26:46AM +0200, nadim khemir wrote: > Same for me. I simply didn't understand what the original mail meant. Not at > all! Apologies. There were some (dumb) typos that I didn't see when I re-read the email, and I didn't do a very good job of illustrating what the problem

Re: sharing perl data structures across tests

2010-04-02 Thread Aristotle Pagaltzis
* Ovid [2010-04-02 10:05]: > It's an art to write a concise email which describes a problem. > What I often find myself doing is writing a long email and then > summarising at the bottom. When that's done, I often > cut-n-paste the summary at the top of the email and only leave > the rest if it is

Re: sharing perl data structures across tests

2010-04-02 Thread Ovid
--- On Fri, 2/4/10, Erik Osheim wrote: > From: Erik Osheim > > I assume either > some code builds it > > and others then need it or it's expensive to > build?  If it's the > > former, it implies an ordering dependency and coupling > in your tests > > which greatly lowers their utility. > > It'

Re: sharing perl data structures across tests

2010-04-02 Thread Erik Osheim
On Fri, Apr 02, 2010 at 12:03:13AM -0700, Ovid wrote: > I see no one's answered this yet. I was hoping for more clarification > lest my (mis)understanding hampers things. You have a large data > structure to share across tests and I assume either some code builds it > and others than need it or it

Re: sharing perl data structures across tests

2010-04-02 Thread Ovid
--- On Fri, 2/4/10, nadim khemir wrote: > From: nadim khemir > Same for me. I simply didn't understand what the original > mail meant. Not at > all! It's an art to write a concise email which describes a problem. What I often find myself doing is writing a long email and then summarising at

Re: sharing perl data structures across tests

2010-04-02 Thread nadim khemir
> I see no one's answered this yet. I was hoping for more clarification lest my (mis)understanding hampers things. You have a large data structure to share across tests and I assume either some code builds it and others than need it or it's expensive to build? If it's the former, it implies an

Re: sharing perl data structures across tests

2010-04-02 Thread Ovid
--- On Wed, 31/3/10, Erik Osheim wrote: > From: Erik Osheim > So at $WORK we have a bunch of really > large data (immutable) data > structures which a ton of our source code uses. As such, > most tests > that we write need to access these data structures to run. > These > structures can't (curr