Gpc-doc

gpc-doc@gnu.de

53 discussions

Re: GNU Pascal Coding stuff References:
by Nicola Girardi 13 Jul '01

13 Jul '01

> Nick, you might want to try s/@ifinfo/@ifnottex/ or something. I'm trying to fix this problem. Well, there's a problem with a "<p>" being inserted after the `G' of "GNU" for no good reason... > > 2. Suggest changing " aString: String " to " S: String " > > Indeed. I copied these lines (as an example) from older code which > does not conform to our rules about identifier names. Is this OK? : @example : @{ Port access functions @} : function InPortB (PortNumber: ShortWord): Byte; : function InPortW (PortNumber: ShortWord): ShortWord; : procedure OutPortB (PortNumber: ShortWord; aValue : Byte); : procedure OutPortW (PortNumber, aValue: ShortWord); : @end example Best regards, Nick

1 0

Standards.text
by Russ Whitaker 13 Jul '01

13 Jul '01

Hi Printed out a copy of the pascal-standards.text: 1. Table of Contents is at wrong end. 2. Suggest changing " aString: String " to " S: String " You have 2 lines that are 100 cols in length. While most printing defaults to 80 cols for 8.5 inch paper you can set printer to elite which gives you 96 cols without line wrap. (I prefer 90 cols max so I can have an extra margin for 3 hole punch.) Yes I know you can't always keep the line length to 96 or less and have the results look neat, but at least this change will help at times. Russ

3 2

GNU Pascal Coding Standards
by Nicola Girardi 13 Jul '01

13 Jul '01

Hi GPC'ers! This is to announce the first public release of the GNU Pascal Coding Standards. The aim of this document is extending the GNU Coding Standards with specific information relating Pascal programming. Of course there are topics that can be shared between the two manuals, and we have taken this into account. You are encouraged to read the manual and follow the suggestions you find, fix the bugs (yes, there can be bugs in documentation, most times disguised as typos ;-)) and discuss the several issues raised. You can find the standards online at: http://adele.gerwinski.de/~nicola/pascal-standards/ NB: We're sorry for the long HTML file, but if we use texi2html to split the files we get many links pointing to the same document instead of pointing to the GNU Coding Standards, to which we refer often. Greetings, Frank Heckenbach <frank(a)pascal.gnu.de> Peter Gerwinski <peter(a)gerwinski.de> Nicola Girardi <nikke(a)swlibero.org>

1 0

email problems
by Peter Gerwinski 11 Jul '01

11 Jul '01

Hello, during the last 36 hours emails to this list were not delivered. The problem is fixed now. In case you have unsuccessfully tried to post to the list, please retry now. In den letzten 36 Stunden wurde E-Mails an diese Liste nicht zugestellt. Das Problem ist jetzt behoben. Wer in diesem Zeitraum vergeblich versucht hat, E-Mail an die Liste zu schicken, kann es jetzt noch einmal probieren. 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-20010623 GnuPG key fingerprint: 9E7C 0FC4 8A62 5536 1730 A932 9834 65DB 2143 9422 keys: http://www.gerwinski.de/pubkeys/ - AntiSpam: http://spam.abuse.net

1 0

server moving this Friday (June 29)
by Anja Gerwinski 29 Jun '01

29 Jun '01

Hello, folks, tomorrow (Friday) our mailing lists and web pages are moving to our new server adele (.gerwinski.de). Maybe the mailing lists will not be available for a brief time; they should be running again in the evening. I'll let you know via the list when we are finished. If afterwards mail is not delivered via the list as it should please let me know <anja(a)maeh.theo-phys.uni-essen.de>. Best wishes, Anja

1 0

help writing documentation
by Eike Lange 09 Mar '01

09 Mar '01

Hi! I would like to help writing documentation for gpc. My project, writing german documentation for gpc died because nobody was interested helping me and its too much for just one man. I would prefer to discuss documentation-related topics on the gpc-doc-mailinglist (gpc-doc(a)gnu.de) . There are still some questions left: - Is Texinfo 4.0 ok? - Which options do you use to create the diffs - Are there any documentation-standards, I have to recognize? Eike

2 3

Re: A very minor documentation error
by Frank Heckenbach 14 Dec '00

14 Dec '00

Bernard Leak wrote: > Dear Sirs, Mesdames, Unspecified Neuters, and others: > > The heading to the page > http://agnes.dida.physik.uni-essen.de/~gnu-pascal/gpc_4.html#SEC4 > 3.1 General Changes And Possible Incompatibilies To Previous Versions > > and the link to it on the page > http://agnes.dida.physik.uni-essen.de/~gnu-pascal/news.html > > (there may be other links - I haven't searched) > is not in English (not even International English). > > It should read > > "Incompatibilies To" <- "Incompatibilities With" > > Normally, the preposition "With", articles and conjunctions > shouldn't be capitalised either, except at the start of a sentence. > The site is notably inconsistent in its capitalisation style, so > I feel free to suggest a merely local change. > > I propose a squeakily-clean replacement with > > 3.1 General Changes and Possible Incompatibilities with Previous Versions Thanks. These kinds of errors are due to the fact that most of the writers and editors of the documentation are non-native speakers, and I (who wrote this section, AFAIR) have never learnt the rules for capitalizing headlines and such... If you'd like to offer more help in these matters, this would be very welcome. The preferred form for making such changes is to start with the Texinfo files (part of GPC source distributions and available through CVS) and send diffs to the gpc-doc mailing list (to which I'm sending a CC of this mail). Frank -- Frank Heckenbach, frank(a)g-n-u.de, http://fjf.gnu.de/ GPC To-Do list, latest features, fixed bugs: http://agnes.dida.physik.uni-essen.de/~gnu-pascal/todo.html

1 0

Val
by Frank Heckenbach 15 Nov '00

15 Nov '00

The GPC reference claims that the 3rd parameter of Val is optional: : procedure Val (const Source: String; var x: INTEGER OR REAL); : or : procedure Val (const Source: String; var x: INTEGER OR REAL; : var ErrorCode: Integer); However, that's not the case in GPC (neither in BP from which the Val procedure comes). Thanks to Nicola Girardi for pointing out this discrepancy. Though there are cases where one might want to ignore the 3rd parameter (such as if it was checked before calling Val that the string consists only of digits, or at least has a starting digit and one is willing to ignore trailing "garbage"), but IMHO they're rare enough that they don't justify another syntax extension. So I suggest to "fix" the documentation by removing the first part. -- Of course, I could've just done that, but perhaps someone disagrees... Also, maybe someone interested in writing/maintaining documentation might want to take this as a start (and perhaps write some words about Val in the reference while they're at it :-)... Minor note: The name of the parameter should by `ErrorPosition' rather than `ErrorCode' (the BP documentation also calls it `Code', but we shouldn't copy their mistakes, it's not a code, just a position)... Frank -- Frank Heckenbach, frank(a)g-n-u.de, http://fjf.gnu.de/ GPC To-Do list, latest features, fixed bugs: http://agnes.dida.physik.uni-essen.de/~gnu-pascal/todo.html

1 0

[egbert: Re: help writing documentation]
by Egbert Seibertz 07 Nov '00

07 Nov '00

Cc forgotten ... Egbert

1 0

Test
by Peter Gerwinski 17 Mar '00

17 Mar '00

Testing (16.3.2000, 27:10)

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

Gpc-doc