Gpc

gpc@gnu.de

5400 discussions

GPC REF: do (2)
by Miklos Cserzo 12 Jun '98

12 Jun '98

Hi Folks, how about the second version? I think it would be practical to use consistent abbreviations in the documentation for the different dialects: SP= ISO Standard Pascal, EP=ISO Extended Pascal, BP= Borland Pascal, GNU. miklos _______________________ here_it_goes _____________ do DESCRIPTION: The "do" reserved word is used in combination with other Pascal key-words in many ways. Due to its diverse functionality no explanation is given here to avoid confusion. See the relevant reference sections for description and examples: for, while, with, to begin, to end. STANDARDS: SP, EP, BP, GNU. SEE ALSO: for, while, with, to begin, to end.

3 2

UNSUBCRIBE
by Geoffrey Arnold 12 Jun '98

12 Jun '98

PLEASE UNSUBCRIBE ME FROM THIS MAILING LIST ----------Geoffrey Arnold--------- ------garnold(a)cyberdrive.net------ http://www.cyberdrive.net/~garnold

1 0

Re: Semi-low level question...
by Frank Heckenbach 10 Jun '98

10 Jun '98

Orlando Llanes wrote: > Frank: > Sorry 'bout my rambling :} What I want to do is to reference all the > variables declared in an object via the stack. > > Peter: > I did dump a -S, but the problem is that the prolog code sets a couple > of registers to the address of the Self parameter, then later on in my > routine, when I try to access the variable, it points to an invalid > location in memory, because the register that was set with the address is > now pointing into space (my routine modifies all of the registers). I think all you have to do is declare those registers as clobbered. You can also specify input and output registers to you r assembler code, so you don't have to worry about whether it's stored on the stack or in some registers by the compiler. The compiler will put it into those registers where you want it. The exact syntax is described in the GPC assembler tutorial (I think the file name is gpcasm.txt, in some directory on Agnes). Frank -- Frank Heckenbach, frank(a)pascal.gnu.de http://fjf.gnu.de/ PGP and GPG keys: http://fjf.gnu.de/plan

1 0

gpc doesn't compile with egcs-19980608; patch appended
by Matthias Klose 09 Jun '98

09 Jun '98

gcc -DIN_GCC -DGPC -DEGCS -DHAIFA -s -o ../gpc1 \ `cat stamp-gbe` ../c-aux-info.o ../c-iterate.o ../c-pragma.o ../choose-temp.o ../pexecute.o gpc-common.o gpc-convert.o gpc-decl.o gpc-lang.o gpc-lex.o gpc-typeck.o module.o gpi-hash.o circle-buf.o objects.o parse.o rts.o types.o util.o setop.o version.o `if [ xobstack.o != x ]; then echo ../obstack.o; else true; fi` `case "gcc" in "cc") if [ x != x ]; then echo ../; else true; fi ;; esac` `if [ x != x ]; then echo ../; else true; fi` toplev.o: In function `main': toplev.o(.text+0x33b4): undefined reference to `lang_init_options' make[3]: *** [../gpc1] Error 1 *** gpc-lang.c.orig Tue Jun 9 15:47:29 1998 --- gpc-lang.c Tue Jun 9 15:48:00 1998 *************** *** 35,40 **** --- 35,45 ---- } void + lang_init_options () + { + } + + void lang_init () { #ifdef GPC

1 0

Semi-low level question...
by Orlando Llanes 09 Jun '98

09 Jun '98

Is there a way to specify to GPC, or for GPC to specify to AS, to reference Object fields (variables) using the stack rather than registers? The reason I ask is because my libs won't work as intended when variables are referenced via clobbered registers. I'm weary of making these variables globals because I intend to make them thread safe (somehow) eventually and owuld like each instance to have its own copy of the variables. Thanks in advance! See ya! Orlando Llanes "Meine Damen und Herren, Elvis hat soeben das Gebaeude verlassen!" "Look out fo' flyeeng feet" O__/ a010111t(a)bc.seflin.org \/|____. O <__. \/\> / \ ____________|___\______ http://ourworld.compuserve.com/homepages/Monkey414

