Gpc

gpc@gnu.de

5400 discussions

assert
by Adam Naumowicz 12 Mar '01

12 Mar '01

Hello, After compiling GPC from the current sources I noticed, that there appears a linking problem when using system unit and my own assert procedure, which was not the case with some precompiled binary distribution I used before. I understand that the routine is added for delphi compatibility, so is there a simple solution to eliminate it when running in --borland-pascal mode or I just have to rename my own procedure since the overloading is not working properly? Adam Naumowicz -------------------------------------- WWW: http://math.uwb.edu.pl/~adamn/ --------------------------------------

2 1

Timestamp format and calculations?
by Pernille Bech & Klaus F. Østergaard 11 Mar '01

11 Mar '01

type TimeStamp = {@@packed} record DateValid, TimeValid : Boolean; Year : Integer; Month : 1 .. 12; Day : 1 .. 31; DayOfWeek : 0 .. 6; { 0 means Sunday } Hour : 0 .. 23; Minute : 0 .. 59; Second : 0 .. 61; { to allow for leap seconds } MicroSecond : 0 .. 999999 end; Is there a function/procedure that calculates the DateValid and TimeValid. Does it proof the DayOfWeek? What is leap seconds and how does one calculate with leap seconds? Does any one know of standard libs/rutines for doing calculations/manipulations with the timestamp, like calculating the day of the week or finding time between two timestamps, with corrections to the diffent length of months ect. Thanks, Klaus

3 5

Re: Has class become a reserved word?
by david＠tcs01.demon.co.uk 10 Mar '01

10 Mar '01

In message <4C6E5C32.20010308193203.FOO-4495.frank(a)g-n-u.de> Frank Heckenbach writes: > Peter Gerwinski wrote: Having now looked at an 'Object Pascal Language Guide' that came with a copy of Borland Delphi for Windows, I'm not convinced that class is being handled in the Delphi manner. This Guide says "Unlike other types, a class type can be declared only in a type declaration part in the outermost scope of a program or unit. Therefore, a class type can't be declared in a variable declaration part or within a procedure, function, or method block." So an example similar to the example I posted last night: program test_class(input,output); type tcomp=packed record name:string[80]; class:1..15; end; var comp:tcomp; begin end. should fail. However, I think the following example: program test_class2(input,output); procedure proc; type tcomp=packed record name:string[80]; class:1..15; end; var comp:tcomp; begin end; begin proc; end. should compile (and it doesn't). I think the "news" section of the first part of the manual should document the introduction of class as a conditionally reserved word. For the moment Russ Whitaker's suggestion of {$define class thing} as a quick and dirty patch looks the easiest way for me to proceed with this upgrade. > > > The question is whether a separate switch, specifically for > > enabling/disabling keywords, makes sense. > > > > [...] I mean something like `--disable-keyword="Class"'. > > Perhaps accept a list of keywords, e.g. > `--disable-keywords="class,object"'. I like that scheme, since, as I posted earlier, I have source code which is such a collection of different dialects within single files that the dialect switches are no use to me. -- David James mailto:david@tcs01.demon.co.uk Special Stage Rally results archive <URL:http://www.tcs01.demon.co.uk/>

4 4

Re: Has class become a reserved word?
by david＠tcs01.demon.co.uk 10 Mar '01

10 Mar '01

In message <1F902E6F.20010309110245.FOO-6B42.frank(a)g-n-u.de> Frank Heckenbach writes: > David James wrote: > > > Having now looked at an 'Object Pascal Language Guide' that came with > > a copy of Borland Delphi for Windows, I'm not convinced that class is > > being handled in the Delphi manner. This Guide says "Unlike other > > types, a class type can be declared only in a type declaration part > > in the outermost scope of a program or unit. Therefore, a class type > > can't be declared in a variable declaration part or within a > > procedure, function, or method block." [snip] > > should compile (and it doesn't). > > I suppose that, while class declarations are allowed only globally > in the outermost scope, `class' is a reserved word throughout. > That's what the Chief said Delphi does, and what I know TP does with > `object'. I probably read too much into the section I quoted, what you say makes sense. > > We could try to make `class' conditionally reserved only in the > outermost scope, but I don't know how hard this would be (Peter?), But you probably shouldn't (for compatibility) if Delphi makes it reserved in places other than the outermost scope. > and it wouldn't solve the issue completely. So I think I'd prefer > `disable-keyword' as well... > > > I think the "news" section of the first part of the manual should > > document the introduction of class as a conditionally reserved word. > > I'm a little surprised. According my old copy of the 19990118 > sources, `class' was already conditionally reserved there. But > anywaym I will document it, Thank you. There's certainly been a change in behaviour between 19991030 and 20010306. > as well as `attribute' and `published' > which have become (conditional) keywords since that version AFAICT. > If there are more keywords I should mention, let me know. I've not come across any more, and I've now managed to compile our entire suite of programs under GPC 20010306. The next step is to see what happens when I try running them ... Have there been any changes in the packing of data in records or packed records between 19991030 and 20010306? Or any changes in the data transfer between variables and typed files (is that the correct name? I mean FILE OF Twhatever, where Twhatever is a TYPE defined in the source)? -- David James mailto:david@tcs01.demon.co.uk Special Stage Rally results archive <URL:http://www.tcs01.demon.co.uk/>

