Is there any plans to support mingw (or gcc) with this library?
jmccay

Well, no plans, because it already does. ;-)

Just about all the COMSTL components work with GCC 3.2 or later.

What specifically did you have in mind? I'd be happy to help if you have a specific problem/need.

Cheers

Matthew


"Joseph McCay" <joemccay@gmail.com> wrote in message news:e0shmn$27a3$1@digitaldaemon.com...
>    Is there any plans to support mingw (or gcc) with this library?
> jmccay

   I was looking into ways I could write/develop COM components using mingw and still have them callable/useable from Visual C++.  Also, is there a tutorial on using the comstl library or atleast some sample files?   Thanks a lot.

Joe McCay

Matthew wrote:
> Well, no plans, because it already does. ;-)
> 
> Just about all the COMSTL components work with GCC 3.2 or later.
> 
> What specifically did you have in mind? I'd be happy to help if you have a specific problem/need.
> 
> Cheers
> 
> Matthew
> 
> 
> "Joseph McCay" <joemccay@gmail.com> wrote in message news:e0shmn$27a3$1@digitaldaemon.com...
> 
>>   Is there any plans to support mingw (or gcc) with this library?
>>jmccay 
> 
> 
> 

I see.

So far, COMSTL contains more stuff for working with COM components than writing them.

In the mid 90s I developed a set of C++ template libraries for writing COM components, which are still used within some of my company's (Synesis Software) core libraries, but since ATL came along I've primarily used it for writing COM components (hence ATLSTL). If you definitely want to write COM components without using VC++/ATL  - note other compilers, incl Digital Mars (free), Borland (some vers free), CodeWarrior, Intel, support ATL - then you're in for some interesting times.

If you're really keen, I'd be happy to have a look at working some of the Synesis components into a decent shape and adding them to COMSTL. It'd take some work on both our parts (I'm assuming you'd be a willing tester) - which I'm a bit tight on at the moment - but you'd be sure to get a really deep understanding of COM. (Although COM's supposedly no longer a viable technology, it pervades Windows and will continue to do so for a long while. And, because it's so challenging, anything else you'd ever do afterwards seems trivial. <g>)

(btw, COM is a binary standard. So (except where someone deliberately subverts the COM type system) it is always possible use a component built using one compiler/language with another.)

As for tutorials, sigh, this is where the libraries are really poor. I've been trying to find time to write some for nearly four years, but time's very short. If you were willing, we could enter into an exchange, whereby you request a tutorial on a given component, and I'll write one, and so on. That may be a way for me to take small bites out of what is now a cookie bigger than Shrek 2's gingerbread man. ;-)

HTH

Cheers

Matthew

"Joseph McCay" <joemccay@gmail.com> wrote in message news:e0v01a$2qng$1@digitaldaemon.com...
>    I was looking into ways I could write/develop COM components using
> mingw and still have them callable/useable from Visual C++.  Also, is
> there a tutorial on using the comstl library or atleast some sample files?
> Thanks a lot.
>
> Joe McCay
>
> Matthew wrote:
>> Well, no plans, because it already does. ;-)
>>
>> Just about all the COMSTL components work with GCC 3.2 or later.
>>
>> What specifically did you have in mind? I'd be happy to help if you have a specific problem/need.
>>
>> Cheers
>>
>> Matthew
>>
>>
>> "Joseph McCay" <joemccay@gmail.com> wrote in message news:e0shmn$27a3$1@digitaldaemon.com...
>>
>>>   Is there any plans to support mingw (or gcc) with this library?
>>>jmccay
>>
>> 

Thank you for the reply.  I too am busy these days.  I learned com programming a while ago, but as with most things you don't use it gets rusty.  I appreciate your help, and when I actually get to working with COM, I will definately come back and look at COMSTL.  It looks like a great idea, and keep up the good work.

   As for your other suggestions, I don't have much time right now. Sorry.  I really do appreciate you responces.

joe


