Gpc

gpc@gnu.de

5400 discussions

pindent features
by Eike Lange 07 Oct '00

07 Oct '00

Hi! Thorsten Hindermann and I are doing a lot of work with pindent, a small program to format Pascal-Source-Files by adding or deleting whitespaces and changing the appearance of comments etc. If you like, you may add some features you would like to have in the program. You can download our actual ideas via anonymous ftp: mond.dida.physik.uni-essen.de/pub/pindent/README.OPTIONS.0005a.bz2 (bzip2-compressed) Ideas not in this file are: - Support for "FIXME"-comments (*@@ Fixme *) - .pindentrc with favourite options If you have any ideas or suggestions, please send them via E-Mail to: pindent(a)mond.dida.physik.uni-essen.de Eike Lange

1 0

Re: GPC - Manual
by Jose' M. Perez 05 Oct '00

05 Oct '00

The format looks good, but I would suggest several changes. First, if "Reference-Card" is the version number, put the version number in the page footer. Second, replace "Theme" with "Subject" or "Command", "Function", or something more suitable. The syntax section uses a notation that I am not familiar with. You might need an explanation of how to interpret the syntax. Good luck and thank you for volunteering! -----Original Message----- From: U. Bauermann <uwe(a)bauermann.de> To: gpc(a)gnu.de <gpc(a)gnu.de> Date: Sunday, September 17, 2000 12:12 PM Subject: GPC - Manual >Hi. > >The GPC-manual is most uncomplete. >Especialy the refence. >I will help to make the reference complete. >I must teach my students 'how to programming in Pascal'. >And i almost make my own scripts. >I can make my docs like a format, that they fit in the GPC-manual. >Today, i am learning LaTeX, and the GPC-manual must be in TeXInfo. >Is this right? >Is there a tool to convert LaTeX to TeXInfo? >(Sorry, i don't know anything about TeXInfo. But when it >is necessary i will learn it.) >In my docs (my scipts) i have a basicly layout. >When it is possilbe to use this layout for the GPC-reference >i'm verry happy, and i will help to make it complete. >('Uff' was this really my words?) >There is a haeder and a footer. >I have made an example in LaTeX. You can take a look: >http://www.bauermann.de/GPC/manual/reference/ >(Several formats: LaTeX, dvi, ps and/or jpg) >This basicly form looks good in my eyes. >Please, think about it and tell me your ideas. >It's only an example. >Then we can change it to make it perfect. >Sorry my english-grammar. I use my english only for reading, now. > >Greetings > Uwe > >PS.:BTW: Sorry my LaTeX-Code. I'm a beginner. Please send me > suggestions, corrections, optimum, ... Thanx > >-- >Zu Fragen, Risiken und Nebenwirkungen wenden Sie sich bitte an: >Email: uwe(a)bauermann.de >Homepage: http://www.bauermann.de >

2 1

Re: Styles
by Eike Lange 05 Oct '00

05 Oct '00

Hi! On Mon, Oct 02, 2000 at 03:36:35PM +0200, Frank Heckenbach wrote: > Eike Lange wrote: > > While discussing about different Pascal-styles for > > the pindent-program there came up a question my books > > can't answer: > > array [1..3] <===> array (.1..3.) > > { comment } <===> (* Comment *) > The standard calls the latter "lexical alternatives". > BTW, another alternative is `@' for `^' (really!)... :-/ Ok, we are going to support this, too ;-) > With the comment delimiters, there seem to be different opinions. > I personally prefer `{ }' (analogous to `[ ]'), but Peter prefers > `(* *)' so that comments are more visible. We are going to support a switch to support both variants. Later, we will ask you for a set of suggestions for our switch --gpc-team or something like that. :-) > Oh yeah, another thing to complicate the issue: To indicate > "FIXME"s, we're currently using two or more (depending on the > urgency) `@'s in a comment -- then, of course, always `(* *)' > comments because they obviously require special attention. So, e.g.: > (*@@ This procedure is a temporary kludge. It will disappear when > foobar has been done correctly. *) > procedure foobar_kludge; > This comment should, of course, not be converted to `{@@ }', even if > it's before a declaration, but for a program it's also not hard to > recognize the `@'... Well, some tools for C/C++/Java support "Doc-Comments" (KDoc, Doc++, JavaDoc, ...) They are bild like this /** This is a Doc-Comment */ and the char '@' indicates a command like /** This is a command for KDoc @author someone, someone(a)somewhere.in.universe */ We would like to write a pdoc after pindent and also want to support some "@"-commands like: (** This might be a pdoc-comment some time @author me, me(a)somewhere.in.universe *) Do these commands conflict with you comments for "FIXME"s ? Eike

