<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.lang.pike.devel">
    <title>gmane.comp.lang.pike.devel</title>
    <link>http://blog.gmane.org/gmane.comp.lang.pike.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.pike.devel/4553"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.pike.devel/4550"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.pike.devel/4543"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.pike.devel/4526"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.pike.devel/4521"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.pike.devel/4519"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.pike.devel/4515"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.pike.devel/4496"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.pike.devel/4488"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.pike.devel/4487"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.pike.devel/4483"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.pike.devel/4465"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.pike.devel/4457"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.pike.devel/4440"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.pike.devel/4437"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.pike.devel/4435"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.pike.devel/4434"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.pike.devel/4432"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.pike.devel/4430"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.pike.devel/4424"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.pike.devel/4553">
    <title>Pike 7.8 Release (last call)</title>
    <link>http://comments.gmane.org/gmane.comp.lang.pike.devel/4553</link>
    <description>&lt;pre&gt;Does anyone have any objections to 7.8.680 becoming the next official release of Pike? Do note that machine code is non-functional on (at least more modern instances of) i386. If I don't hear any objections in 24 hours, I will attempt to update the website, etc, with the new information.

Best,

Bill  
&lt;/pre&gt;</description>
    <dc:creator>H. William Welliver III</dc:creator>
    <dc:date>2012-05-22T03:16:43</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.pike.devel/4550">
    <title>strict type regression</title>
    <link>http://comments.gmane.org/gmane.comp.lang.pike.devel/4550</link>
    <description>&lt;pre&gt;I've started getting

/home/nilsson/pike/lib/modules/String.pmod/module.pmod:98: Warning: An
expression of type string | int | !mixed cannot be assigned to a
variable of type int.

after the changes in there. It should be possible to work out that

  int sz = min(&amp;lt; at &amp;gt;map(strs, sizeof));

is always the correct type.

&lt;/pre&gt;</description>
    <dc:creator>Martin Nilsson (Opera Mini - AFK!) &lt; at &gt; Pike (-) developers forum</dc:creator>
    <dc:date>2012-05-16T15:30:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.pike.devel/4543">
    <title>pike_frame-&gt;fun = FUNCTION_BUILTIN</title>
    <link>http://comments.gmane.org/gmane.comp.lang.pike.devel/4543</link>
    <description>&lt;pre&gt;In INIT, EXIT and some gc callbacks the fun in Pike_fp is set to
FUNCTION_BUILTIN. there are some places in the code (e.g.
ADT.List()-&amp;gt;_get_iterator) where -&amp;gt;fun is used in INHERIT_FROM_INT et
al, which segfaults (except with PIKE_DEBUG). I am not sure where to
fix this. Should the *_FROM_INT macros check for FUNCTION_BUILTIN
or is this better to be handled in the individual INIT/EXIT methods ?

does anyone object to making ADT.Stack and ADT.Queue inherit ADT.List?

arne

&lt;/pre&gt;</description>
    <dc:creator>Arne Goedeke</dc:creator>
    <dc:date>2012-05-05T22:25:17</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.pike.devel/4526">
    <title>Visualization of inherit-graphs</title>
    <link>http://comments.gmane.org/gmane.comp.lang.pike.devel/4526</link>
    <description>&lt;pre&gt;Hi.

I've gotten several requests for adding inherit-graphs to the Pike
documentation. I now have a proof of concept that renders the graphs
as a &amp;lt;pre&amp;gt;-formatted block similar to the corresponding feature in
javadoc (but supporting multiple-inherits). Some examples:

| Class SSL.https
| Inherit graph
| 
|     predef::ADT.Queue
|      |  
|      |  predef::SSL.context
|      |   |  
|      |   |  predef::Stdio.Port
|      |   |   |  
|      +---+---+--predef::SSL.sslport
|                  |  
|                  +--predef::SSL.https

