It looks rather a rewrite than a simple port.
What does gtwvw do?

Brgds,
Viktor

On Wed, Feb 11, 2009 at 12:54 PM, Massimo Belgrano <mbelgr...@deltain.it>wrote:

> Another request that is not for 1.1:
>
> will somebody port gtwvw as harbour contrib?
> afaik Budjanto not have free time and is blocked from new gt
> implementation (a year ago)
> I remember that Przemek have advised ron but gtwvw is still unported to new
> gt
>
>
> 2009/2/10 Viktor Szakáts <harbour...@syenar.hu>:
> > Hi everyone,
> > Who has what pending items (fixes, new development, TODOs)
> > before the 1.1 release?
> > This is my list for 1.1:
> > - gtwvt: add HB_GTI_BOXCP support to change hard-wired "EN" CP.
> > - core: HB_MD5() incompatible modification.
> > - contrib: openssl GNU-make detection.
> > - core: hb_snprintf() switch?
> > - xhb, hbwhat: .prg level MT issues.
> > - hbct .c level MT issues in files.c. (per thread cargo holder may help?)
> > - gtwvg: reported GPF with MSVC, possible problems with other compilers,
> > AMD64 mode and WinCE.
> >   (build stopper !)
> > - core: Copy DISKSPACE() Watcom/CEGCC logic to HB_DISKSPACE().
> > - core: hb_regexMatch()'s 3rd parameter has a double meaning.
> > - hbct: SetFDaTi() duplicated logic.
> > - hbct: hb_fsFindClose() at app exit.
> > - New dbCreateTemp( <cAlias>, <aStruct>, <cRDD>, <cDelimArg>,
> <nConnection>
> > ) -> <lSuccess>
> > - Platform builds and tests.
> >
> > Post 1.1:
> > - Type cleanup.
> > - hbole, hbwin, hbwhat consolidation, cleanup (can be started anytime).
> > Brgds,
> > Viktor
> >
> > _______________________________________________
> > Harbour mailing list
> > Harbour@harbour-project.org
> > http://lists.harbour-project.org/mailman/listinfo/harbour
> >
> >
> _______________________________________________
> Harbour mailing list
> Harbour@harbour-project.org
> http://lists.harbour-project.org/mailman/listinfo/harbour
>
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to