Thread overview
WTL?
Apr 20, 2003
Matthew Wilson
Apr 21, 2003
Matthew Wilson
May 10, 2003
Matthew Wilson
April 20, 2003
So, what about compartibility DMC with WTL? As I see, DMC is strong enougth to compile all the WTL sources. Do you plan add an ability working DMC with WTL? It's very intersting question.


April 20, 2003
It's certainly something on my todo list, but it's a long list. :(

"Michail Semijonovskich" <Michail_member@pathlink.com> wrote in message news:b7uc2d$p0n$1@digitaldaemon.com...
> So, what about compartibility DMC with WTL? As I see, DMC is strong
enougth to
> compile all the WTL sources. Do you plan add an ability working DMC with
WTL?
> It's very intersting question.
>
>


April 21, 2003
>It's certainly something on my todo list, but it's a long list. :(
AFAIK current DMC release (.33) don't support template template parameters, but WTL actively using it. About 2 weeks ago I tryed to rewrite all the WTL sources for DMC - without any success. Many people using WTL in their job, and it's sufficient interesting use it with DMC. Any ideas ? ;)


April 21, 2003
As I said, I'd love to attack this problem, but am out of time at the moment.

That's not to say that we shouldn't take some little steps. Can you suggest a simple example, perhaps one of the WTL samples, that illustrates the problem, which will help us boil the issues down for Walter to effect a change?

"Michail Semijonovskich" <Michail_member@pathlink.com> wrote in message news:b7vmib$1jj1$1@digitaldaemon.com...
> >It's certainly something on my todo list, but it's a long list. :(
> AFAIK current DMC release (.33) don't support template template
parameters, but
> WTL actively using it. About 2 weeks ago I tryed to rewrite all the WTL
sources
> for DMC - without any success. Many people using WTL in their job, and
it's
> sufficient interesting use it with DMC. Any ideas ? ;)
>
>



April 22, 2003
>As I said, I'd love to attack this problem, but am out of time at the moment.
>
>That's not to say that we shouldn't take some little steps. Can you suggest a simple example, perhaps one of the WTL samples, that illustrates the problem, which will help us boil the issues down for Walter to effect a change?

Ok. There are (at least, as I see :) 2 chief problems :
1 - now, current DMC release 8.33.13n don't support template template parameters
(I told you). For example, routine WTL code snippet :
template<typename C, template<C> class B> i.e.

template<CWindow, class T = CWindowImpl<CWindow,CFrameWinTraits> >
class CMyCoolWindow : public T
{
};
2 - headache with ATL versions - some WTL code, perfectrly working with ATL3.x
crushes on ATL7.x (by MS design ).
So, second problem isn't such significant as first.

Moreover, th inners of WTL is so close do ATL that disctinct it to 2 different libraries too hard.


May 10, 2003
Have been messing around with some WTL recently, and plan to have a go at DMC++ support very soon.

I'll post here again to let you know how I'm going.

FYI, to enable Metrowerks compilation (CodeWarrior v8.0) took only 1 hour of
WTL (7.0) header edits.



"Michail Semijonovskich" <Michail_member@pathlink.com> wrote in message news:b82d0c$cvd$1@digitaldaemon.com...
> >As I said, I'd love to attack this problem, but am out of time at the moment.
> >
> >That's not to say that we shouldn't take some little steps. Can you
suggest
> >a simple example, perhaps one of the WTL samples, that illustrates the problem, which will help us boil the issues down for Walter to effect a change?
>
> Ok. There are (at least, as I see :) 2 chief problems :
> 1 - now, current DMC release 8.33.13n don't support template template
parameters
> (I told you). For example, routine WTL code snippet :
> template<typename C, template<C> class B> i.e.
>
> template<CWindow, class T = CWindowImpl<CWindow,CFrameWinTraits> >
> class CMyCoolWindow : public T
> {
> };
> 2 - headache with ATL versions - some WTL code, perfectrly working with
ATL3.x
> crushes on ATL7.x (by MS design ).
> So, second problem isn't such significant as first.
>
> Moreover, th inners of WTL is so close do ATL that disctinct it to 2
different
> libraries too hard.
>
>