4 4

Where to place units from the RTS
by david＠tcs01.demon.co.uk 09 Mar '01

09 Mar '01

I've never really been clear on where units from the RTS are intended to be placed, and I'm even more uncertain now that I'm migrating from GPC 19991030 to GPC 20010306 ... Suppose I have a program that 'uses gpc' (one of the units from the GPC RTS). Where should gpc.o and gpc*.gpi be (this is under Linux)? And should they have been placed there by the make install when I built the compiler? I'd like to be able to say gpc prog.p and have it automatically find the gpc unit at compile time and at link time. At the moment I've put gpc.o and gpc*.gpi in the same directory as the program, and am specifying gpc.o in the command line, but there must be a neater way of doing it ... If this information is in either the GPC Info files (gpc.info*) or the INSTALL file, I've either not found it or not understood it. -- David James mailto:david@tcs01.demon.co.uk Special Stage Rally results archive <URL:http://www.tcs01.demon.co.uk/>

2 1

Re: Has class become a reserved word?
by david＠tcs01.demon.co.uk 09 Mar '01

09 Mar '01

In message <0873F763.20010309182845.FOO-3141.frank(a)g-n-u.de> Frank Heckenbach writes: [snip] > > > > The strict for keeping legacy apps running, the loose mode for > > interoperability. > > I don't see how this should solve Dave's problem. AFAIUH, he's using > "all" of GPC's features (i.e., not restricted to a particular > standard or dialect) and was only disturbed by a particular keyword. That's correct. This particular code started off in UCSD Pascal, was then migrated to Edinburgh Portable Compilers Extended Pascal (which complied with a subset of the *draft* Extended Pascal Standard, I think), and then migrated to GPC. In the migration to GPC (in late 1999) I found some Extended Pascal features we were using did not work reliably enough, and had to replace then by (probably) Borland/UCSD features. So it's a mismash ... [snip] > As I already said in other mails, I'd prefer some more options to > fine-tune the dialect (like --disable-keywords), so one doesn't have > to use a dialect option just because of one single issue (like in > this case). (Besides, those options are probably quite a bit easier > to implement than new dialect versions because they only affect > specific parts of the compiler.) As a user, that's my preference too. -- David James mailto:david@tcs01.demon.co.uk Special Stage Rally results archive <URL:http://www.tcs01.demon.co.uk/>

1 0

Has class become a reserved word?
by david＠tcs01.demon.co.uk 09 Mar '01

09 Mar '01

I'm trying to upgrade from gpc version 19991030 to 20010306 both based on 2.95.2 19991024 (released). I've found the change in the positioning of 'asmname', and the removal of the 'char-escapes' directive. It looks as if 'class' has become a reserved word, which is unfortunate as it is a variable name our code uses frequently. First question: is class now reserved in some way? Second question: is there any easy way for me to disable this? Unfortunately I don't think specifying the Pascal dialect (using --extended-pascal, --borland-pascal, etc) will help me because the source code uses a mixture of dialects often in the same file. Is going throughthe source and changing all occurrences of class into something else going to be my easiest course of action? Third question: any thoughts on whether there any other syntax changes I might trip over? David -- David James mailto:david@tcs01.demon.co.uk Special Stage Rally results archive <URL:http://www.tcs01.demon.co.uk/>

6 10

GNU Pascal Anfänger
by Dieter Schmitz 08 Mar '01

