Pike-devel January 2006

pike-devel@lists.lysator.liu.se

8 participants
33 discussions

GTK2
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 03 Jan '06

03 Jan '06

Could someone with an insight into the intrinsics of the GTK2 module explain to me why e.g. GTK2.Label.set_markup() is implemented by hand in gtklabel.pre? As far as I can see, the autogenerator would have generated an identical function, except that non-ASCII strings would have actually worked...

4 22

pike embedding
by H. William Welliver III 02 Jan '06

02 Jan '06

I managed to build libpike.so from the 7.7 tree last night, and a few minutes ago I ran through the source for main.c, and pulled out what looks like the bare minimum code for starting an embedded pike interpreter. Right now, it performs the same actions as a regular pike, in that your first argument should be a pike script. Differences are that it doesn't parse any command line options, and the pike master must be specified in the PIKE_MASTER environment variable. To get a libpike, you just run a "make lib" from the 7.7 directory. Also, you'll probably want to rename the resulting .so file to libpike.so (I'm sure there's a good reason why the generated file is named "pike.so", but in order for the linker to use it, it has to start with lib :) I'd say that about 25% of the 120 lines of code in this example are the include files, and another 25-35% are for handling errors before the master is initialized. So, the end result is that it takes less than 50 lines of code to initialize, start and shut down the pike compiler. I'd imagine that a good portion of the code in this example could be made into some standard helper functions, and that you're really only dealing with a dozen lines of code or so. Note that none of this is original work on my part; I'm just passing on the results of my attempts at building a program that uses the embedded interpreter. I'd encourage discussion on what the embedding "niceties" should look like. the code: http://hww3.riverweb.com/dist/pike_embedding Bill

4 4

Resolving local variables in inherited classes
by Marcus Agehall (PacketFront) ＠ Pike (-) developers forum 01 Jan '06

01 Jan '06

I'm working on Xine-bindings for pike and I've encountered a situation where I need to access variables in other objects, declared as CVAR in the cmod source. My program structure looks like this PIKECLASS Engine { PIKECLASS AudioPort program_flags PROGRAM_USES_PARENT; { CVAR int my_variable; } PIKECLASS Stream program_flags PROGRAM_USES_PARENT; { PIKEFUN void create(object /*AudioPort object*/ ap) { /* Here I need to access ap->my_variable */ } } } I've looked a bit at how I resolve the parent context in the inner classes, but I can't make it work for the ap-object. I guess my question boils down to, how do I find out where the AudioPort local variables begin in ap->storage?

2 2

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 January 2006