|
Scripting?
That is because Scripting Framework project?
Or Scripting Framework project because scripting?
I am very like IDispatch and IMoniker but not sure that
future it is scripting. May be, but when I think about
Borland C++ Builder, Delphi, Visual Basic, C# and even
UML I think that future it is visualization in
programming and languages. The man must see (in mind) what
he create as Plato said . The world of things, the
world of ideas...
|
|
|
|
|
My current experiences with scripting languages use another kind of *poof*.
"Dor säggsische Dialeggt eechnet sich wie keeen onderor für den Ausdrugg zäärdlischor Gefiehle."
sighist | Agile Programming | doxygen
|
|
|
|
|
|
Perl is still very good for advanced text parsing.
I know no language where You can write a C++ parser faster which
does e.g automatically insert trace statements at top of each
function with class/function name replacement in the trace text.
Alois Kraus
|
|
|
|
|
|
Sure you can do it in other languages. But the fastest way ist still
perl. The regular expressions are part of the language which
leads to the most compact syntax. And it is free and portable without
any fees.
|
|
|
|
|
Java is losing ground fast, and it never 'stole the punchline' from PERL.
Use of PERL is not all that common in the Windows world, but if you use any *Nix system, PERL is a savior!
For example, try writing a program to parse a UNIX log that tracks logins for an entire network in C#, C++, or Java and you will quickly find yourself focusing more in memory issues and locations of certain characters (and the # of lines of code for the program will be close to a hundred just to get it to run as a daemon). Write a script in PERL and it does all of that for you in about 10 lines of code.
"If you decide to become a software engineer, you are signing up to have a 1/2" piece of silicon tell you exactly how stupid you really are for 8 hours a day, 5 days a week"
|
|
|
|
|
Zac Howland wrote:
Use of PERL is not all that common in the Windows world, but if you use any *Nix system, PERL is a savior!
I beg to differ! We use Perl all the time in Windows environments. We have a build environment, much of it automated. Most, if not all, of that is Perl scripts.
I would venture to say that most sizeable operations that have the concept of a build (e.g., not just people compiling on their own machines, then cobbling together a web package or CD from that) will probably be making use of Perl.
If your nose runs and your feet smell, then you're built upside down.
|
|
|
|
|
I was not trying to say that it is never used in Windows development. I use it to do many different tasks. What I was getting at was that it is used much more in *Nix environments.
"If you decide to become a software engineer, you are signing up to have a 1/2" piece of silicon tell you exactly how stupid you really are for 8 hours a day, 5 days a week"
|
|
|
|
|
|
Nishant S wrote:
What I meant is that Java is an even bigger joke than Perl as a future language of importance.
Says who?
You obviously haven't been hanging around Java people. Put this same survey in a Java-centric site and see what happens.
Regards,
Alvaro
Hey! It compiles! Ship it.
|
|
|
|
|
There we go again
Don't think the language war will ever end
Happy programming,
Rakesh Rajan
|
|
|
|
|
Java will loose a lot of popularity on the windows environment because Microsoft has droped its compiler support for Java as a result of the problems with SUN and the MS JVM. Starting in 2004 MS will not be able to distribute its JVM and must distribute SUNs instead.
John
|
|
|
|
|
Nishant S wrote:
What I meant is that Java is an even bigger joke than Perl as a future language of importance.
While I agree that Java is a joke as a future language, PERL is not. It has not gotten the popularity in the Windows world that it has in the *Nix world, but give it time and some people will wonder why they try to write Melissa-style worms in VB instead of PERL :P
"If you decide to become a software engineer, you are signing up to have a 1/2" piece of silicon tell you exactly how stupid you really are for 8 hours a day, 5 days a week"
|
|
|
|
|
|
Not any more
Rakesh
|
|
|
|
|
|
|
I can tell you right now that the most important language in the Windows world for the next 5 years is C++. Microsoft has said it is writing the next 2 versions of Windows using Managed C++.
As far as application programming, the languages don't matter much when using the .Net architecture.
"If you decide to become a software engineer, you are signing up to have a 1/2" piece of silicon tell you exactly how stupid you really are for 8 hours a day, 5 days a week"
|
|
|
|
|
I agree with you.
Most of people participating in vote must be working with .NET or excited with .NET framework.
What ever b the result on this site... C++ will remain most important language in future.
Anand
The chosen one...
|
|
|
|
|
I think importance of C++ or C# are more a matter of domains where they would be of better use rather than raw power or that stuff.
It seems C++ is targetted towards the development of device-drivers and high-performance apps, whereas C# more towards the usual to advanced Windows APPs and of course with ASP.NET.
There's no doubt that C# lets u develop apps much simpler and faster than C++. So how could C++ be important here? And of course vice versa
Happy programming,
Rakesh Rajan
|
|
|
|
|
Rakesh Rajan wrote:
There's no doubt that C# lets u develop apps much simpler and faster than C++.
Isn't there?
|
|
|
|
|
In many respects, I don't think so...do u?
Rakesh Rajan
|
|
|
|
|
I use both C++ and C#, and generally I don't see much diferrence in productivity. In fact, I would say that C++ tends to be somewhat more productive language, especially when it comes to resource handling. And operator == in C# is definitelly brain damaged. In Java it means checking for identity, in C++ it is checking for equality, but in C# it can be any of those. You need to look at the documentation to find out.
One thing I really like about C# is the explicit control of method overriding (new and override keywords).
|
|
|
|
|
It seems you are talking in the microscopic sense. I was talking about the productivity in the outset - the big picture. When you think about general applications, using C# to code is usually faster than developing it in C++. The case is different in different domains though.
Rakesh Rajan
|
|
|
|