SCOUG-Programming Mailing List Archives

<< Previous Message <<

Date:	Sun, 28 Aug 2005 23:02:45 PDT7
From:	"Gregory W. Smith" <gsmith@well.com >
Reply-To:	scoug-programming@scoug.com
To:	scoug-programming@scoug.com
Subject:	SCOUG-Programming: What did I miss?

Content Type: text/plain

Lynn Maxson wrote:
> I did a google search on ViM, went to the downloads, selected
> OS/2, and perused the list of zip files in the directory. The
> minute I saw OS/2 as an option I knew I had missed some
> important piece of communication in the two meetings I
> missed.
>
> If VIM has already been ported, why would we demonstrate
> porting it to OS/2 unless we wanted to participate in the
> project to keep it up to the latest releases?

I chose ViM as a non-trivial example that works. If we want
to demonstrate the GNU compiler and the tools, why not choose
an example that works for someone else.

Or do we just install GCC and take off to a mega project like
Sea Monkey? After all, it was obvious that my initial GCC
install worked when I compiled cal.c and it worked.

If the tools work for the trivial case, then it is trivial
to use them on a major project......

> Why would we
> even be interested in porting latest releases if we were not
> using existing ports? I have no recollection of either Steven
> or Greg using VIM as the editor in their presentations. I
> thought Greg used something called JEdit. I forget if Steven
> even used one.
>
> I would appreciate if someone would fill me in on some missing
> pieces here.

True, my editor of choice was jEdit for the presentation, but
I could have just as easily typed "vi somefile.txt" in a command
window. Depending on the path varialble, I would have invoked
either VIM or the fine version of VI that Watcom installed on
my OS/2 box. (Right now I am using VIM on my Windoze box to
edit this message.)

My goal was to use a non-trivial example (about 1000 pages of
code) to show how the GCC tools work. Don't let the choice of
example distract you from the real objective: showing how the
tools work. Like it or not, GCC and the GNU tools are what most
developers use in the open source world. Of course, some vendors
will do ports of open source projects with their own tools. The
Intel or Sun compilers, for example, are quite popular with some
people who want highly opimized code for x86 or Sparc processors.

The Watcom compiler is not that big in the open source world yet.
We will get around to making it work on some major open source
project eventually. Until then, someone might start with a more
lightweight example like cal.c. (Tee hee... Throw out the bait
and let someone bite. For those that don't remember, the Watcom
compiler choked on cal.c.)
--
Gregory W. Smith (WD9GAY) gsmith@well.com

=====================================================

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".

=====================================================

Return to [ 28 | August | 2005 ]

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.