> Michael Van Canneyt wrote:
> > If Lazarus puts pascal as a language on the map again, it's name is
> > VERY well chosen indeed, as Lazarus rose again from the grave !!
>
> A RAD/IDE should not lock itself into one language only, but should rather
> strive to be compiler/language independent. Implementing this with the FPC
> would probably be proof enough that Pascal isn't dead.
This is very very hard to do. It could be done with a plug-in system - if you
unload the
Pascal parser then the IDE is no longer a Pascal IDE but now a C++ ide. For
example,
CodeTools/CodeInsight needs a parser to parse the text in the IDE window. You'd
have to be
able to unplug the Pascal CodeTools parser and plug another language CodeTools
parser in.
But this is much more man-power required than just focusing on one language.
Look at Vim
and Emacs - they are supposedly the tools which are supposed to handle multiple
languages.
But what good are they? Don't we have to build Emacs plug-ins in Lisp? Why not
Emacs
plug-ins in Pascal?
There is always some language favor it seems. And Eclipse? It is favored for
Java - even
though it's supposed to be a multi language development tool. And as for
BDS2006? It only
handles C++/Pascal but why not Lisp, Perl, PHP? If Borland doesn't have the man
power it
is very slim chance that a small open source project can handle such a task.
And then we
have to beg the question - where do we draw the line? Which languages do we
skip? Perl?
Python? TCL? Algol? Right now it is easy to draw the line - Pascal. It's a very
easy line
to draw. If you let this line slip - it becomes very hard to draw. Where do you
stop? How
many languages are on the chocolate bar packaging before the chocolate bar
package becomes
so flooded with languages and so lacking of actual chocolate bar?
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
