Gpc

gpc@gnu.de

5400 discussions

Re: Known GPC bugs
by JanJaap van der Heijden 07 Oct '96

07 Oct '96

At 12:57 PM 9/23/96 +0200, you wrote: >Hello folks, > >I updated the "known bugs" section of the Texinfo documentation >of the (experimental) gpc-1.2-2.7.2 pre-release. The new file >"bugs.texi" can be found at > Maybe we should get one of those systems where people can file bug reports in HTML forms. I have seen these before, but can't remember ever having seen a ready-to-go distribution. Anybody got any ideas? JanJaap -- The latest & greates in software, hardware and manswear -- Bono Vox (U2)

2 1

OS/2 PM programs and DLL's
by Peter Gerwinski 07 Oct '96

07 Oct '96

According to Allan Derickson: > Is it possible at this point to make OS/2 Presentation Manager programs > with GNU Pascal? Yes, just as with GNU C in the EMX environment. Look into the EMX documentation and example programs (written in C). Use the "asmname" directive to access OS/2 API functions. I will release a version of BO5 which runs with the OS/2 pm not too far in the future. Peter e-mail: peter.gerwinski(a)uni-essen.de home address: D\"usseldorfer Str. 35, 45145 Essen, Germany WWW: http://agnes.dida.physik.uni-essen.de/~peter/

1 0

OS/2 PM programs and DLL's
by alland＠whidbey.com 06 Oct '96

06 Oct '96

Hello, Is it possible at this point to make OS/2 Presentation Manager programs with GNU Pascal? Same question with OS/2 DLL's. If so, what is the format of the code? I have been totally unsuccessful with both. Allan D. Derickson -- Derickson Forestry Services -- Freeland, WA USA ----------------------------------------------------------- alland(a)whidbey.com -----------------------------------------------------------

1 0

subscribe sixconse@sc.ehu.es
by Ikasle Kontseilua 05 Oct '96

05 Oct '96

subscribe sixconse(a)sc.ehu.es

1 0

Double and uses...
by Peter Gerwinski 04 Oct '96

04 Oct '96

According to Alessandro Graizzaro: > I'm new with gnu pascal, and with Linux too. > I decided to try it, because I need a lot of memory for my computations. > 1) Can anoybody of tell me how can I define DOUBLE type ? "Real" *is* what you know as "Double" from Borland Pascal. Borland's 6-byte software real does not exist with GNU; "Single" is "__short__ Real", "Extended" is "__long__ Real". Known bug: you cannot writeln __short__ or __long__ Reals at the moment, but have to convert them to "ordinary" Reals, first. > 2) Is it possible to use the USES clause as in TP ? Yes. See README.TURBO for details (2.6.3 version) or the "From Borland to GNU Pascal" section of the INFO documentation of the 2.7.2-beta version. > Where to find something > like CRT, GRAPH ...? Graph is worked on for the DOS platform. For Linux, you can use the VGAlib C library with "external", "C", and "asmname" Procedures and Functions. CRT does not yet exist -- we are looking for somebody to implement it. However, have a look at BO5 (in the turbo-alpha directory). Its "Events" and "Displays" Units provide important parts of CRT's functionality. Hope this helps, Peter e-mail: peter.gerwinski(a)uni-essen.de home address: D\"usseldorfer Str. 35, 45145 Essen, Germany WWW: http://agnes.dida.physik.uni-essen.de/~peter/

1 0

Double and uses...
by Alessandro Graizzaro 04 Oct '96

04 Oct '96

