Gpc

gpc@gnu.de

5400 discussions

Re: [RFC] Handle GPC specific name for main function
by Pierre Muller 26 Sep '07

26 Sep '07

Sorry, Could you please point me again to the right place for comment formatting? I remember that single line is different from multi-line, and that multi-line comments should end with a point and two spaces before the closing '*/' http://www.gnu.org/prep/standards/ does not seem very explicit about this, unless I did not find the right place inside... Concerning the comment below, should it be 1) /* For GPC, main procedure has a special name */ 2) /* For GPC, main procedure has a special name. */ or something else? Pierre > -----Original Message----- > From: Eli Zaretskii [mailto:eliz@gnu.org] > Sent: Wednesday, September 26, 2007 5:04 PM > To: Pierre Muller > Cc: gdb-patches(a)sourceware.org; gpc(a)gnu.de > Subject: Re: [RFC] Handle GPC specific name for main function > > > From: "Pierre Muller" <muller(a)ics.u-strasbg.fr> > > Cc: <gpc(a)gnu.de> > > Date: Wed, 26 Sep 2007 16:40:30 +0200 > > > > + /* For GPC, main procedure s a special name. > > + . */ > > What happened here? this comment is not formatted according to GNU > coding style.

2 1

Question about fields alignment
by Pascal Viandier 21 Sep '07

21 Sep '07

Hi, I have a question about field's alignment in GNU Pascal records on different platforms. Consider the sample program below: Program offsets; Type Rec1_t = Record Str16 : String(16); R : Real; End; Rec2_t = Record Str11 : String(11); Rec1 : Rec1_t; End; Rec3_t = Record Str11 : String(11); Str16 : String(16); R : Real; End; Var Rec1 : Rec1_t; Rec2 : Rec2_t; Rec3 : Rec3_t; Begin WriteLn('Offset of Str11 in Rec2 : ', LongInt((a)Rec2.Str11) - LongInt(@Rec2)); WriteLn('Offset of Rec1 in Rec2 : ', LongInt((a)Rec2.Rec1) - LongInt(@Rec2)); WriteLn('Offset of Str16 in Rec2 : ', LongInt((a)Rec2.Rec1.Str16) - LongInt(@Rec2)); WriteLn('Offset of R in Rec2 : ', LongInt((a)Rec2.Rec1.R) - LongInt(@Rec2)); WriteLn; WriteLn('Offset of Str11 in Rec3 : ', LongInt((a)Rec3.Str11) - LongInt(@Rec3)); WriteLn('Offset of Str16 in Rec3 : ', LongInt((a)Rec3.Str16) - LongInt(@Rec3)); WriteLn('Offset of R in Rec3 : ', LongInt((a)Rec3.R) - LongInt(@Rec3)); End. When compiled under X86 linux: dibm0014:/home/gnu-port/tests$ gpc --version gpc 20050331, based on gcc-3.4.5 20050821 (prerelease) (Debian 3.4.4-8) Copyright (C) 2005 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. The program produces the following results: Offset of Str11 in Rec2 : 0 Offset of Rec1 in Rec2 : 20 Offset of Str16 in Rec2 : 20 Offset of R in Rec2 : 48 Offset of Str11 in Rec3 : 0 Offset of Str16 in Rec3 : 20 Offset of R in Rec3 : 48 This looks good to me. Rec1 and Rec3 map on each other. However when compiled under SUN Sparc Solaris 10, the same program produces this result: <gnu-pascal> gpc --version gpc 20051116, based on gcc-3.4.4 Copyright (C) 2005 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. <gnu-pascal> offsets Offset of Str11 in Rec2 : 0 Offset of Rec1 in Rec2 : 24 Offset of Str16 in Rec2 : 24 Offset of R in Rec2 : 56 Offset of Str11 in Rec3 : 0 Offset of Str16 in Rec3 : 20 Offset of R in Rec3 : 48 So my question is: How come the difference in alignment of Rec1 in Rec2 between Sparc and Linux? I know that Real data is aligned on 8 bytes boundaries on Sparc platforms but why is the address of Rec1 aligned on 8 bytes instead of 4? So the two records (Rec2 and Rec3) containing the same data are of different sizes and do not map anymore. This causes some trouble in my programs since this kind of data structures are passed back and forth to C code, in order to interface with a database engine. This difference does not happen if there is no Real in the sub-structure. I can manage this with 'dummy' fields in record declarations - enclosed in {$ifdef }...{$endif} but I would like to be sure to understand how the alignment is done in order to avoid recurrent problems on this matter. Kind regards Pascal Viandier

