Pike-devel October 2007

pike-devel@lists.lysator.liu.se

3 participants
19 discussions

objc
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 06 Oct '07

06 Oct '07

How do I use the Objective-C bindings? When trying to build a simple example program, I get: chiyo:/tmp% gcc -o test test.m -lFoundation /tmp/ccowH8qL.o: In function `main': test.m:(.text+0x1c0): undefined reference to `really_free_svalue' /tmp/ccowH8qL.o:(.data+0x334): undefined reference to `__objc_class_name_OCPikeInterpreter' collect2: ld returned 1 exit status chiyo:/tmp% Ok, I obviously need to create some library. But how? The only part of the build system which touches "OCPikeInterpreter" appears to be the rule "framework", but making framework does not work: chiyo:~/Pike/7.7/build/linux-2.6.22-12-powerpc-ppc% make framework Compiling OCPikeInterpreter.m make[1]: Entering directory `/home/marcus/Pike/7.7/build/linux-2.6.22-12-powerpc-ppc' make[1]: Leaving directory `/home/marcus/Pike/7.7/build/linux-2.6.22-12-powerpc-ppc' make[1]: Entering directory `/home/marcus/Pike/7.7/build/linux-2.6.22-12-powerpc-ppc' make[1]: Leaving directory `/home/marcus/Pike/7.7/build/linux-2.6.22-12-powerpc-ppc' Linking Pike.framework gcc: Cocoa: No such file or directory gcc: dynamic_lookup: No such file or directory gcc: 7.7: No such file or directory gcc: @executable_path/../Frameworks/Pike.framework/Pike: No such file or directory gcc: unrecognized option '-current_version' make: *** [framework] Error 1 chiyo:~/Pike/7.7/build/linux-2.6.22-12-powerpc-ppc% I think this needs some work before it can go into 7.8.

3 7

Keywords
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 06 Oct '07

06 Oct '07

As you can see from the sudden spree of checkins we've had another meeting in Linköping (though the initial objective had nothing to do with Pike, the discussion turned in that direction, and we would be stupid to not take notes...) While many of the items are simply bugfixes or incomplete features, there were a few items that dealt with changes that impact the language on a fundamental level. We revisited the "static" discussion and some good arguments were made both for the functionality of static (as in "moved out one scope") and against it. The consensus we had was to directly implement "protected" to do what "static" does today. Previously "protected" did nothing. This has been committed. As next move we would like to implement "shared" as a new keyword that does the "declare in outter scope" thing and to make "static" as deprecated (giving a warning when used). While on the subject of keywords we thought it would be a good idea to also mark "nomask" as deprecated ("final" does the same job). We also want to add "deprecated" as a keyword to be able to mark non-recommended parts of the interface as such. The idea is to tie deprecated into the type system so that it can not only be used on entire functions, but also on specific arguments. A new and annoyingly long #pragma statement to silence deprecation warnings was suggested.

2 1

Re: GTK2 examples
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 04 Oct '07

04 Oct '07

A snapshot is now available at <http://mc.pp.se/gkdrill.pike>. You need the file /usr/share/edict/kanjidic for the program to work.

1 0

Re: GTK2 examples
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 04 Oct '07

04 Oct '07

It's missing lots of functionality. Mostly in the area of selecting the set of kanji to be quizzed on. But the basic stuff works.

1 0

GTK2 examples
by H. William Welliver III 04 Oct '07

04 Oct '07

I got a request the other day for some examples of using the GTK2 module that go beyond "hello world". I only have GTK(1) code; does anyone else have anything that might satisfy an intrepid developer? Bill

2 1

Snapshot tarballs and packaging/debian
by Magnus Holmgren, FR Ryd (Nu med m�l och syfte) ＠ Pike (-) developers forum 03 Oct '07

03 Oct '07

I have a few questions relating to pike in Debian (as you may know, the previous maintainer has retired from Debian and orphaned his packages). I've figured out that one can get a fresh tarball from http://pike.ida.liu.se/generated/pikefarm/packages/7.6/latest. What's the difference between that and checking out from CVS and running "make source" (which is what I suspect Marek has done), if any? Is there any archive of such tarballs except for the official releases? How did the packaging/debian subdirectory originally come to be? Do you synchronize with the Debian package yourself or has Marek been sending you patches? I see that export.pike adds new records to packaging/debian/changelog. AFAICT, export.pike --tag first increments the build number (to an even number, typically), then tags, then increment the build number again, so that an even build number represents a known state of the source, whereas an odd build number can include any number of commits inbetween.

17 129

Re: Snapshot tarballs and packaging/debian
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 02 Oct '07

02 Oct '07

I don't think we've ever changed the API between x.even.y, but it of course happens in e.g. Pike 7.7.

4 3

Snapshot tarballs and packaging/debian
by Magnus Holmgren, exim.org ＠ Pike developers forum 01 Oct '07

01 Oct '07

Wait, there's http://pike.ida.liu.se/download/pub/pike/beta/. Neat. But there's no 7.7 there.

5 7

Snapshot tarballs and packaging/debian
by Johan Sundstr�m (Achtung Liebe!) ＠ Pike (-) developers forum 01 Oct '07

01 Oct '07

Of course, this is a more practically useful URL, though (for 7.6): http://pike.ida.liu.se/_/cvsview/commits/7.6/src/version.h?u=Pike&f=2007-06… meaning that the 7.6.116 build was made from a CVS tree snapshot from 2007-06-03 22:35:36 UTC.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pike-devel October 2007