Pike-devel May 2009

pike-devel@lists.lysator.liu.se

2 participants
8 discussions

Re: Playing music using pike and SDL.
by Martin Nilsson (lvl 60) ＠ Pike (-) developers forum 13 Mar '26

13 Mar '26

Were you not able to get any C code to play through SDL either? Does your SDL library have a mixer compiled in it (I think it is optional)?

5 4

managing comport settings in linux
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 13 Mar '26

13 Mar '26

Not a good idea; the design philosophy of Pike is that Pike-level code should never be able to cause memory corruption at C-level. With ioctls there's no way to know what data a specific ioctl wants without reading the documentation for that specific ioctl for that specific OS. ioctls and fcntls are a way for device handlers to hook in APIs that aren't standard across all filedescriptors. / Henrik Grubbström (Lysator) Previous text: >2004-08-17 13:32: >Subject: managing comport settings in linux >-------------------------------------------------------------------- >What would be nice, is a way to define ioctl methods in >Pike. Perhaps something like > >object i = Stdio.IOCTL(4242 /* request_id */ ); >i->add_int_parameter(); >i->add_string_parameter(); >i->set_return_type(STRING); > >string ret = i(fd, 1, "somestring"); > > >That ought to be possible, or..? > > / Marcus Agehall (PacketFront) >

3 2

full MySQL 4.x support. or pike roadmap
by thomas.gusenleitner＠com-bet.com ＠ Pike developers forum 01 Mar '26

01 Mar '26

HI to all! mysql 4.x support works only with a mysql CFLAGS=-DUSE_OLD_FUNCTIONS is this correct ? are there plans to make a full 4.x support ? bye, thomas

4 4

CHANGES for new stable
by Peter Bortas ＠ Pike developers forum 30 May '09

30 May '09

I've committed a rough draft for CHANGES for the next stable. You are encouraged to fix the FIXME's either directly in CVS or by discussing them here and I'll commit something based on the discussion: http://pike.ida.liu.se/development/cvs/diff.xml?module=Pike&file=7.8/CHANGE… There are also two things that have to be resolved before I can make a build: 1) Protocols.IPv6 It really isn't a protocol module. Shouldn't that stuff be in Standards or Tools? 2) "Added symlink support to chown and utime" I will read the code later, but perhaps someone can describe what _exactly_ that change is supposed to do? I've flagged it because changes of the follow-the-symlink kind has a well known tendency to blow up in the face.

2 7

%4H broken
by Peter Bortas ＠ Pike developers forum 30 May '09

30 May '09

Release stopper: %4H seems to be broken: > sprintf("%4H", "hello"); sprintf: Length of string to %4H too large. HilfeInput:1: HilfeInput()->___HilfeWrapper() I've checked in a test-case, so Pikefarm should light up yellow shortly.

4 10

%4H broken
by Peter Bortas ＠ Pike developers forum 30 May '09

30 May '09

s/humongus/humongous string/

1 0

Documentation licensing
by Niels M�ller () ＠ Pike (-) developers forum 19 May '09

19 May '09

Hi, I'm reviewing the license of the Nettle manual, which has been somewhat unclear (in some places it was stated that the manual was GPL:ed, while copyright notices in the manual said something differently or were simply missing). This is related to Pike, because some paragraphs of the Nettle manual are copied to pike's module reference doc, e.g., http://pike.ida.liu.se/generated/manual/modref/ex/predef_3A_3A/Crypto/AES.h…. The corresponding Pike source file (http://pike.ida.liu.se/development/cvs/view.xml?module=Pike&file=7.8/lib/mo…), but I guess the intention is that it's licensed under the usual GPL/LGPL/MPL dual (or "threeal") license as the rest of Pike. I'd like to make clear that such copying and remixing is allowed, question is how. I could use the GNU FDL (no invariant sections), and try to come up with an exception covering remixing of the manual into documentation for crypto modules that reuse nettle code and/or interfacecs. Or I could make the entire manual public domain. Or in between, I could try to use something along the lines of CC-attribution or CC-sharealike. If possible, I'd prefer to retain some kind of copyleft, i.e, it should not be allowed to remix the manual and then require a per-copy licensing fee for the result, or apply drm-madness, and things like that. Suggestions? PS. Whatever I decide for the main text, I'm going to add some disclaimer saying that code examples are in the public domain. PPS. At least I think the copying is from the Nettle manual to Pike module documentation. If anybody thinks the copying is in the other direction, please correct me.

3 4

%4H broken
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 18 May '09

18 May '09

New fix in CVS.

1 0

2026

2025

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 May 2009