3 2

New gpc snapshot released
by Waldek Hebisch 20 Sep '07

20 Sep '07

I have put a new gpc snapshot at: http://www.math.uni.wroc.pl/~hebisch/gpc-20070904.tar.bz2 This snaphshot contains mostly bugfixes. Main feature is that gcc-4.1.x support is now integrated. NOTE: there is a change of licence: this snapshot uses GPL version 3. For new features see: http://www.math.uni.wroc.pl/~hebisch/gpc/NEWS-20070904 and for fixed bugs: http://www.math.uni.wroc.pl/~hebisch/gpc/Fixed-20070904 -- Waldek Hebisch hebisch(a)math.uni.wroc.pl

8 37

Re: New gpc snapshot released
by Waldek Hebisch 08 Sep '07

08 Sep '07

I wrote: > I have put a new gpc snapshot at: > > http://www.math.uni.wroc.pl/~hebisch/gpc-20070904.tar.bz2 Sorry for wrong link, the snapshot is at: http://www.math.uni.wroc.pl/~hebisch/gpc/gpc-20070904.tar.bz2 -- Waldek Hebisch hebisch(a)math.uni.wroc.pl

2 3

[RFC] adding gdb.pascal subdir: updated version
by Pierre Muller 07 Sep '07

07 Sep '07