08 Mar '01

Hallo, Bin mir nicht sicher welche Sprache auf dieser Liste gesprochen, da die GNU Pascal Seite kommplett in Englisch ist und ich von der Liste noch keine Mails bekommen hab, ich versichs einfach mal mit Deutsch. Ich bin gerade dabei in GNU Pascal einzusteigen und hatte vorher auch nie mit einer Programmiersprache zu tun. Jetzt suche ich ein biÃchen Dokumentation daz, kennt jemand von euch gute deutsche Dokumnetion zu GNU Pascal? Ich hab schÃ¶n einige BÃ¼cher und Dokumentationen zu Pascal gesehn, kann ich diese auch zum lernen von GNU Pascal verwenden? GruÃ Dieter

5 7

Re: Timestamp format and calculations?
by Tom Verhoeff 08 Mar '01

08 Mar '01

Eike Lange wrote: >IMHO, you should write the unit. We could perhaps improve the unit by >conversions of date/time formats, used in special cases like >"flight-sheduling". AFAIK do the airports calculate an hour based on 100 >"Ticks?" (like swatch-thee-beep :). Maybe, there are some more date/time >calculations available for some special purpose. Here is a wonderful reference for all your calendrical calculations: http://www.amazon.com/exec/obidos/ISBN=0521777526/theinternationscA/ One reviewer noted, however, that this is An excellent book on the history and workings of various calendars. But don't use the source code! The licensing agreement is a trap. Use the code in GNU Emacs from the Free Software Foundation distributed under the General Public License. It does everything the authors code does (except for two obscure calendars) and it's free and always will be. Success, Tom Verhoeff

1 0

RE: Timestamp format and calculations?
by Klaus Friis Østergaard 08 Mar '01

08 Mar '01

I have been looking at the code my self and I think I can rewrite in Pascal, so it fits to the timestamp format. Should I write the code a stand a lone lib and sent it to Frank Heckenbach/Peter Gerwinski or just to the list and then the person that maintains the GPC unit would cut and past it into the unit? Kind Regards, Klaus F. Ãstergaard -----Original Message----- From: Pernille Bech & Klaus F. Ãstergaard [mailto:farremosen@mail.tele.dk] Sent: Monday, March 05, 2001 11:29 PM To: gpc(a)gnu.de Subject: Sv: Timestamp format and calculations? I have been looking for a lib with date calculations, and found this C/PERL lib. As I don't know anything about C and how you make C work together with GPC, could some of you please look at the lib to see if it is an easier way to get more functional lib than starting all over in pascal. http://www.engelschall.com/u/sb/download/ I think this lib contains some nice routines to convert from different date/time notations, also including different languages for text name on dayes, months, converting to and from normal date and business (year week day) format ect. Hope this can help improve GPC kind regards, Klaus F. Ãstergaard ----- Original Message ----- From: Frank Heckenbach <frank(a)g-n-u.de> To: <gpc(a)gnu.de> Sent: Saturday, March 03, 2001 9:00 AM Subject: Re: Timestamp format and calculations? > Eike Lange wrote: > > > On Mon, Feb 26, 2001 at 07:04:38AM +0100, Frank Heckenbach wrote: > > > A routine to check a given date (with or without checking DayOfWeek) > > > would be nice, and I might write it someday (too busy right now), > > > but if you have such a routine to contribute, let me know... > > > > We have such in our GLib-Unit, GDateValid(...). Just wait a few days :-) > > I looked at it. But it operates on a different type (PGDate). > Converting to and from it, and linking glib is probably much more > effort than writing the function in Pascal which shouldn't take more > than a few lines. (I don't mean to put down the project, but using a > set of date/time routines that operate on yet another type (as if > there weren't more than enough already) is probably not such a good > idea unless one is porting a C program that uses glib already...) > > BTW, when I looked at the unit, I saw > `function GPOINTER_TO_INT(x : Pointer) : Integer;' at the end. > That's very dangerous. If you have to cast between pointers and > integers at all for some reason, use PtrInt or PtrCard which is > guaranteed to have the same size. On some 64 bit platforms, Integer > is still 32 bit and Pointer is 64 bit, so this routine is a sure way > to produce invalid addresses. (I don't know if glib uses `int' where > it accepts pointers, but if it does, it's not 64 bit safe, > either...) > > 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 >

2 1

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