i2phd wrote:
> --- In [email protected], "drmail377" <[EMAIL PROTECTED]> wrote:
>
>> Alberto, which "free" piece of software are you referring to? Turbo
>> C++ 2006 Explorer is available but requires the nightmarish .NET
>> framework. C++ Compiler 5.5 is available and will work at Win2K
>> level after much configuration so I probably can be coaxed to work
>> with WinXP; but it is pretty dated. That's it aside from truly
>> ancient stuff such as Turbo C and Turbo C++
>>
>
> Well, somebody found the Turbo C++ 2006 Explorer
> (http://cc.codegear.com/item/24724 )
> available free on the Embarcadero pages. I haven't tested nor used it,
> and from what it can be read there, yes, it uses the .NET framework,
> but just for compiling. The compiled code, if it behaves like the full
> blown compiler, does need the .NET to run. While .NET may be huge and
> ugly, once you have installed it, you forget it, usually it doesn't
> step into your toes. I had to install it for the CodeGear Rad Studio
> compiler, but then I haven't heard from it since...
>
> 73 Alberto I2PHD
>
For what it is worth ... I have Borland C++Builder6 (Personal) (Cripple
ware) and it will compile and link SDRadio I haven't tried WinRad yet
... the 500 pound gorilla in the room for using non borland compilers
seems to be the Borland "PACKAGE" concept ... Dev-Cpp compiler chokes on
the "PACKAGE" stuff but seems to be ok with most all else ... haven't
got to the link stage yet ... the Borland disk says the "PACKAGE" is a
key word ... another book on Builderx says it is a MACRO ... The Borland
"PACKAGE" seems to be the Borlands method to block any (Non Borland)
compiler from working ... I would view MS MFC and Borland PACKAGE as
being the killer functions that makes their code useless on other
compilers ...
Jim KI6MZ
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>
>
>
