Re: Compiling code at runtime
From: Paul Schmidt (wogsterca_at_yahoo.ca)
Date: 05/26/04
- Next message: Eric Sosman: "Re: Java Interview Questions: Am I Being Too Difficult?"
- Previous message: Snurrberget: "Re: XML Parser"
- In reply to: Jo Vermeulen: "Re: Compiling code at runtime"
- Next in thread: Jo Vermeulen: "Re: Compiling code at runtime"
- Reply: Jo Vermeulen: "Re: Compiling code at runtime"
- Reply: Craig Hennessey: "Re: Compiling code at runtime"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 26 May 2004 10:29:05 -0400
Jo Vermeulen wrote:
> Op Tue, 25 May 2004 11:47:21 -0400, schreef Paul Schmidt:
>
>
>>C# and VB.Net are NOT programming languages, real or otherwise, they are
>>Microsoft specific implementations of languages.
>
>
> Could you explain this further?
Sure, C# was invented by Microsoft, as a Java like system, because Sun,
didn't like the concept that when using a Microsoft compiler VisualJ I
think they called it, produced code that would only run on Windows,
because half the code depended on Microsoft hacks. When Microsoft tried
this, Sun said, see you in court, and you can't call your product Java,
until the court says you can. Microsoft lost, in the mean time, they
hacked some more and called the result C#.
VB isn't a language either, the language behind it is BASIC, but it's
been hacked so much over the years, adding Pascal like features
actually, that even the inventors wouldn't recognize VB as BASIC,
however that does't make it a separate language.
>
> For your information, I write C# programs on Mono
> (http://www.go-mono.com/). .NET is standardized you know, unlike Java. The
> biggest disadvantage of Java is in my opinion the fact that it is
> controlled by one company (Sun namely).
>
> I'm certainly not a Microsoft zealot (on the contrary! I'm a GNU/Linux
> user and I favor the concept of free software), but I quite like
> their .NET platform, just as a like Java. Both have their respective
> advantages and disadvantages.
>
.NET is not a standard, no matter how much Microsoft's prophet William
Gates V3.0 says so. There is no standard called .Net, as identified by
any standards organization (like ISO or ANSI). Mono is really a tail
chasing a dog, as they get close, Microsoft hacks on, and changes stuff.
Java isn't a standard either, for the same reason, no standards
organization has published a Java standard.
>
>>Compiling at run-time defeats the purpose of using a compiler in the
>>first place, there are other languages like Perl, PHP, Javascript and
>>TCL that are interpretive, that make it easy to run changes on the fly.
>> However one really needs to know why you want to compile at run time.
>
>
> For easy extensibility, and doing things at runtime, without recompiling
> the entire code. But I still require a powerful programming language,
> because the things users might add to the functionality are not
> really trivial programming tasks.
>
Just because a language is compiled, doesn't make it more powerful then
one that is interpreted, I still think you would be better off using TCL
to extend your software, it's fairly easy to learn, and was designed to
work with other programming languages to do this kind of thing.
Paul
- Next message: Eric Sosman: "Re: Java Interview Questions: Am I Being Too Difficult?"
- Previous message: Snurrberget: "Re: XML Parser"
- In reply to: Jo Vermeulen: "Re: Compiling code at runtime"
- Next in thread: Jo Vermeulen: "Re: Compiling code at runtime"
- Reply: Jo Vermeulen: "Re: Compiling code at runtime"
- Reply: Craig Hennessey: "Re: Compiling code at runtime"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|