I resend here the result of some discussion with Daniel to add a new directory to test pascal language features. I updated the headers to the new GNU v3 licence and used gdb_get_line_number function as suggested by Daniel. The current patch adds one failure to gdb testsuite if the compiler is Free Pascal and three failures if it it GNU pascal, the increase is related to GNU Pascal specific startup code that is not yet recognized by gdb. The common error has to do with pascal strings. It is not an easy issue to solve because pascal string are using single quotes, but single quotes are also used for specific purpose inside the gdb expression parser, and I do not want to alter this behavior. Comments are most welcome as always, Pierre Muller 2007-09-08 Pierre Muller <muller(a)ics.u-strasbg.fr> Daniel Jacobowitz <dan(a)codesourcery.com> * Makefile.in (ALL_SUBDIRS): Add gdb.pascal. * configure.ac (AC_OUTPUT): Add gdb.pascal/Makefile. * configure: Regenerated. * gdb.pascal/Makefile.in, gdb.pascal/hello.exp, gdb.pascal/hello.pas, gdb.pascal/types.exp, lib/pascal.exp: New files. Index: Makefile.in =================================================================== RCS file: /cvs/src/src/gdb/testsuite/Makefile.in,v retrieving revision 1.18 diff -u -p -r1.18 Makefile.in --- Makefile.in 27 Mar 2007 18:09:35 -0000 1.18 +++ Makefile.in 7 Sep 2007 21:46:12 -0000 @@ -37,7 +37,7 @@ RPATH_ENVVAR = @RPATH_ENVVAR@ ALL_SUBDIRS = gdb.ada gdb.arch gdb.asm gdb.base gdb.cp gdb.disasm \ gdb.dwarf2 \ gdb.fortran gdb.server gdb.java gdb.mi \ - gdb.objc gdb.threads gdb.trace gdb.xml \ + gdb.objc gdb.pascal gdb.threads gdb.trace gdb.xml \ $(SUBDIRS) EXPECT = `if [ -f $${rootme}/../../expect/expect ] ; then \ Index: configure =================================================================== RCS file: /cvs/src/src/gdb/testsuite/configure,v retrieving revision 1.23 diff -u -p -r1.23 configure --- configure 23 Jan 2007 17:11:54 -0000 1.23 +++ configure 7 Sep 2007 21:46:24 -0000 @@ -3102,7 +3102,7 @@ done - ac_config_files="$ac_config_files Makefile gdb.ada/Makefile gdb.arch/Makefile gdb.asm/Makefile gdb.base/Makefile gdb.cp/Makefile gdb.disasm/Makefile gdb.dwarf2/Makefile gdb.fortran/Makefile gdb.server/Makefile gdb.java/Makefile gdb.mi/Makefile gdb.objc/Makefile gdb.threads/Makefile gdb.trace/Makefile gdb.xml/Makefile" + ac_config_files="$ac_config_files Makefile gdb.ada/Makefile gdb.arch/Makefile gdb.asm/Makefile gdb.base/Makefile gdb.cp/Makefile gdb.disasm/Makefile gdb.dwarf2/Makefile gdb.fortran/Makefile gdb.server/Makefile gdb.java/Makefile gdb.mi/Makefile gdb.objc/Makefile gdb.pascal/Makefile gdb.threads/Makefile gdb.trace/Makefile gdb.xml/Makefile" cat >confcache <<\_ACEOF # This file is a shell script that caches the results of configure # tests run on this system so they can be shared between configure Index: configure.ac =================================================================== RCS file: /cvs/src/src/gdb/testsuite/configure.ac,v retrieving revision 1.7 diff -u -p -r1.7 configure.ac --- configure.ac 23 Aug 2007 17:58:44 -0000 1.7 +++ configure.ac 7 Sep 2007 21:46:24 -0000 @@ -113,6 +113,6 @@ AC_OUTPUT([Makefile \ gdb.arch/Makefile gdb.asm/Makefile gdb.base/Makefile \ gdb.cp/Makefile gdb.disasm/Makefile gdb.dwarf2/Makefile \ gdb.fortran/Makefile gdb.server/Makefile \ - gdb.java/Makefile gdb.mi/Makefile \ - gdb.objc/Makefile gdb.threads/Makefile gdb.trace/Makefile \ + gdb.java/Makefile gdb.mi/Makefile gdb.objc/Makefile \ + gdb.pascal/Makefile gdb.threads/Makefile gdb.trace/Makefile \ gdb.xml/Makefile]) Index: gdb.pascal/Makefile.in =================================================================== RCS file: gdb.pascal/Makefile.in diff -N gdb.pascal/Makefile.in --- /dev/null 1 Jan 1970 00:00:00 -0000 +++ gdb.pascal/Makefile.in 7 Sep 2007 21:46:31 -0000 @@ -0,0 +1,24 @@ +VPATH = @srcdir@ +srcdir = @srcdir@ + +EXECUTABLES = hello/hello + +MISCELLANEOUS = + +all info install-info dvi install uninstall installcheck check: + @echo "Nothing to be done for $@..." + +clean mostlyclean: + -find . -name '*.o' -print | xargs rm -f + -find . -name '*.ali' -print | xargs rm -f + -find . -name 'b~*.ad[sb]' -print | xargs rm -f + -rm -f *~ a.out xgdb *.x *.ci *.tmp + -rm -f *~ *.o a.out xgdb *.x *.ci *.tmp + -rm -f core core.coremaker coremaker.core corefile $(EXECUTABLES) + -rm -f $(MISCELLANEOUS) twice-tmp.c + +distclean maintainer-clean realclean: clean + -rm -f *~ core + -rm -f Makefile config.status config.log + -rm -f *-init.exp + -rm -fr *.log summary detail *.plog *.sum *.psum site.* Index: gdb.pascal/hello.exp =================================================================== RCS file: gdb.pascal/hello.exp diff -N gdb.pascal/hello.exp --- /dev/null 1 Jan 1970 00:00:00 -0000 +++ gdb.pascal/hello.exp 7 Sep 2007 21:46:31 -0000 @@ -0,0 +1,72 @@ +# Copyright 2007 Free Software Foundation, Inc. +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 3 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, see <http://www.gnu.org/licenses/>. + +if $tracelevel then { + strace $tracelevel +} + +load_lib "pascal.exp" + +set testfile "hello" +set srcfile ${testfile}.pas +set binfile ${objdir}/${subdir}/${testfile} + +if {[gdb_compile_pascal "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable [list debug ]] != "" } { + return -1 +} + +gdb_exit +gdb_start +gdb_reinitialize_dir $srcdir/$subdir +gdb_load ${binfile} +set bp_location1 [gdb_get_line_number "set breakpoint 1 here"] +set bp_location2 [gdb_get_line_number "set breakpoint 2 here"] + +if { [gdb_breakpoint ${srcfile}:${bp_location1}] } { + pass "setting breakpoint 1" +} +if { [gdb_breakpoint ${srcfile}:${bp_location2}] } { + pass "setting breakpoint 2" +} + +# Verify that "start" lands inside the right procedure. +if { [gdb_start_cmd] < 0 } { + untested start + return -1 +} + +# This test fails for gpc +# because debug information for 'main' +# is in some <implicit code> +gdb_test "" \ + ".* at .*hello.pas.*" \ + "start" + +gdb_test "cont" \ + "Breakpoint .*:${bp_location1}.*" \ + "Going to first breakpoint" +gdb_test "print st" \ + ".* = ''.*" \ + "Empty string check" + +# This test also fails for gpc because the program +# stops after the string has been written +# while it should stop before writing it +gdb_test "cont" \ + "Breakpoint .*:${bp_location2}.*" \ + "Going to second breakpoint" +gdb_test "print st" \ + ".* = 'Hello, world!'.*" \ + "String after assignment check" Index: gdb.pascal/hello.pas =================================================================== RCS file: gdb.pascal/hello.pas diff -N gdb.pascal/hello.pas --- /dev/null 1 Jan 1970 00:00:00 -0000 +++ gdb.pascal/hello.pas 7 Sep 2007 21:46:31 -0000 @@ -0,0 +1,15 @@ +program hello; + +var + st : string; + +procedure print_hello; +begin + Writeln('Before assignment'); { set breakpoint 1 here } + st:='Hello, world!'; + writeln(st); {set breakpoint 2 here } +end; + +begin + print_hello; +end. Index: gdb.pascal/types.exp =================================================================== RCS file: gdb.pascal/types.exp diff -N gdb.pascal/types.exp --- /dev/null 1 Jan 1970 00:00:00 -0000 +++ gdb.pascal/types.exp 7 Sep 2007 21:46:31 -0000 @@ -0,0 +1,109 @@ +# Copyright 1994, 1995, 1997, 1998, 2007 Free Software Foundation, Inc. +# Copyright 2007 Free Software Foundation, Inc. +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 3 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, see <http://www.gnu.org/licenses/>. + +# Please email any bugs, comments, and/or additions to this file to: +# bug-gdb(a)prep.ai.mit.edu + +# This file was adapted from old Chill tests by Stan Shebs +# (shebs(a)cygnus.com). +# Adapted to pascal by Pierre Muller + +if $tracelevel then { + strace $tracelevel +} + +set prms_id 0 +set bug_id 0 + +# Set the current language to pascal. This counts as a test. If it +# fails, then we skip the other tests. + +proc set_lang_pascal {} { + global gdb_prompt + + if [gdb_test "set language pascal" ""] { + return 0; + } + + if ![gdb_test "show language" ".* source language is \"pascal\".*"] { + return 1; + } else { + return 0; + } +} + +proc test_integer_literal_types_accepted {} { + global gdb_prompt + + # Test various decimal values. + # Should be integer*4 probably. + gdb_test "pt 123" "type = int" +} +proc test_character_literal_types_accepted {} { + global gdb_prompt + + # Test various character values. + + gdb_test "pt 'a'" "type = char" +} + +proc test_string_literal_types_accepted {} { + global gdb_prompt + + # Test various character values. + + gdb_test "pt 'a simple string'" "type = string" +} + +proc test_logical_literal_types_accepted {} { + global gdb_prompt + + # Test the only possible values for a logical, TRUE and FALSE. + + gdb_test "pt TRUE" "type = bool" + gdb_test "pt FALSE" "type = bool" +} + +proc test_float_literal_types_accepted {} { + global gdb_prompt + + # Test various floating point formats + + # this used to guess whether to look for "real*4" or + # "real*8" based on a target config variable, but noone + # maintained it properly. + + gdb_test "pt .44" "type = double" + gdb_test "pt 44.0" "type = double" + gdb_test "pt 10e20" "type = double" + gdb_test "pt 10E20" "type = double" +} + +# Start with a fresh gdb. + +gdb_exit +gdb_start +gdb_reinitialize_dir $srcdir/$subdir + +if [set_lang_pascal] then { + test_integer_literal_types_accepted + test_logical_literal_types_accepted + test_character_literal_types_accepted + test_string_literal_types_accepted + test_float_literal_types_accepted +} else { + warning "$test_name tests suppressed." 0 +} Index: lib/pascal.exp =================================================================== RCS file: lib/pascal.exp diff -N lib/pascal.exp --- /dev/null 1 Jan 1970 00:00:00 -0000 +++ lib/pascal.exp 7 Sep 2007 21:46:32 -0000 @@ -0,0 +1,152 @@ +# Copyright 2007 Free Software Foundation, Inc. +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 3 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, see <http://www.gnu.org/licenses/>. + +load_lib libgloss.exp + +set pascal_init_done 0 + +# This procedure looks for a suitable pascal compiler +# For now only GNU pascal compiler and Free Pascal compiler +# are searched. +# First, environment variable GPC is checked +# if present, GPC compiler is assumed to be the value of +# that environment variable. +# Second, environment variable FPC is checked +# if present, Free Pascal compiler is assumed to be the value of +# that environment variable. +# Third, gpc executable is searched using `which gpc` +# Lastly, fpc executable is searched using `which fpc` +# Using environment variable allows to force +# which compiler is used in testsuite + +proc pascal_init {} { + global pascal_init_done + global pascal_compiler_is_gpc + global pascal_compiler_is_fpc + global gpc_compiler + global fpc_compiler + global env + + if { $pascal_init_done == 1 } { + return + } + + set pascal_compiler_is_gpc 0 + set pascal_compiler_is_fpc 0 + set gpc_compiler [transform gpc] + set fpc_compiler [transform fpc] + + if ![is_remote host] { + if { [info exists env(GPC)] } { + set pascal_compiler_is_gpc 1 + set gpc_compiler $env(GPC) + verbose -log "Assuming GNU Pascal ($gpc_compiler)" + } elseif { [info exists env(FPC)] } { + set pascal_compiler_is_fpc 1 + set fpc_compiler $env(FPC) + verbose -log "Assuming Free Pascal ($fpc_compiler)" + } elseif { [which $gpc_compiler] != 0 } { + set pascal_compiler_is_gpc 1 + verbose -log "GNU Pascal compiler found" + } elseif { [which $fpc_compiler] != 0 } { + set pascal_compiler_is_fpc 1 + verbose -log "Free Pascal compiler found" + } + } + set pascal_init_done 1 +} + +proc gpc_compile {source dest type options} { + global gpc_compiler + set add_flags "" + if {$type == "object"} { + append add_flags " -c" + } + + if { $type == "preprocess" } { + append add_flags " -E" + } + + if { $type == "assembly" } { + append add_flags " -S" + } + + foreach i $options { + if { $i == "debug" } { + if [board_info $dest exists debug_flags] { + append add_flags " [board_info $dest debug_flags]"; + } else { + append add_flags " -g" + } + } + } + + set result [remote_exec host $gpc_compiler "-o $dest --automake $add_flags $source"] + return $result +} + +proc fpc_compile {source dest type options} { + global fpc_compiler + set add_flags "" + if {$type == "object"} { + append add_flags " -Cn" + } + + if { $type == "preprocess" } { + return "Free Pascal can not preprocess" + } + + if { $type == "assembly" } { + append add_flags " -al" + } + + foreach i $options { + if { $i == "debug" } { + if [board_info $dest exists debug_flags] { + append add_flags " [board_info $dest debug_flags]"; + } else { + append add_flags " -g" + } + } + } + + set result [remote_exec host $fpc_compiler "-o$dest $add_flags $source"] + return $result +} + +proc gdb_compile_pascal {source dest type options} { + global pascal_init_done + global pascal_compiler_is_gpc + global pascal_compiler_is_fpc + + if { $pascal_init_done == 0 } { + pascal_init + } + + if { $pascal_compiler_is_fpc == 1 } { + set result [fpc_compile $source $dest $type $options] + } elseif { $pascal_compiler_is_gpc == 1 } { + set result [gpc_compile $source $dest $type $options] + } else { + unsupported "No pascal compiler found" + return "No pascal compiler. Compilation failed." + } + + if ![file exists $dest] { + unsupported "Pascal compilation failed: $result" + return "Pascal compilation failed." + } +} +

1 1

Re: New gpc snapshot released
by Russell Whitaker 07 Sep '07

07 Sep '07

Hi Results here: Native configuration is i686-pc-linux-gnu (bigred) === gpc tests === Running target any Running testsuite ... UNSUPPORTED: aregextest.pas FAIL: fjf1102.pas FAIL: fjf322.pas FAIL: fjf403b.pas FAIL: fjf563e.pas FAIL: fjf587b.pas === gpc Summary === # of tests 5111 # of expected passes 5105 # of unexpected failures 5 # of unsupported tests 1 /home/russ/src/gcc_collection/gpc-20070904/build/gcc/xgpc version 20070904, based on gcc-4.1.2 Good job. I wonder, though, how many of the failures are due to back end bugs. Russ

1 0

indirect jmp redux (Mac OS on Intel)
by Frederick Karl Kepner DuPuy 04 Sep '07

04 Sep '07

Hi. Regarding gpc for Mac OS X on Intel, I found a thread in the archives (see below) from October 2006 concerning an error message a user (Nestor Aguilera) got in compiling even the simplest programs. Unless I'm misreading the thread, no final conclusion was reached. Is anything further known now? Here's the thread: http://www.gnu-pascal.de/crystal/gpc/en/mail13854.html And the gist of the error messages: indirect jmp without `*' I'm having the same issue he had: programs which used to compile and execute happily with the gpc for PPC compiler are less happy with the gpc for Intel compiler--- they're still compiling, but issuing this error message repeatedly as they do so. I believe the output executes OK; but you can see why this is unsettling. So: is this a problem, or just an annoyance to be lived with? And is it happening to everybody trying to use gpc for Mac on Intel? (If so I'm curious as to why it hasn't been discussed since October.) (Please pardon my near-complete ignorance, by the way.) Thanks a lot, Rick DuPuy

