Re: GNUstep Code Freeze

[Gregory Casamento]

Fred,

Richard said it was okay, since we didn't have anything before which
worked at all.  I implemented something before the freeze which uses
NSXMLParser and committed it to the trunk.  It does basic operations,
but it is not based on libxml2 so it can't do Xpath operations, so
although it works for some things, it is useless for complex
operations of any kind.

Currently the code in the branch is in flux.  It is much more
functional than the code which is currently on the trunk and it may be
"ready" prior to the release, but I think it's best to leave it until
the next release to give it some additional time to be vetted and for
it to mature.

GC

On Mon, Jan 30, 2012 at 3:30 AM, Fred Kiefer <address@hidden> wrote:
> On 30.01.2012 02:27, Gregory Casamento wrote:
>>
>> As for the XML work, I would like to get it into this release, but at
>> this point I'm not sure it's ready even though the code on the branch
>> is MUCH more complete and functional than what is on the trunk in base
>> at this point.
>
>
> This is of course Richard's decision but I would argue strongly against this
> kind of late change. Event though the old code was unusable it could get
> worse just because of a minor compilation issue on some untested platform.
> Lets merge this change after the release and give it the testing it
> deserves.
>
> Fred
>
>
>
> _______________________________________________
> Gnustep-dev mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/gnustep-dev



-- 
Gregory Casamento
Open Logic Corporation, Principal Consultant
yahoo/skype: greg_casamento, aol: gjcasa
(240)274-9630 (Cell)
http://www.gnustep.org
http://heronsperch.blogspot.com