Matthew wrote:
> I see.
> 
> So far, COMSTL contains more stuff for working with COM components than writing them.
> 
> In the mid 90s I developed a set of C++ template libraries for writing COM components, which are still used within some of my company's (Synesis Software) core libraries, but since ATL came along I've primarily used it for writing COM components (hence ATLSTL). If you definitely want to write COM components without using VC++/ATL  - note other compilers, incl Digital Mars (free), Borland (some vers free), CodeWarrior, Intel, support ATL - then you're in for some interesting times.
> 
> If you're really keen, I'd be happy to have a look at working some of the Synesis components into a decent shape and adding them to COMSTL. It'd take some work on both our parts (I'm assuming you'd be a willing tester) - which I'm a bit tight on at the moment - but you'd be sure to get a really deep understanding of COM. (Although COM's supposedly no longer a viable technology, it pervades Windows and will continue to do so for a long while. And, because it's so challenging, anything else you'd ever do afterwards seems trivial. <g>)
> 
> (btw, COM is a binary standard. So (except where someone deliberately subverts the COM type system) it is always possible use a component built using one compiler/language with another.)
> 
> As for tutorials, sigh, this is where the libraries are really poor. I've been trying to find time to write some for nearly four years, but time's very short. If you were willing, we could enter into an exchange, whereby you request a tutorial on a given component, and I'll write one, and so on. That may be a way for me to take small bites out of what is now a cookie bigger than Shrek 2's gingerbread man. ;-)
> 
> HTH
> 
> Cheers
> 
> Matthew
> 
> "Joseph McCay" <joemccay@gmail.com> wrote in message news:e0v01a$2qng$1@digitaldaemon.com...
> 
>>   I was looking into ways I could write/develop COM components using 
>>mingw and still have them callable/useable from Visual C++.  Also, is there a tutorial on using the comstl library or atleast some sample files? Thanks a lot.
>>
>>Joe McCay
>>
>>Matthew wrote:
>>
>>>Well, no plans, because it already does. ;-)
>>>
>>>Just about all the COMSTL components work with GCC 3.2 or later.
>>>
>>>What specifically did you have in mind? I'd be happy to help if you have a specific problem/need.
>>>
>>>Cheers
>>>
>>>Matthew
>>>
>>>
>>>"Joseph McCay" <joemccay@gmail.com> wrote in message news:e0shmn$27a3$1@digitaldaemon.com...
>>>
>>>
>>>>  Is there any plans to support mingw (or gcc) with this library?
>>>>jmccay
>>>
>>>
> 

No worries. I am rather too busy myself at the mo, so your position is something of a relief.

Please feel free to post again if/when you need any help on COMSTL or any other of my libs.

Cheers

Matthew

"Joseph McCay" <joemccay@gmail.com> wrote in message news:e1er86$qbo$1@digitaldaemon.com...
> Thank you for the reply.  I too am busy these days.  I learned com programming a while ago, but as with most things you don't use it gets rusty.  I appreciate your help, and when I actually get to working with COM, I will definately come back and look at COMSTL.  It looks like a great idea, and keep up the good work.
>
>    As for your other suggestions, I don't have much time right now. Sorry.
> I really do appreciate you responces.
>
> joe
>
>
> Matthew wrote:
>> I see.
>>
>> So far, COMSTL contains more stuff for working with COM components than writing them.
>>
>> In the mid 90s I developed a set of C++ template libraries for writing COM components, which are still used within some of my company's (Synesis Software) core libraries, but since ATL came along I've primarily used it for writing COM components (hence ATLSTL). If you definitely want to write COM components without using VC++/ATL  - note other compilers, incl Digital Mars (free), Borland (some vers free), CodeWarrior, Intel, support ATL - then you're in for some interesting times.
>>
>> If you're really keen, I'd be happy to have a look at working some of the Synesis components into a decent shape and adding them to COMSTL. It'd take some work on both our parts (I'm assuming you'd be a willing tester) - which I'm a bit tight on at the moment - but you'd be sure to get a really deep understanding of COM. (Although COM's supposedly no longer a viable technology, it pervades Windows and will continue to do so for a long while. And, because it's so challenging, anything else you'd ever do afterwards seems trivial. <g>)
>>
>> (btw, COM is a binary standard. So (except where someone deliberately subverts the COM type system) it is always possible use a component built using one compiler/language with another.)
>>
>> As for tutorials, sigh, this is where the libraries are really poor. I've been trying to find time to write some for nearly four years, but time's very short. If you were willing, we could enter into an exchange, whereby you request a tutorial on a given component, and I'll write one, and so on. That may be a way for me to take small bites out of what is now a cookie bigger than Shrek 2's gingerbread man. ;-)
>>
>> HTH
>>
>> Cheers
>>
>> Matthew
>>
>> "Joseph McCay" <joemccay@gmail.com> wrote in message news:e0v01a$2qng$1@digitaldaemon.com...
>>
>>>   I was looking into ways I could write/develop COM components using
>>> mingw and still have them callable/useable from Visual C++.  Also, is
>>> there a tutorial on using the comstl library or atleast some sample
>>> files? Thanks a lot.
>>>
>>>Joe McCay
>>>
>>>Matthew wrote:
>>>
>>>>Well, no plans, because it already does. ;-)
>>>>
>>>>Just about all the COMSTL components work with GCC 3.2 or later.
>>>>
>>>>What specifically did you have in mind? I'd be happy to help if you have a specific problem/need.
>>>>
>>>>Cheers
>>>>
>>>>Matthew
>>>>
>>>>
>>>>"Joseph McCay" <joemccay@gmail.com> wrote in message news:e0shmn$27a3$1@digitaldaemon.com...
>>>>
>>>>
>>>>>  Is there any plans to support mingw (or gcc) with this library?
>>>>>jmccay
>>>>
>>>>
>>