2 2

Re: GPC REFERENCE
by richard.kerry＠quantel.com 08 Jun '98

08 Jun '98

Should the info attempt to be a Pascal language tutor ? ie. Should it cover FOR, WHILE, REPEAT etc. Surely most people coming to GPC will do so knowing Pascal from elsewhere. Since the world at large seems to prefer C (or Cobol), it seems to me that we don't need to worry too much about explaining the standard contructs as only those who have already chosen Pascal will be interested in GPC. If we do want to include standard constructs, we might derive our explanations from one of a number of existing books eg. Programming in Pascal, by Peter Grogono. (Addison-Wesley 0-201-12070-4). This book explains the FOR loop by its equivalent code using WHILE. I know this is copyright, but it (or similar) should give an idea how to explain these basic constructs. I think LALR(1) is the algorithm used for parsing. The syntax definition language is Backup-Naur Form, known as BNF. The Grogono book I mentioned doesn't use it, it uses syntax diagrams instead, but I'm sure someone can provide BNF for GPC. Whatever goes in should certainly be checked for English grammar and usage by a native speaker, or one of the German members of the list, who seem to write extremely good English. Regards, Richard.

5 5

Re: Semi-low level question...
by Frank Heckenbach 08 Jun '98

08 Jun '98

Orlando Llanes wrote: > Is there a way to specify to GPC, or for GPC to specify to AS, to > reference Object fields (variables) using the stack rather than registers? > The reason I ask is because my libs won't work as intended when variables > are referenced via clobbered registers. I'm weary of making these > variables globals because I intend to make them thread safe (somehow) > eventually and owuld like each instance to have its own copy of the > variables. Thanks in advance! I'm not sure I really understand your problem. Do your routines rely on no registers being clobbered by other routines? I don't think you could ever rely on this, because registers are used for other purposes, too. Perhaps declaring the variables "volatile" might help, but actually I don't think so. I don't think "volatile" is needed unless the variables are used in different threads at the same time or modified by hardware interrupts or such things. -- Frank Heckenbach, frank(a)pascal.gnu.de http://fjf.gnu.de/ PGP and GPG keys: http://fjf.gnu.de/plan

1 0

GRX graphics library v2.3 available
by Hartmut Schirmer 08 Jun '98

08 Jun '98