3 5

linux test results for gpc based on GCC-4.1.2
by Matthias Klose 30 Aug '07

30 Aug '07

please find attach test results for gpc based on GCC-4.1.2 built on Ubuntu gutsy development. Listing for each architecture the results for the build based on 4.1.2 and then for the build based on 3.4.6. The packages (gpc-2.1-3.4 and gpc-4.1) are available in the Ubuntu archives. Looks like there are some regressions, or I'm missing some patches. Matthias ----- i486-linux-gnu ----------------------------------------------- Running target any FAIL: agettext2test.pas FAIL: asmtest.pas FAIL: fjf322.pas FAIL: fjf395a.pas FAIL: fjf395b.pas FAIL: fjf403b.pas FAIL: fjf524f.pas FAIL: fjf524g.pas FAIL: fjf563e.pas FAIL: fjf587b.pas FAIL: fjf779a.pas FAIL: fjf779b.pas FAIL: fjf779e.pas FAIL: fjf779f.pas FAIL: fjf779g.pas FAIL: fjf958c.pas FAIL: fjf998r.pas FAIL: nicola4c.pas === gpc Summary === # of tests 5070 # of expected passes 5051 # of unexpected failures 18 # of unsupported tests 1 3.4.6: Running target any FAIL: agettext2test.pas FAIL: fjf998r.pas === gpc Summary === # of tests 5057 # of expected passes 5054 # of unexpected failures 2 # of unsupported tests 1 ----- i686-linux-gnu ----------------------------------------------- Running target any FAIL: asmtest.pas FAIL: fjf322.pas FAIL: fjf395a.pas FAIL: fjf395b.pas FAIL: fjf403b.pas FAIL: fjf524f.pas FAIL: fjf524g.pas FAIL: fjf563e.pas FAIL: fjf587b.pas FAIL: fjf779a.pas FAIL: fjf779b.pas FAIL: fjf779e.pas FAIL: fjf779f.pas FAIL: fjf779g.pas FAIL: fjf958c.pas FAIL: nicola4c.pas === gpc Summary === # of tests 5070 # of expected passes 5053 # of unexpected failures 16 # of unsupported tests 1 3.4.6: Running target any === gpc Summary === # of tests 5057 # of expected passes 5056 # of unsupported tests 1 ----- amd64-linux-gnu ---------------------------------------------- Running target any FAIL: chuck6.pas FAIL: fieldw.pas FAIL: fjf23.pas FAIL: fjf30b.pas FAIL: fjf322.pas FAIL: fjf395a.pas FAIL: fjf395b.pas FAIL: fjf403b.pas FAIL: fjf524f.pas FAIL: fjf524g.pas FAIL: fjf563e.pas FAIL: fjf587b.pas FAIL: fjf779a.pas FAIL: fjf779b.pas FAIL: fjf779e.pas FAIL: fjf779f.pas FAIL: fjf779g.pas FAIL: fjf958c.pas FAIL: fsc22.pas FAIL: fsc24.pas FAIL: nicola4c.pas FAIL: writeb.pas FAIL: writec.pas FAIL: writee.pas FAIL: writeg.pas === gpc Summary === # of tests 5070 # of expected passes 5043 # of unexpected failures 25 # of unsupported tests 2 3.4.6: Running target any FAIL: chief40.pas FAIL: chuck6.pas FAIL: fieldw.pas FAIL: fjf23.pas FAIL: fjf30b.pas FAIL: fjf327.pas FAIL: fjf526a.pas FAIL: fjf526b.pas FAIL: fsc22.pas FAIL: fsc24.pas FAIL: shl.pas FAIL: writeb.pas FAIL: writec.pas FAIL: writee.pas FAIL: writeg.pas === gpc Summary === # of tests 5057 # of expected passes 5040 # of unexpected failures 15 # of unsupported tests 2 ----- powerpc-linux-gnu -------------------------------------------- Running target any FAIL: agettext2test.pas FAIL: fjf322.pas FAIL: fjf395a.pas FAIL: fjf395b.pas FAIL: fjf403b.pas FAIL: fjf563e.pas FAIL: fjf587b.pas FAIL: fjf779a.pas FAIL: fjf779b.pas FAIL: fjf779e.pas FAIL: fjf779f.pas FAIL: fjf779g.pas FAIL: fjf998r.pas FAIL: nicola4c.pas FAIL: prep2p.pas === gpc Summary === # of tests 5070 # of expected passes 5052 # of unexpected failures 15 # of unsupported tests 3 3.4.6: Running target any FAIL: agettext2test.pas FAIL: fjf998r.pas FAIL: prep2p.pas === gpc Summary === # of tests 5057 # of expected passes 5051 # of unexpected failures 3 # of unsupported tests 3 ----- sparc-linux-gnu ---------------------------------------------- Running target any FAIL: agettext2test.pas FAIL: fjf322.pas FAIL: fjf395a.pas FAIL: fjf395b.pas FAIL: fjf403b.pas FAIL: fjf563e.pas FAIL: fjf587b.pas FAIL: fjf746.pas FAIL: fjf779a.pas FAIL: fjf779b.pas FAIL: fjf779e.pas FAIL: fjf779f.pas FAIL: fjf779g.pas FAIL: fjf967e.pas FAIL: fjf998r.pas FAIL: nicola4c.pas === gpc Summary === # of tests 5070 # of expected passes 5052 # of unexpected failures 16 # of unsupported tests 2 3.4.6: Running target any FAIL: agettext2test.pas FAIL: fjf980a.pas FAIL: fjf980b.pas FAIL: fjf998r.pas === gpc Summary === # of tests 5057 # of expected passes 5050 # of unexpected failures 4 # of unsupported tests 3 ----- ia64-linux-gnu ----------------------------------------------- Running target any FAIL: chief35b.pas FAIL: chuck6.pas FAIL: fieldw.pas FAIL: fjf23.pas FAIL: fjf30b.pas FAIL: fjf322.pas FAIL: fjf395a.pas FAIL: fjf395b.pas FAIL: fjf403b.pas FAIL: fjf524f.pas FAIL: fjf524g.pas FAIL: fjf563e.pas FAIL: fjf587b.pas FAIL: fjf779a.pas FAIL: fjf779b.pas FAIL: fjf779e.pas FAIL: fjf779f.pas FAIL: fjf779g.pas FAIL: fjf958c.pas FAIL: fsc22.pas FAIL: fsc24.pas FAIL: nicola4c.pas FAIL: writeb.pas FAIL: writec.pas FAIL: writee.pas FAIL: writeg.pas === gpc Summary === # of tests 5070 # of expected passes 5042 # of unexpected failures 26 # of unsupported tests 2 3.4.6: Running target any FAIL: chief40.pas FAIL: chuck6.pas FAIL: fieldw.pas FAIL: fjf23.pas FAIL: fjf30b.pas FAIL: fjf327.pas FAIL: fjf526a.pas FAIL: fjf526b.pas FAIL: fsc22.pas FAIL: fsc24.pas FAIL: shl.pas FAIL: writeb.pas FAIL: writec.pas FAIL: writee.pas FAIL: writeg.pas === gpc Summary === # of tests 5057 # of expected passes 5040 # of unexpected failures 15 # of unsupported tests 2

