* info about mailing lists updated

This commit is contained in:
Tomas Hajny 2000-01-24 20:20:29 +00:00
parent 26f38e15e3
commit 2737dcd7f1

View File

@ -10,7 +10,8 @@
This package contains a freeware 32-bit pascal compiler for 386+. The language
and the runtime library are more or less compatible to TP 7.0. Some Delphi
additions have also been implemented like classes,exceptions,ansistrings and rtti.
additions have also been implemented like classes, exceptions, ansistrings
and rtti.
Free Pascal is currently available for the following platforms:
- DOS, via the DJ Delorie's GO32V2 Dos extenders
@ -209,10 +210,10 @@ Optional source package src09914.zip:
* Documentation
****************************************************************************
The documentation is available as HTML pages, PDF, PS, and text although the recommended
format is pdf. These are all available in ftp... /docs/...
The documentation is available as HTML pages, PDF, PS, and text although the
recommended format is pdf. These are all available in ftp... /docs/...
NB that there is at present no fpc specific documentation for the win32
NB that there is at present no FPC specific documentation for the Win32
system functions. There is a note in the ftp /doc explaining where
the MS help file for this can be obtained.
@ -223,8 +224,14 @@ the MS help file for this can be obtained.
Suggestions, Help ...
---------------------
e-mail: fpc-devel@vekoll.saturnus.vein.hu (bugs, developer related qs)
e-mail: fpc-pascal@vekoll.saturnus.vein.hu (general pascal related qs)
e-mail: fpc-devel@lists.freepascal.org (bugs, developer related qs)
e-mail: fpc-pascal@lists.freepascal.org (general pascal related qs)
Both these adresses are for mailing lists. If you're not subscribed,
be sure to mention this fact when sending questions to these lists,
so that people sending answers know about it and send you a copy.
Information about available lists and subscription can be found
on http://lists.freepascal.org/mailman/listinfo
www: http://www.freepascal.org
ftp: ftp.freepascal.org/fpc
@ -235,23 +242,23 @@ can be found on the web site.
SNAPSHOTS & SOURCES
-------------------
One of the features of fpc is the snapshots. These are made daily or weekly
One of the features of FPC is the snapshots. These are made daily or weekly
from the developers' latest versions of the source. Snapshots are available
for the go32v2, win32, os2 and linux versions of the compiler/rtl. Snapshots
are also available for the go32v2 & win32 ides, and for fv, fcl, gtk and
utils for go32v2 and win32. The latest snapshots are in: ftp... /fpc/snapshot/
for the GO32v2, Win32, OS/2 and Linux versions of the compiler/rtl. Snapshots
are also available for the go32v2 & Win32 IDEs, and for FV, FCL, GTK and
utils for GO32v2 and Win32. The latest snapshots are in: ftp... /fpc/snapshot/
in appropriately named .zip/tar files.
You will also normally find in the snapshot .zip file a readme, with a mention
the latest changes included. It is quite common, tho' doesn't always happen,
that when a bug is reported it is fixed and a fixed version can be obtained
the NEXT day in the appropriate snapshot.... yes really!
You will also normally find in the snapshot archive file a readme, with
a note about the latest included changes. It is quite common, tho' doesn't
always happen, that when a bug is reported it is fixed and a fixed version
can be obtained the NEXT day in the appropriate snapshot.... yes really!
Also on the ftp site you'll find a /dist directory, with the latest
distributed releases, a /docs directory, and a /source directory, in
which every night at about 0100 GMT the latest source generated by the
developers during the day& evening before is exported from cvs
into .zips eg compiler.zip, rtl.zip, base.zip etc.
developers during the day & evening before is exported from CVS
into ZIP files eg compiler.zip, rtl.zip, base.zip etc.
Making your own snapshots
@ -274,7 +281,7 @@ the fpc-devel mailing list.
If you find a fault or 'feature' in a release, please report it
to the fpc-devel mailing list. PLEASE SEND ALSO A SMALL EXTRACT OF THE SOURCE
CODE which caused the problem, and state the version eg win32, go32v2,
CODE which caused the problem, and state the version eg Win32, GO32v2,
and the date of the compiler etc on which you noticed the problem & any other
useful info so the developers can reproduce the problem, otherwise they may
not be willing/able to fix it.