said:
>I have not looked at the Watcom IDE, but I am fairly certain that it is
>NOT based on VIM.
This is true. Watcom includes an implementation of an editor that is
somewhat like the unix VI. This is also the default editor used by the
IDE and, of course, this can be overridden. Bindings exist for seamless
access to EPM and a couple of other editors.
The IDE is just an application that knows how to build parameter files and
invoke some of the other Watcom tools.
Watcom differs from most other toolchains in that it is pretty much self
contained. In addition to the compiler and linker, it includes
implementations of lexx an yacc and other tools needed to build the tool
chain.
>Well, jEdit is about 2000 pages of Java source code. The build process
>does not use a separate make utility.
Actually, not unexpectedly, it does. A quick Google for
building jedit
finds
ant -Dant.full.path=C:/Java/apache-ant-1.6.2/bin/ant
build Buildfile: build.xml
Ant is essentially make for Java. For Java, there's also bake and its
bakefiles. Some of the links suggest that orginally jEdit was build with
POMs (plain old makefiles).
>Also, the package naming
>conventions are reflected in how you organize the source tree.
This is a requirement of the Java. I guess one could build a class loader
with different rules, but I don't see any useful reason for this.
>> Let us be clear on this point. Every IDE begins with an editor.
This I would disagree with. It would be more correct to say that every
IDE offers some sort of access to one or more editors.
>> The most ambitious IDE underway, Eclipse, begins with an
>> editor. The Watcom IDE, for example, offers access to all
>> functions through the editor interface.
Lynn, have you actually used the Watcom IDE?
>So an alternate approach might be to develop an Eclipse plug-in to add
>the data store with automatic invocation of the GCC or Watcom compilers.
This, at least, would avoid a lot of useless reinvention of existing
technology.
>OK, so we are starting with 2000 pages of Java code for the editor. The
>compilers are written in C.
I wouldn't worry too much about an actual project schedule. I don't
believe anyone actually intends to code any of this.
Steven
--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.67 #10183 Warp4.something/14.100c_W4
www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST)
----------------------------------------------------------------------
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-programming".
For problems, contact the list owner at
"postmaster@scoug.com".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 14 |
January |
2006 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