1 0

Re: AKFAvatar
by M. Uhle sen. 18 Aug '07

18 Aug '07

This seems to me to be another version of a very academic discussion about our "new" students, who all know how to "click"......Sorry, they are as the are. Trying to teach "programming" to undergraduate students for years now, I do see the problem from a different point of view. It is NOT a question of IDE's, debugging-Systems, sophisticated tools, not even languages. To me it seems to be a problem of missing applications. What I mean? Student: To program my first "hallo world" is simply boaring, I am not interested to print a simple sin-table.. and the like. What on earth all this programming is to be used for? Some years ago Iswitched to: A simple editor, a plain compiler, and a textbased console and AN INTERESTING JOB to do. Say: simulate an atomobile on a 10 km long road with traffic lights. Answer the question: does it make sense to ignore speed limits or does it not? So jump, dive, and swim.. And the advice to our beginners is: Start with a small program saying 'Program Speed Simulation Start' 'Program Speed Simulation Stop' If that works, you know: I can use the editor, it worked I can use the compiler, it worked I wrote my first program, it worked. I save it as version 0, copy ist to version 1, and I will expand it now to version n+1. Output will be written to screen and (later) redirected to a file from where it can be plotted by eg. xmgrace or so. We all in the teaching business should think about interesting 'real life' examples, it seems there are just a few! The sophisticated tools should NOT be used. To be honest: even the above example is - in my opinion - not real enough! What I mean? try to use "Kdevelop" (or any of the like) with beginners. Even the "hallo world" project creates "thousands" of files in the associated directories, no beginner will understand that not to talk about keeping track. I dropped it completely (for beginners, not for later real work). If I am allowed to add one thing: my students are still using GPC 2004.12.18 Why? There is no newer binary available on "www.gnu-pascal.de", and beginners are NOT able to compile GPC from scratch. And: most Pascal users are not experts for c! Mathias Uhle -- Univ.-Prof. Dr.-Ing. Mathias Uhle, Messtechnik, Universitaet Dortmund Leonhard Euler Str. 5, D-44221 Dortmund Tel: +49.231.755.3257 Fax: +49.231.755.2631 email: uhle(a)mt.mb.uni-dortmund.de http://www.mt.mb.uni-dortmund.de