| Class Parser.XML.Tree.SimpleRootNode
| Inherit graph
| 
|     predef::Parser.XML.Tree.AbstractSimpleNode
|      |  
|      |  predef::Parser.XML.Tree.VirtualNode
|      |   |  
|      |   |  predef::Parser.XML.Tree.XMLParser
|      |   |   |  
|      +---+------predef::Parser.XML.Tree.SimpleNode
|              |   |  
|              +---+--predef::Parser.XML.Tree.SimpleRootNode

| Class GTK2.FileChooserDialog
| Inherit graph
| 
|     predef::GTK2.Object
|      |  
|      +--pre&lt;/pre&gt;</description>
    <dc:creator>Henrik Grubbström (Lysator) &lt; at &gt; Pike (-) developers forum</dc:creator>
    <dc:date>2012-05-02T18:45:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.pike.devel/4521">
    <title>Metafunctions</title>
    <link>http://comments.gmane.org/gmane.comp.lang.pike.devel/4521</link>
    <description>&lt;pre&gt;I've got a bit of a problem with the `-&amp;gt;() lfun.  To illustrate,
consider the following class:

---8&amp;lt;--
class Base
{
  mixed `-&amp;gt;(string x)
  {
    return
      (x == "add_one" &amp;amp;&amp;amp; lambda(int x) { return x+1; }) ||
      (x == "add_two" &amp;amp;&amp;amp; lambda(int x) { return x+2; });
  }
}
---8&amp;lt;---

I now have a class which allows me to do Base()-&amp;gt;add_one(7) to get 8,
and Base()-&amp;gt;add_two(7) to get 9.  So far so good.

Now, let's try to specialize this class:

---8&amp;lt;---
class Sub
{
  inherit Base;
  string add_two(int x) { return x+"two"; }
}
---8&amp;lt;---

FAIL!  Sub()-&amp;gt;add_two(7) still returns 9.  And what's more, even if I
try to add something with a name that doesn't exist in Base, I still
can't access it outside of Sub.

Is there a way around this?  I tried using `::-&amp;gt;() as a fallback in
`-&amp;gt;(), but it didn't have the desired effect.

&lt;/pre&gt;</description>
    <dc:creator>Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) &lt; at &gt; Pike (-) developers forum</dc:creator>
    <dc:date>2012-04-27T10:45:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.pike.devel/4519">
    <title>Pike 7.8 beta: feedback?</title>
    <link>http://comments.gmane.org/gmane.comp.lang.pike.devel/4519</link>
    <description>&lt;pre&gt;So, 7.8.680 has been out and about for a week, and despite the fact 
that I checked a fix in after I made that build, I'm inclined to say .680 
should become an official release. Does anyone have any feedback? Go? No 
go?

Bill




&lt;/pre&gt;</description>
    <dc:creator>Bill Welliver</dc:creator>
    <dc:date>2012-04-23T23:01:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.pike.devel/4515">
    <title>Segfault</title>
    <link>http://comments.gmane.org/gmane.comp.lang.pike.devel/4515</link>
    <description>&lt;pre&gt;I get this crash when trying to build pike with dmalloc.

#### Making dynamic: post_modules/GTK2
make[2]: Entering directory `/home/nilsson/pike/dmalloc/post_modules/GTK2'
Makefile:576: warning: overriding commands for target `depend'
Makefile:332: warning: ignoring old commands for target `depend'
/home/nilsson/pike/dmalloc/pike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/home/nilsson/pike/dmalloc/master.pike  /home/nilsson/pike/src/post_modules/GTK2/build_pgtk.pike --source='/home/nilsson/pike/src/post_modules/GTK2/source/' \
                   /home/nilsson/pike/src/post_modules/GTK2/output/few.pike
make[2]: *** [compile1] Segmentation fault
make[2]: Leaving directory `/home/nilsson/pike/dmalloc/post_modules/GTK2'
make[1]: *** [GTK2] Error 1
make[1]: Leaving directory `/home/nilsson/pike/dmalloc/post_modules'
make: *** [post_module_objects] Error 1

And it looks like it is in the startup things bail out.

nilsson&amp;lt; at &amp;gt;riaa:~/pike/dmalloc$ gdb pike
GNU gdb (Ubuntu/Linaro 7.3-0ubuntu2) 7.3-2011.08
Copyright (C)&lt;/pre&gt;</description>
    <dc:creator>Martin Nilsson (Opera Mini - AFK!) &lt; at &gt; Pike (-) developers forum</dc:creator>
    <dc:date>2012-04-23T15:25:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.pike.devel/4496">
    <title>Pike 7.8 Beta</title>
    <link>http://comments.gmane.org/gmane.comp.lang.pike.devel/4496</link>
    <description>&lt;pre&gt;I've prepared a new 7.8 test release for consideration. Please feel free to download and test.

http://pike.ida.liu.se/download/pub/pike/beta/7.8.680/

I am not aware of any show stoppers in this release; if none are found in the next week, this will become the new stable 7.8 release.

As always, please feel free to get in touch with any comments or concerns.

Best,

Bill
bill-NuqkLFvhzZFg9hUCZPvPmw&amp;lt; at &amp;gt;public.gmane.org
&lt;/pre&gt;</description>
    <dc:creator>H. William Welliver III</dc:creator>
    <dc:date>2012-04-18T05:51:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.pike.devel/4488">
    <title>map/filter, mapping index/values</title>
    <link>http://comments.gmane.org/gmane.comp.lang.pike.devel/4488</link>
    <description>&lt;pre&gt;I'm playing with map and filter and stuff, trying to do a functional way of removing an index from a map, like this:

({ 

  ([ "name": "user1",
        "val": "test",
        "random": "other"

  )],
  ([ "name": "user2",
        "val": "another test",
        "random": "something else"
  ]),
})

The array and mapping will be in that kind of format.  name is unique among all the map entries, and all the keys exist with all the maps.  I want to change it to something like this:

([ "user1": ([ "val": test", "random": "other" ]),
    "user2": ([ "val": "another test", "random": "something else" ])
])

I can get the keys for the new map with array[*]["name"].

But removing that key from the maps and leaving the others is giving me a problem.  Filter doesn't quite work because it only gives the value, and I'm not testing on the value, but the key.

A foreach would work, but I'm wondering if I can do something like:

mkmapping(a[*]["name"],map(a,lambda(mapping m) { filter(......&lt;/pre&gt;</description>
    <dc:creator>Lance Dillon</dc:creator>
    <dc:date>2012-04-12T19:20:24</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.pike.devel/4487">
    <title>7.8 release note assistance sought</title>
    <link>http://comments.gmane.org/gmane.comp.lang.pike.devel/4487</link>
    <description>&lt;pre&gt;I've been working through the check-in comments and have about 3/4 of them 
distilled into meaningful release notes, however I'm getting to the point 
where I need a little assistance weeding out noise and making sense of 
what's left.

I put together a list of the entries that I haven't added to the release 
notes yet, and I'd like to give everyone an opportunity to weigh in. The 
list is at the following url:

http://wiki.gotpike.org/ReleaseToDo7-8-664

If you've got something to say about anything left, feel free to put 
together a sentence or two describing the change. You can either 
send them to me, or just add them to the bottom of the wiki 
page. Also, if you know the entry isn't worth writing about, 
feel free to remove it from the list. Otherwise, I won't put too much more 
effort into adding the rest of these.

Best,

Bill

&lt;/pre&gt;</description>
    <dc:creator>Bill Welliver</dc:creator>
    <dc:date>2012-04-11T15:25:05</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.pike.devel/4483">
    <title>mime type update</title>
    <link>http://comments.gmane.org/gmane.comp.lang.pike.devel/4483</link>
    <description>&lt;pre&gt;Any objections to adding a few newish popular mime types to the MIME 
extension database? Specifically, I was thinking about the ODT types, but 
would be glad to add others if someone cares to send them my way.

Bill

&lt;/pre&gt;</description>
    <dc:creator>Bill Welliver</dc:creator>
    <dc:date>2012-04-05T18:51:33</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.pike.devel/4465">
    <title>new block allocator</title>
    <link>http://comments.gmane.org/gmane.comp.lang.pike.devel/4465</link>
    <description>&lt;pre&gt;We pushed an experimental branch which uses a new block allocator we 
have been developing. This one uses a different algorithm than the one 
we briefly mentioned on the conference. The new one uses a hashtable for 
page lookup instead of radix trees.

The branch can be found under arne/block_alloc, a GJAlloc-bundle is 
available at http://fortranland.com/GJAlloc-0.08.tar.gz or from 
https://github.com/arneg/GJAlloc via git. The branch currently contains 
alot of obsolete history, which we would squash into one commit in case 
of inclusion.

Standalone performance comparisons are available at 
https://github.com/arneg/GJAlloc/wiki/Performance-comparison. The 
speedup is quite noticeable when compiling with --cleanup-on-exit, 
otherwise for most use cases the differences should be unnoticable. 
However, when having many things around that do not get freed linearly, 
the speedup can be dramatic. A rather extreme example is

  time pike -e 'array a = map(allocate(1000000, 5), random_string); for (int i = 0; i &amp;lt;&lt;/pre&gt;</description>
    <dc:creator>Arne Goedeke</dc:creator>
    <dc:date>2012-04-02T21:16:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.pike.devel/4457">
    <title>gobject-introspection</title>
    <link>http://comments.gmane.org/gmane.comp.lang.pike.devel/4457</link>
    <description>&lt;pre&gt;Hi guys.

I was feeling bored so I started work on a Pike binding for GLib:s
object introspection repository (aka "gir").

It's still horribly incomplete, but it can already handle simple stuff
like this:

---8&amp;lt;---
import GI.repository;

void main()
{
  Notify.init("notifytest");
  Notify.Notification.new("Hello world", "This is an example",
  "dialog-information")-&amp;gt;show();
}
---8&amp;lt;---

The branch is available as "marcus/gobject-introspection" on the git
server if you want to check it out or (*gasp*) contribute.  :-)

&lt;/pre&gt;</description>
    <dc:creator>Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) &lt; at &gt; Pike (-) developers forum</dc:creator>
    <dc:date>2012-04-01T10:35:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.pike.devel/4440">
    <title>String handling optimisation</title>
    <link>http://comments.gmane.org/gmane.comp.lang.pike.devel/4440</link>
    <description>&lt;pre&gt;Does anyone know how often in the code we actually depend on the
fact that the same string will be at the same address in memory?

Because I'm contemplating an optimisation which would involve making
the string duplication avoidance opportunistic instead of mandatory.

I.e. something along the lines of all strings shorter than stringmin will
always be optimised to a single reference, and all strings above that *might*
have more than one reference, but not necessarily do (i.e. they're not
fully hashed all the time, to avoid the overhead of rehashing large strings
repeatedly when juggling around lots of strings).

All the places that depend on same string = same address would need to be
patched.  Also, to determine stringmin, some profiling of existing apps
would be interesting.  Is that statistic available for say Roxen, to know
the distribution of string length and reference count in a running
application?
&lt;/pre&gt;</description>
    <dc:creator>Stephen R. van den Berg</dc:creator>
    <dc:date>2012-03-29T08:22:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.pike.devel/4437">
    <title>Compiling Pike 7.9 crashes?</title>
    <link>http://comments.gmane.org/gmane.comp.lang.pike.devel/4437</link>
    <description>&lt;pre&gt;#### Making dynamic: post_modules/Bz2
#### Making dynamic: post_modules/COM
#### Making dynamic: post_modules/CritBit
/var/src/roxen/rpike/build/linux-3.1.9-vs2.3.2.5-dirty-x86_64/precompile.sh precompile.pike --api=4 &amp;gt;"/var/src/roxen/rpike/src/post_modules/CritBit/inttree.c" "/var/src/roxen/rpike/src/post_modules/CritBit/inttree.cmod" || { rm "/var/src/roxen/rpike/src/post_modules/CritBit/inttree.c"; exit 1; }
precompile: pike /var/src/roxen/rpike/bin/precompile.pike --api=4 /var/src/roxen/rpike/src/post_modules/CritBit/inttree.cmod (method=QQQQQQ)
Unsupported API version: 4 (max: 3)
precompile: /usr/bin/pike /var/src/roxen/rpike/bin/precompile.pike --api=4 /var/src/roxen/rpike/src/post_modules/CritBit/inttree.cmod (method=QQQQQQ)
Unsupported API version: 4 (max: 3)
precompile: /var/src/roxen/rpike/build/linux-3.1.9-vs2.3.2.5-dirty-x86_64/pike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/var/src/roxen/rpike/build/linux-3.1.9-vs2.3.2.5-dirty-x86_64/master.pike  /var/src/roxen/rpike/bin/precompile.pike --api=&lt;/pre&gt;</description>
    <dc:creator>Stephen R. van den Berg</dc:creator>
    <dc:date>2012-03-28T14:05:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.pike.devel/4435">
    <title>pgsql fixes and other things</title>
    <link>http://comments.gmane.org/gmane.comp.lang.pike.devel/4435</link>
    <description>&lt;pre&gt;I just pulled the latest pike version from git.
It clearly has been a while, since I've actively participated.
I apologise for my extended leave, it was due to some real-life issues
that got in the way of things.  That is not to say that I didn't stop using
Pike or Roxen; quite the opposite, I just didn't have time to keep up on
the mailinglists.  I got snippets of updates through Marc though, so I wasn't
completely ignorant.

Anyway, the good news is: I'm back.
I just glanced through the mailinglist archives (in my mailbox) and it is
quite a bundle to skip through (not started on that yet).
I first checked the state of the pgsql module.  I see some minor updates/fixes.
I have one small and one very important fix waiting here which should get in
ASAP (which I have been hunting down for the past three years, but did not,
until about 2 weeks ago, result in a SEGV; which finally made it possible
to zoom in on it; which, in effect, was the final nudge that I needed to get
back on track with the mailinglist here)&lt;/pre&gt;</description>
    <dc:creator>Stephen R. van den Berg</dc:creator>
    <dc:date>2012-03-28T12:25:09</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.pike.devel/4434">
    <title>abi and building with bundles</title>
    <link>http://comments.gmane.org/gmane.comp.lang.pike.devel/4434</link>
    <description>&lt;pre&gt;I noticed a few problems that exist when building Pike using bundles. I'm 
not very familiar with how that all works, so I thought I'd report them 
here in the hope that someone more comfortable with making changes to this 
can take a closer look:

1. If you specify an ABI that isn't the "default" for a given system 
using --with-abi, the ABI specific compiler flags don't seem to be passed 
on to any subsequent bundles. Thus, you get all kinds of problems with 
mismatched abis when trying to link. A temporary workaround seems to be to 
define CFLAGS and pass them in for the whole build process.

2. A problem specific to Nettle seems to be that there's a small c++ test 
program that gets built as part of the Nettle bundle. When building for a 
non-default ABI, this test program can't link against the built library, 
causing the whole bundle to fail. A temporary workaround seems to be to 
define CXXFLAGS and pass these flags (such as -m32) as part of the overall 
build process.

Bill

&lt;/pre&gt;</description>
    <dc:creator>Bill Welliver</dc:creator>
    <dc:date>2012-03-27T17:06:55</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.pike.devel/4432">
    <title>Pike 7.8 Alpha</title>
    <link>http://comments.gmane.org/gmane.comp.lang.pike.devel/4432</link>
    <description>&lt;pre&gt;I've prepared a new 7.8 test release for consideration. Please feel free to download and test.

http://pike.ida.liu.se/download/pub/pike/alpha/7.8.664/

The following known problems exist:

- Change log is not complete (feel free to contribute)
- A compilation problem exists under OSX 10.6/7: pike_threadlib includes mach*.h, which causes an error.

Please feel free to get in touch with any comments or concerns.

Bill
bill-NuqkLFvhzZFg9hUCZPvPmw&amp;lt; at &amp;gt;public.gmane.org
&lt;/pre&gt;</description>
    <dc:creator>H. William Welliver III</dc:creator>
    <dc:date>2012-03-22T03:50:07</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.pike.devel/4430">
    <title>need permissions help on pelix</title>
    <link>http://comments.gmane.org/gmane.comp.lang.pike.devel/4430</link>
    <description>&lt;pre&gt;I'm trying to create some new release folders and unfortunately the permissions seem to be incorrect (I'm in the pike group):

$ ls -l /pike/data/ftp/pub/pike/
total 20
-rw-r--r--   1 nilsson  pike         804 Sep 14  2004 README
drwxrwsr-x  33 jhs      pike        1024 Mar 19 22:12 all
drwxr-sr-x  12 peter    pike         512 Jan  3  2011 alpha
drwxrwsr-x  14 peter    pike         512 Apr 16  2011 beta
drwxr-sr-x   2 jhs      pike         512 Aug 16  2002 contrib
drwxr-sr-x   2 jhs      pike         512 Aug  2  2002 docs
drwxr-sr-x   2 mast     pike        1024 Mar 19 22:06 latest-stable
drwxr-sr-x   2 jhs      pike         512 May 12  2001 libs
drwxr-sr-x   2 jhs      pike         512 Aug  2  2002 man
drwxr-sr-x   4 jhs      pike         512 Aug  2  2002 patches

Can someone help out with that?

Thanks,

Bill
&lt;/pre&gt;</description>
    <dc:creator>H. William Welliver III</dc:creator>
    <dc:date>2012-03-21T02:38:22</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.pike.devel/4424">
    <title>paging Peter Bortas</title>
    <link>http://comments.gmane.org/gmane.comp.lang.pike.devel/4424</link>
    <description>&lt;pre&gt;I don't have Peter's email address, so hopefully he's monitoring this…

I'd like to get working on a 7.8 release but don't really have any idea what's involved, aside from change log entries (which I'm working on, slowly). Anything you might have for me to go on in that department (even if it's a rough outline) would be greatly appreciated!

Bill
&lt;/pre&gt;</description>
    <dc:creator>H. William Welliver III</dc:creator>
    <dc:date>2012-02-16T04:00:45</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.pike.devel/4420">
    <title>compilation handler for multi-tenant applications: update</title>
    <link>http://comments.gmane.org/gmane.comp.lang.pike.devel/4420</link>
    <description>&lt;pre&gt;Hi all,

A few months ago, started a conversation about what I'll call multi-tenant 
applications: that is, a single pike process running multiple applications 
(perhaps including copies of a given application) with isolated program 
and module spaces. The idea is to provide a similar capability to that 
provided by Java's ClassLoader API.

That is, I'd like to be able to do the following:

                                pike
                +-----------------|-----------------+
                |                                   |
          thread a1...an                     thread b1 ... bn
     compilation handler a                compilation handler b
  loads classes for app1 instance 1  loads classes for app1 instance
       from location a,b                    from location a,c (perhaps)
      uses module foo.bar                  uses module foo.bar

            foo.bar              !=             foo.bar


            though it would perhaps be acceptable if

      object_program(foo.bar)    ==      &lt;/pre&gt;</description>
    <dc:creator>Bill Welliver</dc:creator>
    <dc:date>2012-02-08T23:19:45</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.lang.pike.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.lang.pike.devel</link>
  </textinput>
</rdf:RDF>

