Hello, GPC folks,
the Essener Linux User Group (ELUG) is organising a workshop on
GNU Pascal:
Weekend 29./30. July 2000
Villa Vogelsang, Antonienallee 1
45279 Essen Steele-Horst, Germany
http://www.villa-vogelsang.de ("Linux Hotel")
The primary language will be German. (However the speaker (myself;-)
and probably most of the participants can also speak English.)
Details will be published (in German) on the ELUG web site
(http://www.elug.de). For even more details, please ask the
Essener Linux User Group on their mailing list <elug(a)elug.de>
or Anja Drewitz <anja(a)drewitz.de> who organises the event.
See you,
Peter
--
http://home.pages.de/~Peter.Gerwinski/ - G-N-U GmbH: http://www.g-n-u.de
Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - gpc-19990118
GnuPG key fingerprint: 9E7C 0FC4 8A62 5536 1730 A932 9834 65DB 2143 9422
keys: http://www.gerwinski.de/pubkeys/ - AntiSpam: http://spam.abuse.net
Hello, folks!
This is the announcement of a new alpha version of GPC:
gpc-20000705
We also have set up a CVS server where you can always check out the
current development snapshot. Alpha snapshots are now going to be
released much more frequently.
At the same time we have updated the GPC WWW pages. They now contain
the GPC documentation in HTML, DVI and PS format which are updated
automatically with the GPC source.
The instructions below are an extract from the new `INSTALL' file.
For a list of new features in this release, see the section `news'
on the GPC WWW pages and/or in the GPC documentation. For fixed
bugs, see the GPC TODO list at the same places.
Have fun,
the GNU Pascal development team
Where and what to download
==========================
The master server for GNU Pascal is
`agnes.dida.physik.uni-essen.de'. Official and beta releases of the
compiler with sources and binaries for many platforms as well as other
GNU Pascal related files can be found in
`ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/'
You can find binary distributions for many platforms in the
subdirectory `binary'. The archive files are named
`gpc-VERSION.PLATFORM.EXTENSION' - for example
`gpc-2.1.alpha-unknown-linux-gnu.tar.gz' for GPC version 2.1 on an
Alpha workstation running the Linux kernel with GNU C Library, or
`gpc-20000616.i586-pc-djgppv201.zip' for GPC version 20000616 on an
i586 PC running DOS with DJGPP version 2.01.
After you have downloaded the correct archive file for your
platform, please read the installation notes on how to install such a
binary distribution.
If you are running Dos or MS Windows, you will need additional tools
- see "What else to download and where" below.
Current snapshots
-----------------
GNU Pascal is subject to steady development. You can download the
current snapshot (source only, use at your own risk) via anonymous FTP
from:
`ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/alpha/'
or via anonymous CVS from:
CVS root: :pserver:anonymous@agnes.dida.physik.uni-essen.de:/usr/local/cvsroot
Password: anonymous
Command: checkout gpc
Please read the installation notes on how to compile the source from
a distribution or a CVS checkout.
Compiling GPC
=============
The preferred way to distribute GNU software is distribution of the
source code. However, it can be a non-trivial exercise to build GNU
Pascal on some non-Unix systems, so we also provide ready-to-run
binaries for a number of platforms. (See above for how to install a
binary distribution.)
GPC is based on the GNU Compiler Collection, GNU CC or GCC. You will
need the GCC sources to build it. It must be the same version as the one
GPC is implemented with - `version 2.95.x' as of this writing. Although
you need GCC to build the GNU Pascal compiler, you don't need GCC to
compile Pascal programs once GNU Pascal is installed. (However, using
certain libraries will require compiling C wrappers, so it is a good
idea to install the C compiler as well.)
Because GNU Pascal shares its back-end with GCC, it should run on any
system supported by GCC. A full list of platforms supported by GCC can
be found in the GCC installation instructions.
The GCC source can be obtained from any mirror of the GNU FTP site,
`ftp://ftp.gnu.org/gnu/gcc/'. The "core" distribution is sufficient for
GPC.
Here is the generic procedure for installing GNU Pascal on a Unix
system. See below for extra information needed to install GPC on
DOS-like platforms.
1. Checking the prerequisites
Make sure that GNU make is installed. (In the following, we will
simply speak of `make' when invoking GNU make; you might need to
call `gmake' instead.)
For extracting the example programs from the documentation to the
`doc/docdemos' directory a non-crippled `sed' is needed. GNU sed
is known to work.
If you have checked out the GPC source from CVS, you will have to
rebuild most derived files, so you will need additional tools:
`bison', `flex', `makeinfo', `gperf', and `autoconf'. Make sure
that these are installed.
If you want to build the GPC WWW pages you will also need:
`texi2html' version 1.61 (older versions are missing some needed
features; newer versions suffer from a bug), `texi2dvi', TeX,
`gzip', `dvips', `dviselect', and `dviconcat'.
If you run into trouble during the installation process, please
check whether you are using outdated versions of the required
utilities and upgrade if necessary.
The GNU versions of the packages above are available from
the GNU FTP server (ftp://ftp.gnu.org) or any of its mirrors.
Package PACKAGE is usually located in the directory `gnu/PACKAGE'.
2. Unpacking the source
From a directory of your choice (e.g. `/home/fred'), unpack the
GCC and GNU Pascal source distributions. This will create separate
subdirectories for GCC and GPC. Let us assume `gcc-2.95.1' and
`gpc-20000535' in this example.
% cd /home/fred
% gzip -c -d gcc-core-2.95.1.tar.gz | tar xf -
% gzip -c -d gpc-20000535.tar.gz | tar xf -
`cd' to the GPC directory and move the contents (a subdirectory
`p') to the subdirectory `gcc' of the GCC directory:
% cd /home/fred/gpc-20000535
% mv p /home/fred/gcc-2.95.1/gcc/
It is recommended, though not required, to use a separate
directory for building the compiler, rather than compiling in the
source directory. In this example, let us create
`/home/fred/gpc-build' for this purpose:
% mkdir /home/fred/gpc-build
If you use a separate directory, you do not need to write into the
GCC source directory once you have patched the GCC source (see
below), and can build GPC for more than one platform from the same
source tree.
In case you are re-using a directory where you have already built
GCC and/or GPC for a different target machine, do `make distclean'
to delete all files that might be invalid. One of the files this
deletes is `Makefile'; if `make distclean' complains that
`Makefile' does not exist, it probably means that the directory is
already suitably clean.
3. Configuring and building GCC
GNU Pascal is automatically configured with GCC. Configuration of
GCC is treated in depth in the GCC installation instructions. The
normal procedure is as follows:
`cd' to the GPC build directory. From there, run the `configure'
script in the GCC source directory:
% cd /home/fred/gpc-build
% /home/fred/gcc-2.95.1/configure --enable-languages=pascal
This creates all the necessary config files, links and Makefile in
the GCC object directory.
Note 1: The configuration will prompt you for patching the GCC
source for GPC support, so you need write access to that
directory. All changes to GCC are surrounded by `#ifdef GPC ...
#endif', so they should not interfere when you build a C compiler
from this source tree.
Note 2: The `--enable-languages=pascal' option means that we only
want to build the Pascal compiler and not, for instance, the C++
compiler.
Note 3: The standard directory for installing GCC and GPC is
`/usr/local/lib'. If you want to install files to an alternate
directory DIR, specify `--prefix=DIR' when you run `configure'.
4. Putting other GNU tools in place
Some environments require other GNU tools (such as the GNU
assembler or linker) instead of the standard system tools for GCC
to work. (See the GCC installation instructions for details.) If
this is the case for your system, install the required tools in
the GPC build directory under the names `as', `ld', or whatever is
appropriate. This will enable the compiler to find the proper
tools for compilation of the program `enquire' (a part of GCC) and
to install the GNU tools to a place where they are found by GCC
but do not interfere with the standard system tools.
Alternatively, you can do subsequent compilation using a value of
the `PATH' environment variable such that the necessary GNU tools
come before the standard system tools.
5. Compiling GPC
Once you are satisfied with the configuration as determined by
`configure', you can build the compiler:
% make
Notice that this procedure will build the C compiler (and maybe
some other compilers) too, because that is used to compile the GPC
runtime library.
Optionally, you may supply CFLAGS, LDFLAGS or RTSFLAGS. CFLAGS is
used for compiler and RTS, RTSFLAGS are for RTS only, i.e.: `make
CFLAGS="-O2" RTSFLAGS=-Wall'
6. Completing the installation
When everything has been compiled, you can check the installation
process with:
% make -n install
To complete the installation, run the command `make install'. You
need write access to the target directories (`/usr/local/bin',
`/usr/local/lib', `/usr/local/info', `/usr/local/doc', and
`/usr/local/man' in this example), so this is usually done as
`root':
% su -c "make install"
If you want to install *only* the Pascal compiler (for example if
you already have the correct version of GCC installed), `cd' to the
`gcc' subdirectory of the build directory (e.g.
`/home/fred/gpc-build/gcc') and run `make pascal.install'. This
installation process does *not* overwrite existing copies of
`libgcc.a' or `specs', should they exist.
Also from the `gcc' subdirectory you can do some more "exotic"
builds. For instance, you can build the GPC WWW pages by typing
`make pascal.html' or a binary distribution by typing `make
pascal.bindist'. See the `Makefile' in that directory for more
examples.
Have fun with GPC!
Hi all
You can get the latest version of my ongoing work of translating the
GCC WinAPI headers to GPC import units from agnes (in the
directory: ftp://agnes.dida.physik.uni-essen.de/home/chief/).
The sources (messages.pas, wintypes.pas and winprocs.pas) are in:
ftp://agnes.dida.physik.uni-essen.de/home/chief/winapi-src.zip
The precompiled units are in:
ftp://agnes.dida.physik.uni-essen.de/home/chief/winapi-bin.zip.
I suggest that you put the precompiled units in your GPC 'units'
directory, and keep the sources elsewhere (where they won't be
located automatically by the compiler). That way you will get much
faster compiles and links (two of the units are quite huge, and until
automake is fixed, you don't want GPC to try and compile them all
the time).
Since the original GCC headers are LGPL, I guess that this makes
my Pascal translations LGPL as well. If anyone wishes to help to
debug/test/develop/complete these units, please feel free to jump in!
I have been working on this for about a year, and it is quite clear
that it is way beyond the capacity of one person to complete.
Best regards, The Chief
-----
Dr Abimbola A Olowofoyeku (The African Chief)
Email: African_Chief(a)bigfoot.com
Author of Chief's Installer Pro v5.22 for Win32
http://www.bigfoot.com/~African_Chief/chief32.htm
Hello,
we now have a separate list for documenting GPC. Everyone who
wants to contribute to the GPC documentation project is invited
to join.
We have splitted this list from the main GPC list because some
documentation issues are not of interest for users of GPC.
(For instance, spelling wars are off-topic on the ordinary GPC
list, but they can be on-topic on the GPC documentation list.:-)
The GPC documentation list is <gpc-doc(a)gnu.de>. To subscribe to
the list, write a message containing "subscribe gpc-doc" in the
body to <majordomo(a)gnu.de>. (The subject will be ignored.)
Happy hacking,
Peter
--
http://home.pages.de/~Peter.Gerwinski/ - G-N-U GmbH: http://www.g-n-u.de
Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - gpc-19990118
GnuPG key fingerprint: 9E7C 0FC4 8A62 5536 1730 A932 9834 65DB 2143 9422
keys: ftp://ftp.gerwinski.de/pub/keys/ - AntiSpam: http://spam.abuse.net
Hi all
A new snapshot of GPC (Mingw32) has been uploaded to Agnes.
This is based on Peter's recent native Mingw32 build (based on gcc
2.95.1).
The file is:
ftp://agnes.dida.physik.uni-essen.de/home/chief/
gpc-20000202-i586-mingw32.zip
If you unzip (with an unzip program that understands long
filenames) into 'c:\usr\', reproducing the directory structure in the
zip file, you should have a ready-to-run and stable Win32 snapshot
of GPC (you just need to add 'c:\usr\local\bin' to the PATH).
Best regards, The Chief
-----
Dr Abimbola A Olowofoyeku (The African Chief)
Email: African_Chief(a)bigfoot.com
Author of Chief's Installer Pro v5.22 for Win32
http://www.bigfoot.com/~African_Chief/chief32.htm
Svgalib-GPC is a set of graphics units for GNU-Pascal. The units are the
rewriting of data contained in the header include files included in the
Svgalib distribution, in a manner which make it easy for Pascal
programmers to use Svgalib without needing to rewrite prototypes.
Most units just contain the prototypes for using Svgalib functions, with
some adjustments regarding Boolean return values and CString stuff. The
keyboard units (raw and normal mode) yet are rewritten using TFDD
capabilities (and thanks to Frank for the explanation) and they seem to
work well.
I think the package is alright but I haven't tested it out much. So
current status is neither of alpha, beta, gamma, delta, YOU have to tell
me :-)
The full library is distributed under the GNU LGPL. For details read the
file COPYING.LIB contained in the tarball.
Svgalib-GPC needs the latest alpha version of GPC, because of the TFDD
stuff, and it's not that portable, in fact I think it's useable for
Linux/x86 only, but it might work under other systems with svgalib4ggi.
If you're going to test it for me, please tell me about the results.
There are not good demos in the tarball to show you the capabilities of
this all, and I'm not spending much time coding new features or demos. I
think I'll improve this just if I get feedback and requests :-) Just
because I enjoy only if people use what I code :-)
If you have to report bugs, suggestions, requests, write to me at this
address girardi(a)keycomm.it
The site where you can find a bit more details about the units and
download the current tarball is:
http://agnes.dida.physik.uni-essen.de/~nicola/
Thanks to: Frank Heckenbach for help with TFDD stuff and for getting me
to release this and Peter Gerwinski for the account on agnes.
Have fun :)
--
Nicola Girardi <girardi(a)keycomm.it>
Key fingerprint = 5D9E ED36 C2E9 EF8F C4B6 25C2 3FF4 E5A2 27A7 83B9
GnuPG Key at http://agnes.dida.physik.uni-essen.de/~nicola/gpg-plan
Hi, everybody!
This is to announce the release of PENG 2.1. PENG is an Integrated
Development Environment written in and for GPC.
PENG was written completely in Pascal and created using GPC. It is
well suited for editing and compiling Pascal programs with GPC,
though its functionality is not Pascal specific, and it can just as
well be used for writing C, HTML, TeX, Texinfo, E-Mail or any other
ASCII based format. PENG was developed and tested mainly under
Linux/x86, but also under DJGPP and Solaris.
The main web site of PENG is <http://fjf.gnu.de/peng.html>. It
contains more extensive information about PENG, including the
complete documentation in HTML format, as well as download
facilities and a pointer to the PENG mailing list. The mailing list
is the recommended place for bug reports and requests about PENG.
The main changes since PENG 2.0 are the following. They are
documented in more detail in PENG's online help.
- Some minor bug fixes and improvements in some details
- Made some aspects of the "look and feel" easier and more
consistent
- PENG also accepts long options on the command line now
- PENG's example tools and variables are now built into PENG, and
their documentation was merged into the PENG manual. The built-in
tools and variables can be dumped to a file with the `-d' or
`--dump-tools' option, and their automatic use can be suppressed
with the `-N' or `--no-builtin-tools' option, so PENG's tools and
variables remain fully customizable.
- Support for progress messages and a progress bar while running
tools
- Lex highlighting for different languages, case sensitive or
insensitive
- Speeded up the opening of info files without tag tables
- `<ALT>-<SPACE>' (non-breaking space) now also works under X11 and
DJGPP.
- Deleting words with `<CTRL>-<T>' now also works in string input
boxes.
- Easier and better customizable color selection
- Menu `Options/Editor' split into two menus (`Options/Editor1' and
`Options/Editor2') because it was growing too large
- New option to show the line numbers in the text editor (menu items
`Options/Editor1/Line numbers', `Options/Editor2/Line number
width', `Options/Colors/Editor/Line number')
- New tool output redirections `#p', `#P' ("parallel")
- Under Linux, PENG now recognizes shifted function keys if you have
new keytables (e.g. console-data-1999.xx.xx) which come with
recent versions of the distributions. However, if you still have
the old keytables and PENG doesn't recognize, e.g., `<SHIFT>-<F1>'
anymore, you'll have to upgrade them if you need shifted function
keys (the change doesn't affect other keys, so PENG will be far
from unusable even with the wrong version of keytables).
Note, there are some changes which could require a few users to do
some manual changes, but should be beneficial to most. First-time
PENG users do not need to care about the following:
- The names of the automatically loaded config files have changed.
They are now `/etc/peng.conf' and `~/.peng' under Unix. Under Dos,
they are `peng.ini', either in the directory `$DJDIR\etc\' (if
DJGPP is installed) or in the directory where `peng.exe' is
installed, and `peng.cfg', either in the directory `$HOME' (if you
set the environment variable `HOME') or in the directory where
`peng.exe' is installed.
- Since PENG's example tools and variables are now built into PENG,
if you installed the `pengrc' file before, please delete it now,
to avoid confusion. If you made changes to the file, you might
have to extract them to a new config file.
- Since the documentation of the built-in tools was merged into
PENG's manual, if you installed pengtools.info before, please
delete it now to avoid confusion.
- The `viewdvi' script is no more needed. Its functionality has been
included into the respective PENG tools itself. If you installed
the script before, you can delete it now, but you can as well keep
it if you like. If you made changes to the script, you'll have to
change the respective PENG tools now.
- PENG's color selection has been extended. On the one hand, there
are more colors to choose, so you can customize your colors in
more detail (e.g., different colors for the main menu and submenus
if you like). On the other hand, most colors now can be unselected
(and many are unselected by default), and PENG will automatically
use the next appropriate one then. E.g., the colors for the main
menu are unselected by default, and PENG will use the same colors
as for submenus by default. Similarly, the backgound color of most
items in the text editor now defaults to that of normal text, so
you can change the background in a single place rather than having
to change several items. More details can be found in the online
help for `Options/Colors'.
While all this will make your color selection easier and better
customizable, it might change your previous color selections
slightly because of unexpected influence of the "next" color
mechanism. This should be easy to correct by setting the right
colors.
Furthermore, this change required slight changes to PENG's config
file format. You can convert your old config files with the script
below. If you don't want to do it (e.g., because you don't have
awk and you're too lazy to install it ;-), you can load the old
config files and ignore the warnings. You will lose your color
selections, nothing more.
#!/bin/sh
if [ $# == 0 ]; then
echo "$0: no arguments given" >&2
exit 1
fi
if test -z "$AWK" ; then
for AWK in gawk nawk awk ""; do
if type $AWK 2>&1 | grep 'not found' > /dev/null 2>&1; then
:
else
break
fi
done
fi
if test -z "$AWK" ; then
echo 'No awk found.' >& 2
exit 1
fi
for a do
if [ ! -f "$a" ]; then
echo "$a does not exist"
elif [ `grep -c '^ProgramVersion="[^"]*", 6' "$a"` != 1 ]; then
echo "$a is not a PENG config file, version 6"
else
$AWK '
/^ProgramVersion=/ { sub ("=.*", "=\"PENG config converter\", 7") }
/^Color Progress message=/ { sub ("^Color Progress message=", "Color Activity message=") }
/^Color Editor Non breaking space=/ { sub ("^Color Editor Non breaking space=", "Color Editor Non-breaking space=") }
/^Color/ { c = $0;
sub ("[^=]*=", "", c);
x = c;
sub (",.*", "", c);
sub ("[^,]*,", "", x);
sub (",.*", "", x);
if (c + 0 >= 0) c = sprintf ("%i, %i", c % 16, c / 16);
if (x + 0 >= 0) x = sprintf ("%i, %i", x % 16, x / 16);
sub ("=.*,", "=" c ", " x ",")
}
{ print }
' < "$a" > "$a.conv"
mv -f "$a.conv" "$a"
echo "$a converted"
fi
done
Have much fun with PENG,
Frank
--
Frank Heckenbach, frank(a)fjf.gnu.de
http://fjf.gnu.de/
PGP and GPG keys: http://fjf.gnu.de/plan
Hello,
the list archive at should be working again now.
The URL is
http://www.gnu.de/archive/wilma.cgi/gpc
and
http://www.gnu.de/archive/wilma.cgi/gpc-announce
respectively. Now the pages also come in gpc signature colors. :-)
Currently, the search option is working fine. If you find it broken,
please email me at <anja(a)drewitz.de>. Please don't mail a copy to the
gpc list because I let procmail move all mails with To: gpc... and
Cc: gpc... to a separate folder and would not see your mail for a
long time.
Best wishes,
Anja
Hi All
Binaries for Solaris 8 (Sparc and Intel) are now available on:
http://math.uwb.edu.pl/download/solaris8/
ftp://mizar.uwb.edu.pl/pub/misc/solaris8/
Hope someone uses it
--
.
Mariusz Zynel
Institute of Mathematics | phone: +48 (85) 745 75 52
University of Bialystok |
Akademicka 2 St | mailto:mariusz@math.uwb.edu.pl
15-267 Bialystok |
Poland | http://math.uwb.edu.pl/~mariusz/
Hi, everybody!
This is to announce the release of PENG 2.0. PENG is an Integrated
Development Environment written in and for GPC.
PENG 2.0 is the first version released publicly. (In case you wonder
about the version number: Large parts of PENG have grown out of
another application which was developed and used for several years.
Therefore, I feel that version 2.0 is appropriate for this release.)
PENG was written completely in Pascal and created using GPC. It is
well suited for editing and compiling Pascal programs with GPC,
though its functionality is not Pascal specific, and it can just as
well be used for writing C, HTML, TeX, Texinfo, E-Mail or any other
ASCII based format. PENG was developed and tested mainly under
Linux/x86, but also under DJGPP and Solaris.
The main web site of PENG is <http://fjf.gnu.de/peng.html>. It
contains more extensive information about PENG, including the
complete documentation in HTML format, as well as download
facilities and a pointer to the PENG mailing list. The mailing list
is the recommended place for bug reports and requests about PENG.
To the beta testers: The format of the config files has not changed
since the last beta release (19991028), so you can keep using them
without changes.
Some Highlights:
* Portability. In particular, there are versions for general
terminals on Unix systems, for X11, and for DJGPP. The terminal
versions work naturally across telnet/rlogin/slogin between
systems with the same or different terminal types, and X11 is
network-transparent, anyway.
* Support for multiple windows, including editing of the same file
in several windows at the same time
* Advanced block operations, persistent and non-persistent blocks,
editable clipboard, automatic copy function
* A reader for GNU Info documentation, including support for
compressed info files
* A paragraph mode, useful for editing mail, news, TeX, HTML, etc.
* A quote protection mode for editing mail and news
* Multi-level Undo/Redo capability
* Lex highlighting
* Autosave mode
* Combines the ease of use known from some Dos IDEs with the power
of Unix environments, e.g.:
- Supports function keys (where available on the terminal) and
file selection boxes, but also file name completion with Tab;
`$' for environment variables as well as `~' and `~user' for
home directories, and all the file name wildcards like `*',
`?', `[^-]', `{,}'
- Easy search/replace capabilities, but also regular expression
searches and replacements with backreferences
- Handles files with Unix or Dos line endings on both kinds of
systems, without converting them automatically, but with the
easy possibility to convert them explicitly at any time.
- You can invoke an OS shell, but you can also suspend PENG.
- You can use control characters like Control-C for cursor
movement in PENG if you want, but PENG still reacts correctly
to external interrupt, termination or hangup signals and
saves unsaved changes whenever possible.
- Readable configuration files in text format, a global one and
per-user ones under Unix
- Simple and numbered backup files
- Lock files (compatible with vim) to prevent several editors
from editing the same file at the same time
- Easily accessible context-sensitive help, but in the same
format (GNU Info) as used by many other programs, and easily
extendable for your own tools
- PENG tools can invoke external processes (e.g., compilers),
but they can also fork them to run in the background while you
can already go on editing your files.
* Completely configurable colors. Very important. :-)
* A way to open files read-only, from the menu and the command line
* No mouse support. (-: Leaves the mouse to gpm and similar
applications.)
* Hotlist for easy access to files edited frequently
* Extensive tool scripting capabilites:
- Powerful syntax, similar to Unix shells
- User-defined variables of several types
- Many pre-defined functions for strings, regular expressions,
file names, boolean values, mathematical operations on real
and complex numbers, interaction with the user and control of
the editor and info reader
- Conditional statements
- Access to a message window, suitable for GNU standard message
format, but other message formats can be converted. An example
converter for LaTeX messages is included.
- PENG can start external processes in the background and still
receive their output. Background processes can be killed
easily. Very useful for long compilations.
- Tools can depend on the file name of the current editor and on
other conditions, to allow e.g. several versions of a similar
tool by the same name for different languages/formats.
- Tools can be executed automatically at the start or
termination of PENG.
- Many example tools, including usage of utilities like grep,
syntax macros, and the compiler invocations with hotkeys
familiar from other IDEs (for GPC and GCC and very similarly
even for LaTeX and makeinfo), all fully customizable
Have much fun with PENG,
Frank
--
Frank Heckenbach, frank(a)fjf.gnu.de
http://fjf.gnu.de/
PGP and GPG keys: http://fjf.gnu.de/plan