3 3

[Fwd: Re: AKFAvatar]
by Adriaan van Os 17 Aug '07

17 Aug '07

-------- Original Message -------- Subject: Re: AKFAvatar Date: Thu, 16 Aug 2007 22:53:46 +0200 From: marcov(a)stack.nl (Marco van de Voort) To: Adriaan van Os <gpc(a)microbizz.nl> References: <20070814101911.GA5425(a)castrophe.akfoerster.de> <46C3FF48.50100(a)microbizz.nl> In gmane.comp.compilers.gpc, you wrote: >> your program to use my library. (The program may not use the CRT unit or >> any other nonstandard output facility) > > The same mistake was made in teaching mathematics the-modern-way, with > much graphics and much less exact reasoning nor proofs-of-correctness. > Well, indeed in a democratic society the Pythogorean Theorem > <http://en.wikipedia.org/wiki/Pythagorean_theorem> should no longer be > proofed, which is dictatorial, or even be thought about, which is > elitarian, but decided on by voting .... > > This is all bullsh..., I mean nonsense. Programming, like mathematics, > *is* about exact reasoning and it *is* about abstract thinking. The task > of teachers is to lead pupils into this new world and to bring young > people to spiritual maturity. It is *not* the task of teachers to succumb > to the first shallow prejuduce, like whether something yet unknown is > "boring" or not. I talked a bit with teachers on the FPC booth at Systems 2005, and I got a different feeling; Teachers have had a love for the consoles tools because their simplicity somewhat put a brake on the time being spent in e.g. form designers making blinkenlightes with buttons and the like. (and because they are generally too lazy to re-setup their courses) However slowly that is becoming a problem because current students seem to miss any feel for the textconsole at all, having never used Dos. It is simply not a common skill anymore. And yes, that is not a really hard skill to teach, but every course day lost also detracts from the real objective of the course. The consensus seemed to be that a simple IDE maybe integrated with a lib to do some minimal work (few textfields/memo's input, a few output ones) would be the best. IOW one should separate "old and simple" and the real issue "can't be abused" here. Anyway, TP is probably still too free for a CS practicum, though the skills to exploit it may have decreased in new students A cut down compiler,IDE and lib that can't do anything communicating with the outside world except this special lib would be best. So one of the open source compilers, cut down and an IDE (Bloodshed?). Main problem probably: the debugger.

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