OpenEuphoria

RE: win32lib v0.57.7

• Posted by Derek Parnell <Derek.Parnell at SYD.RABOBANK.COM> Jun 12, 2002
• 521 views

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01C2129E.EB2F6600
 charset=iso-8859-1

Yes to both questions.

> -----Original Message-----
> From: Juergen Luethje [mailto:jluethje at gmx.de]
> Sent: Thursday, 13 June 2002 15:27
> To: EUforum
> Subject: Re: win32lib v0.57.7
> 
> 
> 
> Hello Dan,
> 
> you wrote:
> 
> > Juergen,
> 
> > But isn't this how it's being done now?
> 
> I don't know.
> 
> > On the RDS site is the latest *official* version of 
> Win32Lib, v 0.55.1,
> 
> There is no resource leakage or other known serious bug in 
> the "official"
> version?
> 
> > and at Derek's site is the latest "bleeding edge" version, 0.57.7,
> > for which he asks for help debugging.
> 
> And it is planned, that this will become the "official" version, only
> without serious bugs like resource leakages?
> 
> > Only problem I see with this is that we find the features of 57 so
> > interesting we start to use it before it's stable & finished!  :)
> 
> If the answers to both questions above is "yes", than I agree 
> with you.
> 
> > Dan Moyer
> 
> Best regards,
>    Juergen
> 
> 
> 
> > ----- Original Message -----
> > From: "Juergen Luethje" <jluethje at gmx.de>
> > To: "EUforum" <EUforum at topica.com>
> > Sent: Wednesday, June 12, 2002 8:03 AM
> > Subject: Re: win32lib v0.57.7
> 
> <snip>
> 
> >> How about maintaining two different versions of Win32Lib:
> >> one conservative version ("conservative" in it's best sense),
> >> let's say "Win32Lib classic", and one experimental version,
> >> let's say "Win32Lib future".
> >>
> >> "Win32Lib classic" should be as stable and reliable as possible,
> >> "Win32Lib future" could be used to experiment with cool new
> >> features and new controls.
> >> New features will only be taken over from "Win32Lib future" to
> >> "Win32Lib classic" after they didn't cause any problem for
> >> let's say 3 months.
> >>
> >> Doing it this way will be more work, but one person could maintain
> >> "Win32Lib classic", and someone else could maintain 
> "Win32Lib future".
> >> In this case, both should work close together, of course.
> >>
> >> Just some ideas.
> >> Best regards,
> >>    Juergen
> 
> 
> 
> 

==================================================================
De informatie opgenomen in dit bericht kan vertrouwelijk zijn en 
is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht 
onterecht ontvangt wordt u verzocht de inhoud niet te gebruiken en 
de afzender direct te informeren door het bericht te retourneren. 
==================================================================
The information contained in this message may be confidential 
and is intended to be exclusively for the addressee. Should you 
receive this message unintentionally, please do not use the contents 
herein and notify the sender immediately by return e-mail.


==================================================================

------_=_NextPart_000_01C2129E.EB2F6600
Content-Type: application/ms-tnef