Hi, I uploaded GRX v2.3 on ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2tk (Mirrors see http://www.simtel.net/simtel.net/mirrors.html) and on the GRX pages at http://www.techfak.uni-kiel.de/~hsc/GRX/ What's GRX ---------- GRX is a low level graphics library designed for general purpose 2D graphics. It's designed to be portable (ANSI-C) and effective. In addition to the ANSI-C API it's possible to call GRX from other languages, an interface to GNU-Pascal comes with GRX. GRX is under the LGPL. Check out doc/copying.cb for details. Currently GRX is known to work on DOS systems (GCC+DJGPP, Borland C++, Watcom C++ 32bit) Linux systems (svgalib and X11) Unix systems (Sun, DEC, HP with X11R5 or newer) What's new in this release -------------------------- -- Thomas Hahn ported GRX to DEC alpha systems -- Ulrich Leodolter contributed his latest X11 driver. Several X11 problems (readpixel, color handling in pseudo color mode) are now. Additionally GRX will run on X11R5 systems now. -- Vincenzo Morello contributed the addons/ctx2jpeg source -- Andris Pavenis contributed the memory driver and the addons/print sources -- Gary Sands ported GRX to Watcom C++ (32bit, V11.0, other versions may work) -- Michal Stencl contributed the image handling code and the addons/bmp sources -- code portability has be greatly enlarged. GRX should be easily portable to new compilers now. -- BCC port should now work on _all_ Borland 16bit compilers (Tested with BCC 2.0, 3.1 and 4.52) -- GRX will work on big endian systems (sparc, AIX systems) -- GRX has 64bit support -- GRX uses a more flexible scheme for temporary memory allocation now. Depending system and the SMALL_STACK switch either alloca or malloc will be used. GRX allocates an internal buffer for blit blits, scanline return, etc now -- GRX supports a platform independant keyboard interface -- Nearly all frame drivers have be optimized for performance -- On Linux systems GRX can be build as shared lib -- New GRX functions: GrFloodFill GrGetScanline GrGetScanlineC GrPutScanline GrGetLibraryVersion GrGetLibrarySystem GrAllocEgaColors GrImage.... I wish to thank all of you for your continuing contributions to GRX. If you look at the list above, without your help this release would not have been possible. A special thank to Andris and Gary for testing nearly every new beta release, your feedback was extremely helpful! What's missing -------------- The GRX documentation is somewhat outdated. Other minor problems have been reported. Check out the GRX pages at http://www.techfak.uni-kiel.de/~hsc/GRX/ for more details. Hartmut Schirmer -- Hartmut Schirmer | Phone: +49-431-77572-709 FAX:-703 Automatisierungs- & Regelungstech. | hsc(a)techfak.uni-kiel.de Technische Fakult"at, | http://www.techfak.uni-kiel.de/~hsc Kaiserstr. 2, 24143 Kiel, Germany | PGP key via WWW, Key ID:6D84AEC1

1 0

UCE: PC-to-UNIX Connectivity Software
by info＠xlink.com 05 Jun '98

05 Jun '98

************************************************* Come see why Fortune 1000 Companies choose XLink for their PC-to-UNIX integration needs! ************************************************* We know you're busy so we'll be brief. :) XLink Technology, Inc. provides total networking software solutions for now and to the future Visit XLink Technology, Inc. @ http://www.xlink.com if you need help with the following... Total PC-to-UNIX integration software for the Windows Platforms: - NFS Client/Server - X-Windows - LPD/LPR - Terminal Emulation - All windows platforms - and more! Visit http://www.xlink.com for a FREE demo and more details! Thank you for your time. This is a one time mailing.

1 0

GPC REFERENCE: for
by Miklos Cserzo 04 Jun '98

04 Jun '98

for SYNTAX: for iteration_variable := initial_value to final_value do statement or for iteration_variable := initial_value downto final_value do statement DESCRIPTION: "for" is reserved word in all Pascal standards. It is used for introducing iterative loops during the execution. At the start of the loop the control variable set to the initial value then incremented by 1 after each execution step of the body of the "do" statement. The control variable should be an integer type. When the value of the control variable equals to the final value the execution continues at the next statement after the body of the "do". If the initial value and the final value are equal the loop executed ones. If the initial value higher than the final value the body of the "do" statement not executed. In the second form of the command the control variable decremented by 1 in each cycle. The relation of the initial and final values are reversed accordingly. The body of the "do" statement can contain other "for" cycles resulting nested loops. It is an error to set the value of the loop-control variable inside the loop. The code that violate that rule will compile and run - if there are no other errors - but the result will be unpredictable. After the execution of the loop the value of the control variable is undefined. A proper code should not relay on that value. STANDARDS: All EXAMPLE: var i,j,k:integer; vec:array[1..10] of integer; cube:array[1..10.1..10.1..10] of real; ... for i:= 1 to 10 do begin write('element [',i,']:? '); { prompt for the next value } readln(vec[i]); { read it } end; .... for i:= 1 to 10 do { load data from "infile" } for j:= 1 to 10 do begin for k:= 1 to 10 do read(infile,cube[i,j,k]); readln(infile); { next line } end; close(infile); SEE ALSO: do, while, repeat ________________________________ Comment this please. miklos

4 4

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