-- [ From: Alessandro Graizzaro * EMC.Ver #2.5.02 ] -- I'm new with gnu pascal, and with Linux too. I decided to try it, because I need a lot of memory for my computations. 1) Can anoybody of tell me how can I define DOUBLE type ? 2) Is it possible to use the USES clause as in TP ? Where to find something like CRT, GRAPH ...?

1 0

BUG: gpc and type modifiers.
by J.J. van der Heijden 03 Oct '96

03 Oct '96

I discovered a bug in the way GPC treats type modifiers: Consider this snippet, for a 32bit architecture: ------------------------------------------- type uint = __unsigned__ integer; { unsigned 32-bit } const c1 : uint = $7FFFFFFF ; { maxint } c2 : uint = $80000000 ; ------------------------------------------- The declaration of c2 gives this error message: `integer constant does not fit in integer type' while this faulty snippet is accepted: ------------------------------------------- type short = __short__ integer; { signed 16-bit } const c3 : short = $FFFF ; c4 : short = $00010000 ; ------------------------------------------- Although c4 gives a warning: `warning: overflow in implicit constant conversion' Obviously, GPC doesn't treat the type modifiers the right way when it evaluates whether a constant is valid or not. The same is true for __longlong__ (64bit), which cannot be initialized with a value > $7FFFFFFF. Workaround ========== With this silly trick it's still possible to assign an unsigned 32bit value: ------------------------------------------- type uint = __unsigned__ integer; { unsigned 32-bit } const c1 : uint = $7FFFFFFF + 1; ------------------------------------------- This gives again: `warning: overflow in implicit constant conversion' which can be suppressed by surrounding the declaration with {$W-} .. {$W+} JanJaap --- "Nothing shocks me, I'm a scientist", Indiana Jones

1 0

patch for linking-dumps-core problems
by J.J. van der Heijden 02 Oct '96

02 Oct '96

Somebody asked for it, so here it is, the patch for the `linking only dumps core' problem. It was a strcpy() with NULL source problem. Apply it, then rebuild the `gpc' driver program. Greetings, JanJaap *** gpc-1.2-2.7.2/gcc.c Tue Aug 20 21:59:57 1996 --- gpc/gcc.c Tue Sep 24 01:08:44 1996 *************** *** 4976,4980 **** putenv (obstack_finish (&collect_obstack)); ! #ifdef __EMX__ /* Substitute the basename of the first input file for %b in link_command_spec. */ --- 4978,4982 ---- putenv (obstack_finish (&collect_obstack)); ! #ifdef GPC /* Substitute the basename of the first input file for %b in link_command_spec. */ *************** *** 4992,4998 **** if (*p == '.' && p != input_basename) basename_length = p - input_basename; - #endif /* __EMX__ */ - #ifdef GPC explicit_link_files = add_automake_files (explicit_link_files); #endif /* GPC*/ --- 4994,4998 ---- --- "Nothing shocks me, I'm a scientist", Indiana Jones

1 0

ANNOUNCE: new win32 GPC binary available.
by J.J. van der Heijden 02 Oct '96

02 Oct '96

The latest cygwin32-compatible GNU Pascal binary is now available from: ftp://agnes.dida.physik.uni-essen.de/home/janjaap/cygwin32/ I keep this seperate from the main release directory because some things have to be done before the next all-platform release. Still, the win32 GPC has improved enough that I think you should all try it out. Files in this directory: gpc-960930-2.7.2.i386-cygwin32-b16.zip Sep.30 snapshot binary of cygwin32 GPC. For a cygwin32-beta16 toolchain. devtools.i386-cygwin32-b16.zip For those who only want to do Pascal, it's a waist to download a complete toolchain from ftp.cygnus.com. This archive has all the tools (as, ld, libraries) needed to complete GPC. If you already have cygwin32-beta16 installed, you don't need this. Changes ------- Since the last release (gpc-1.2-2.7.2.i386-cygwin32-b14.zip), these things have changed: * Now beta16 compatible. * Fixed internal fork() problems, now --automake works. * Pipes (`gpc -pipe ...') supported. * Binary/text file IO problem fixed. * Some new test programs. * Support for function attributes and multiple directives per function declaration. Effectively, this means this GPC can access the Win32 API and build both GUI and console applications! Thanks, Peter. See the demos in the "test\windows" subdirectory. Installation ------------ * create a subdirectory of your choice (`c:\gpcwin32') and unzip gpc-960930-2.7.2.i386-cygwin32-b16.zip and devtools.i386-cygwin32-b16.zip from there. Use a version of `unzip' that can handle long filenames, i.e. not PKunzip. * Add the directory where `gpc.exe' lives (`c:\gpcwin32\bin') to your path. * Set GCC_EXEC_PREFIX=C:\gpcwin32\lib\gcc-lib\ Beware of the trailing slash! * Set LIBRARY_PATH=c:\gpcwin32\lib;c:\gpcwin32\i386-cygwin32\lib Not yet done ------------ GPC has incomplete support for the `stabs' debugging format. This affects the win32 platform (and all ELF unices). Although you can step your program in GDB, it may lose track of where you really are, be unable to display variables etc. I'm working on this. The function attributes and asmname directives seem to get lost in the GPI mechanism, so you will have to #include `units' for now, if they define WinAPI type functions. Other problems -------------- These things often give problems: * Do NOT mix binaries from different beta's -- they are incompatible. * Be sure to have only one `cygwin.dll' in your path and it must be beta16. The symptoms of these are crashes, stack/register dumps and Windows telling you it cannot load a dll. Read the cygwin32 FAQ (http://www.cygnus.com/ or this directory) Most of the information also applies for GNU Pascal. And please, do not bother the people of the cygwin32 mailinglist if you have problems with GPC, send them to the gpc(a)hut.fi list instead. Have fun, JanJaap <j.j.vanderheijden(a)student.utwente.nl> --- "Nothing shocks me, I'm a scientist", Indiana Jones

1 0

Subscription to your mailing list
by premiere＠askesis.it 02 Oct '96

02 Oct '96

Hi, I'm a Student in Computer Programming at University (Milan,Italy). I,ve downloaded Gnu Pascal Compiler and I've given it to my Teacher. Their comments are Enthusiastic! Please , add my E-mail Address to your mailing list. Thanx a lot. HardPile.

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