The message below is being cross-posted from the LogoForum. Please
reply here at comp.lang.logo and it will be cross-posted back to the
LogoForum. The original author of this message is
laske_lionel@[EMAIL PROTECTED]
In LogoForum@[EMAIL PROTECTED]
"jotape1960" <jotape1960@[EMAIL PROTECTED]
> wrote:
>
>
> My question is: if that thing ".NET Framework" is very important
but
> it isn't self included with Windows (at least my XP pro version
> needs a 20MB extra downloaded to it), WHY TO MAKE A LOGO COMPILER
> WITH SOMETHING NOT INCLUDED IN THE STANDARD WINDOWS VERSION?
>
>
Of course, you're right but, except if your name is Pavel ;-) it's
really hard to write a Logo compiler "from scratch" ("from scratch"
means using only something included in a standard windows version).
..NET Framework help me to write lot of cool Liogo stuff:
- Native code generation: no need to write assembly,
- Localization: no need to write a local resource manager,
- OLE Automation: no need to write most of COM stuff,
- Vista support: WPF is natively callable from .NET,
- Interoperability: it's really easy to call .NET code from Liogo,
- Multi-threading: it's a native feature of .NET,
- ...
There are Pros and Cons to use .NET as developpement platform for
Liogo but I must confess that without .NET, I probably didn't take
time to write a Logo compiler ! Only a "superman" like Pavel can do
this spending several years to write the better Logo compiler:
Lhogho !
By the way, .NET Framework becomes really a part of Windows operating
system. You can't use Windows Update or install a service pack for
Windows without getting .NET Framework. Vista for example comes
natively with .NET Framework 2.0 and .NET Framework 3.0.
Lionel.
__._,_.___
LogoForum messages are archived at:
http://groups.yahoo.com/group/LogoForum
|
