SCOUG-Programming Mailing List Archives
Return to [ 31 |
January |
2005 ]
Content Type: text/plain
February is a mite more reasonable in offering breathing
space for preparation. This month we will continue with
presentations by Greg Smith and Sheridan Georg on Python.
As I mentioned before they have set a initial level which we
should make every effort to match or exceed in the other
explorations ahead of us.
For your reading pleasure (?) I submit the following:
"Extensible Programming for the 21st Century
Is an open, more flexible programming environment just
around the corner?
http://www.acmqueue.com/modules.php?name=Content&pa=sh
owpage&pid=247"
The following is from the beginning of this article:
"This article argues that next-generation programming
systems can accomplish this by combining three specific
technologies:
-> Compilers, linkers, debuggers, and other tools that are
frameworks for plug-ins, rather than monolithic applications.
-> Programming languages that allow programmers to extend
their syntax.
-> Programs that are stored as XML documents, so
programmers can represent and process data and meta-data
uniformly.
These innovations will likely change programming as
profoundly as structured languages did in the 1970s, objects in
the 1980s, and components and reflection in the 1990s. To see
why, we must first examine the shortcomings of the systems
that programmers use today. Let's begin with two of the most
popular: the Unix command line and Microsoft's COM
(component object model)."
The author and I would probably differ on the details, but
have the same concept in mind. I will pursue it with him.
Also I had need to have a Windows-based C compiler to do
some contract work for a client. I initially tried to use the
IBM VisualAge C/C++ 3.6.5 compiler, but discovered that the
Windows version (which is no longer supported) has a
software failure in the autoplay: it fails to initialize properly.
Rather than fight this with IBM I opted for the Watcom C
compiler. Unfortunately I overlooked an option during the
install process which led to having all the components on the
startup menu. I ended up uninstalling it, promising to pay
more attention on re-installing it.
I also installed it under OS/2. I find it an impressive package.
Maybe we can include a presentation on it with some samples
in the future.
You can do me a favor by letting me know if you can access
BMTMicro. I can't. I had somehow lost my copies of Filestar/2
and Unimaint. So I fugured just to order the latest releases.
My error. My cost.
Nevertheless I ended up in correspondence with Jim Read the
author of both products who has a database which indicated
my purchases. He assisted me in getting the latest releases of
the products as well as several procedures to apply in their
use. One of these reduced my OS2SYS.INI file by nearly 200k
bytes. My OS2.INI file is some 1.9MB. I need to bring it down
to size.
My point in all this is that the OS/2 community remains with
some viable ISPs like Innotek, Bill Richter (Guiffy), Jan van
Wijk(DFSee) and Jim Read (FileStar/2 and Unimaint). I would
hope that eventually SCOUG will join that list. I know that we
don't lack for talent or interest.
=====================================================
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
"rollin@scoug.com".
=====================================================
Return to [ 31 |
January |
2005 ]
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.
| 