2 1

Re: Styles
by Olivier Lecarme 04 Oct '00

04 Oct '00

>>>>> "EL" == Eike Lange <eike.lange(a)uni-essen.de> writes: EL> Hi! EL> While discussing about different Pascal-styles for EL> the pindent-program there came up a question my books EL> can't answer: EL> How are the different styles called, EL> which one can use for coding: EL> array [1..3] <===> array (.1..3.) EL> and EL> { comment } <===> (* Comment *) EL> BTW: EL> Why did these styles came up? EL> Is one of them "old-fashioned"? Pascal was first implemented on a CDC 6600 computer. Characters were coded on 6 bits, and thus there were only 64 different characters, including end-of-line. There were no square brackets, no circumflex, but there were curly brackets, an up arrow and a Â« not equal Â» operator. Thus, {} is as old as the first implementation, but [] is less old. ^ for pointers and <> for comparison are newer than the old characters, which no longer exist on most existing character codes. Olivier Lecarme

1 0

GPC - Manual
by U. Bauermann 03 Oct '00

03 Oct '00

Hi. The GPC-manual is most uncomplete. Especialy the refence. I will help to make the reference complete. I must teach my students 'how to programming in Pascal'. And i almost make my own scripts. I can make my docs like a format, that they fit in the GPC-manual. Today, i am learning LaTeX, and the GPC-manual must be in TeXInfo. Is this right? Is there a tool to convert LaTeX to TeXInfo? (Sorry, i don't know anything about TeXInfo. But when it is necessary i will learn it.) In my docs (my scipts) i have a basicly layout. When it is possilbe to use this layout for the GPC-reference i'm verry happy, and i will help to make it complete. ('Uff' was this really my words?) There is a haeder and a footer. I have made an example in LaTeX. You can take a look: http://www.bauermann.de/GPC/manual/reference/ (Several formats: LaTeX, dvi, ps and/or jpg) This basicly form looks good in my eyes. Please, think about it and tell me your ideas. It's only an example. Then we can change it to make it perfect. Sorry my english-grammar. I use my english only for reading, now. Greetings Uwe PS.:BTW: Sorry my LaTeX-Code. I'm a beginner. Please send me suggestions, corrections, optimum, ... Thanx -- Zu Fragen, Risiken und Nebenwirkungen wenden Sie sich bitte an: Email: uwe(a)bauermann.de Homepage: http://www.bauermann.de

2 1

Styles
by Eike Lange 02 Oct '00

02 Oct '00

Hi! While discussing about different Pascal-styles for the pindent-program there came up a question my books can't answer: How are the different styles called, which one can use for coding: array [1..3] <===> array (.1..3.) and { comment } <===> (* Comment *) BTW: Why did these styles came up? Is one of them "old-fashioned"? Eike Lange

2 1

converter (*.c => *.pas)
by Gregor Schlosser 28 Sep '00

28 Sep '00

Hallo, i am looking for a program to convert c-files into pascal-files. Can anybody help me,please? Thanks Gregor Schlosser

2 1

Compilation Problems with Native sun-sparc compiler
by Anuradha 27 Sep '00

27 Sep '00

Hello , Even When i compile the program with the included file pge4aa in the working directory itself , PROGRAM TEST; uses pge4aa; var i : integer; Begin writeln('trial'); writeln(i); end. I get the error, $ gpc -o anu --automake test.pas pge4aa.pas:618: warning: empty input file tst.pas:3: module/unit interface `Pge4aa' could not be imported $ What do i do? Thank you. Regards, Anu

1 0

Compilation Problems with Native sun-sparc compiler
by Anuradha 26 Sep '00

26 Sep '00

2 1

Test
by Dafi Yondra 22 Sep '00

22 Sep '00

newbie

1 0

Jump to page:

2025

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

1999

1998

1997

1996

1995

Gpc