Alex and I work together at Ingres, so I'll more than happily take on
the commit 'responsibility' of this patch when it's vetted.
Chuck
On 01/06/2010 11:41 AM, Alex Trofast wrote:
> Good idea Mateusz, thank you.
>
> I opened the following ticket:
> http://trac.osgeo.org/geos/ticket/314
>
> Thanks
I have read, understand and agree to RFC 2
http://trac.osgeo.org/geos/wiki/RFC2
Thanks,
Chuck
On Tue, 2009-01-13 at 11:10 -0600, Howard Butler wrote:
> On Jan 13, 2009, at 11:08 AM, Paul Ramsey wrote:
>
> > PSC,
> >
> > Chuck has now created and had accepted a large patch to the code base,
> > I
Hi again,
With the holidays over, just want to push this up the stack again. I
want to be sure it's commit ready when I hand it off. Any further
comments?
Thanks,
Chuck
On Fri, 2008-12-19 at 15:42 -0500, Chuck Thibert wrote:
> Hi all,
>
> I've changed the patch based
Hi all,
I've changed the patch based on Paul's comments.
-- combined the two header files for easy maintenance. (This 'fixed' the
configure error by getting rid of the thread safe header.)
-- fixed the char * error.
-- changed the .c from geosTS_c.cpp to geos_ts_c.cpp
-- moved the test executable
amsey wrote:
> I would hazard tests/capi
>
> Other thoughts?
>
> P
>
> On Fri, Dec 19, 2008 at 8:31 AM, Chuck Thibert
> wrote:
> > Got the other comments worked out but I have a couple questions about
> > moving the test programs.
> >
> > 1) The
Got the other comments worked out but I have a couple questions about
moving the test programs.
1) The original test program, geostest.c has been there all along. The
new ones I added were copies of geostest.c. Should everything be moved?
2) Where in the tests directory should they go? They are
> > extern char GEOS_DLL GEOSisValidReason_r(GEOSContextHandle_t handle,
> > const GEOSGeometry* g1);
> >
> > in geosTS_c.h.in is incorrect, the return type should be *char.
> >
> > P
> >
> > On Thu, Dec 11, 2008 at 1:14
Hello all,
Just wanted to find out if there is anything more that needs to be done?
I don't want to send this into the aether and then walk away. :) I'd
love to see this included in the next release version so if there's
anything I can do to help ensure this
Thanks,
Chuck
___
quite clear how that
> magic happens.
>
> I presume it is not happening because you only provided a Makefile.am
> and I guess a similar change needs to happen for VC something or
> other?
>
> Haven't tried the changes on my OpenSUSE VM yet, but hope to at some
> point.
>
heck
these out for me on Mac/Windows.
Thanks,
Chuck
On Thu, 2008-11-27 at 14:17 -0500, Chuck Thibert wrote:
> Hi Paul,
>
> RE: Thread Safe API. I'm looking to finish up in the next day or so,
> assuming no gotchas. Just finalizing the last changes for the old API
> callin
Hi Paul,
RE: Thread Safe API. I'm looking to finish up in the next day or so,
assuming no gotchas. Just finalizing the last changes for the old API
calling the new one. I'm pushing to have it ready for review by Friday,
or early next week.
Chuck
On Thu, 2008-11-27 at 10:08 -0800, Paul Ramsey
Ingres and what better way to help than fix it
ourselves. :)
Chuck
On Mon, 2008-11-10 at 09:38 -0600, Howard Butler wrote:
> On Nov 10, 2008, at 9:27 AM, Chuck Thibert wrote:
>
> > Hi all,
> >
> > I have:
> >
> > Paul, Howard, strk and Frank all at +1, and Mart
Hi all,
I have:
Paul, Howard, strk and Frank all at +1, and Martin abstaining.
No vetos.
I believe that to be enough for approval. I will proceed with the
development of RFC3.
Thank you.
Chuck
___
geos-devel mailing list
geos-devel@lists.osgeo.org
h
Hi all,
Didn't want to crowd the list while the 3.0 stuff was heavy. Seems to
have calmed down a bit.
I haven't had any more comments on the RFC (could be because of the 3.0
stuff mentioned above...) and I'm wondering if it's ready for voting? I
don't want to jump the gun and start coding only t
On Sat, 2008-10-18 at 08:28 +0100, Mark Cave-Ayland wrote:
> Well the definition is fairly woolly as a quick search revealed that the
> distinction between thread safety and re-entrancy is not always apparent
> in various descriptions of the functions. Probably the best descriptions I
> found were
I like it when the compiler can catch my mistakes. :) I've not seen _HS
before. Does it mean something particular?
Chuck
On Fri, 2008-10-17 at 14:25 -0500, Howard Butler wrote:
> On Oct 17, 2008, at 2:06 PM, Frank Warmerdam wrote:
> >
> > I'd add that I'd like the RFC to define the context of t
this as I'm not going for
re-entrancy but it is 'more standard.' Mark, it was your comment,
rebuttal? :) Otherwise I think I'll go back to TS since I'm not
guaranteeing re-entrance.
Thanks,
Chuck
On Fri, 2008-10-17 at 15:06 -0400, Frank Warmerdam wrote:
> Chuck Thib
RFC updated.
Thanks Frank.
Chuck
On Fri, 2008-10-17 at 14:36 -0400, Frank Warmerdam wrote:
> Chuck Thibert wrote:
> > Hello all,
> >
> > Thanks for the feedback on my initial proposal. I have updated the
> > proposal with said feedback and posted an official RF
Hello all,
Thanks for the feedback on my initial proposal. I have updated the
proposal with said feedback and posted an official RFC on Trac at:
http://trac.osgeo.org/geos/wiki/RFC3
Thanks,
Chuck
___
geos-devel mailing list
geos-devel@lists.osgeo.org
6:02 -0400, Frank Warmerdam wrote:
> >> On Tue, Oct 14, 2008 at 11:12 AM, Chuck Thibert
> >> <[EMAIL PROTECTED]> wrote:
> >>> Hi,
> >>>
> >>> I have been prototyping a thread safe CAPI. I have attached a simple
> >>> proposal/
de.
>
> P.
>
> On Tue, Oct 14, 2008 at 11:12 AM, Chuck Thibert
> <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I have been prototyping a thread safe CAPI. I have attached a simple
> > proposal/design intent. I have sample executables and test data that
Hi,
I have been prototyping a thread safe CAPI. I have attached a simple
proposal/design intent. I have sample executables and test data that
will illustrate the thread issues but I don't want to flood the mailing
list with them. If the proposal attached looks decent to you all I'll
create a ne
Hi all,
As preparation for proposing a thread safe CAPI fix I thought I'd get my
feet wet and fix a simple bug currently in Trac. I've attached a patch
to bug #197 that fixes the seg fault.
Thanks,
Chuck
___
geos-devel mailing list
geos-devel@lists.osg
23 matches
Mail list logo
