Pike-devel July 2005

pike-devel@lists.lysator.liu.se

8 participants
26 discussions

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

09 Apr '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) >

4 3

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

28 Feb '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

Pike 7.6
by Martin Nilsson (DivX Inc.) ＠ Pike (-) developers forum 22 Aug '06

22 Aug '06

It is time for a new release of Pike 7.6. Is there anyone who can do the release notes? If not, we'll just wait a bit longer...

9 12

New feature: Tools.Monger
by Bill Welliver 28 Jul '05

28 Jul '05

I've placed the first version of the unbundled Monger tool up on the modules.gotpike.org website. Unbundling the monger tool is the first step toward making all Pike modules available outside the pike distribution. This first release offers significant new functionality for developer types, in that it allows a certain amount of change functionality when working with the remote module repository. In fact, this functionality was used to create the new version of Tools.Monger and upload its source using Tools.Monger.MongerDeveloper. As of right now, you'll have to create a new module using the web interface. I think that the most dangerous situations are caught, but please don't purposely try to crash the repository :) Here's an example: > object m = Tools.Monger.MongerDeveloper(); > m->set_auth("joedeveloper", "pikerulez"); (1) Result: 0 > m->add_new_version("Tools.Monger", "7.6.28", "This is the first functional unbundled release of the Monger tool.\nThis version includes developer functionality, such as version creation,\ndependency functionality, and source upload.", "GPL/LGPL/MPL"); (2) Result: 1 > m->set_dependency("Tools.Monger", "7.6.28", "Pike", "7.6.0", "7.7.999", 1); (3) Result: 1 > m->set_module_source("Tools.Monger", "7.6.28", "Tools_Monger-7.6.28.tar.gz"); (2) Result: 1 > quit To get the new release, use this command with any 7.6.6 or higher release of Pike: pike -x monger --install Tools.Monger You may need to remove your Tools.pmod/Standalone.pmod/monger.pike.o file if you get annoyed at the out of date warning messages. Obviously, this is just a first step, and so there are some things that are less than ideal, but I think it's a big step in the right direction for users and developers. As always, comments and suggestions are welcome. Bill

1 0

7.6 release
by Bill Welliver 27 Jul '05

27 Jul '05

OK, I've extracted the majority of changes from the changelog. Anyone care to look through my work to see if i've missed anything? After that, what's next in getting a new release out the door? Bill

5 4

pike terminology: parent/child, super/sub or base/derived?
by Martin Bähr 27 Jul '05

27 Jul '05

hi, what is the preferred terminology for pike documentation: parent and child class super and subclass base and derived class ? i am kinda leaning towards parent/child. greetings, martin.

3 2

Changes
by Bill Welliver 25 Jul '05

25 Jul '05

I've started going through the changelog since 7.6.24. I checked in what I have so far; please take a look to make sure your change is properly described (I'm not finished yet, so consider these preliminary). Also, I'm not sure, but it looks like there might be some missing entries for previous 7.6 releases. Can anyone confirm or deny that? Thanks, Bill

2 1

automap: [*] not supported here. bug?
by Martin Bähr 23 Jul '05

23 Jul '05

hi, can you explain why: random(allocate(3,9)[*]); or random(({9,9,9})[*]); don't work, while array foo = allocate(3,9); random(foo[*]); does? greetings, martin.

6 13

Re: Pike 7.6
by Peter Bortas ＠ Pike developers forum 23 Jul '05

23 Jul '05

>so while it would be nice to have in 7.6, It would, and I want it there, but it needs to sit in 7.7 for a while so people get a sproting chance at checking out the interface before it's cast in stone.

1 0

Binary size
by Martin Nilsson (DivX Inc.) ＠ Pike (-) developers forum 23 Jul '05

23 Jul '05

Something strange has happened with the pike 7.7 binary during the last month or so. It used to be 4.6 MB, but is now 15.4 MB when looking with ls. Using size however tells that the text segment is down 34k and the rest remains unchanged since May. What's the padding?

3 2

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 July 2005