<?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 about="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel">
    <title>gmane.comp.lang.dylan.gwydion.devel</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.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://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2182"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2181"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2180"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2179"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2178"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2177"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2176"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2175"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2174"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2173"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2172"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2171"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2170"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2169"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2168"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2167"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2166"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2165"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2164"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2163"/>
      </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://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2182">
    <title>Buildbot, and a minor Gwydion change</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2182</link>
    <description>For those who hadn't noticed, we've now got a Buildbot running. Right
now it does an automatic build whenever anything affecting Gwydion
Dylan 2.5.x is committed; automatic builds for Open Dylan will come
soon.  You can monitor what the Buildbot is currently up to at
http://www.opendylan.org/buildbot/ (trailing slash required).

Right now we have builders and build hosts for

- FreeBSD 8.0-CURRENT
- Debian GNU/Linux 4.0 (Etch)
- Mac OS X

If you have a persistent network connection and another one of the
platforms supported by Gwydion Dylan, and would like to volunteer a
build host, let me know in e-mail or IRC.

In order to improve the Buildbot "experience", I'd like to change the
Gwydion build system slightly to split the running of the test suites
out of the "make compile" target (the default target) and into a new
"make check" target.  This will make it easier to write some
customization code for Buildbot to scan the test report and include it
on the status page.

Diff follows.

Index: tools/shared-misc/</description>
    <dc:creator>Peter S. Housel</dc:creator>
    <dc:date>2008-08-29T05:41:11</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2181">
    <title>Re: Diff for Gwydion Dylan --dump-od switch</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2181</link>
    <description>Um, it looks like the mailing list word-wrapped that message, making  
it useless for patching.

Download "switch.diff" from http://public.me.com/d_j_v instead.


On Aug 21, 2008, at 6:18 AM, Dustin Voss wrote:

_______________________________________________
hackers mailing list
hackers&lt; at &gt;lists.opendylan.org
https://www.opendylan.org/mailman/listinfo/hackers

</description>
    <dc:creator>Dustin Voss</dc:creator>
    <dc:date>2008-08-22T22:44:52</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2180">
    <title>Re: Diff for Gwydion Dylan --dump-od switch</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2180</link>
    <description>For those who missed the comment on IRC, this patch adds a --dump-du  
switch to GD. This switch creates a .lib.du.txt file in addition to  
the .lib.du file. The .txt file is a human-readable version of  
the .lib.du file.

I had to add some features to the od-format library to get this to  
work, but these changes are all conditional and have no impact on pre- 
existing code. Specifically, I added an option to prevent loading  
objects from external data units, a &lt;extern-ref&gt; class to handle  
references to said objects that is only used when that option is  
enabled, and support for additional informational parameters to object  
loader functions.

The actual functionality of the --dump-du switch is in d2c/compiler/ 
main/text-du.dylan.

This patch also includes an HTML file, d2c/compiler/base/od-format- 
description.html, that describes the format of various dumped objects.  
Without this, the .txt file is mostly useless.


On Aug 21, 2008, at 6:18 AM, Dustin Voss wrote:

________________________________</description>
    <dc:creator>Dustin Voss</dc:creator>
    <dc:date>2008-08-22T22:09:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2179">
    <title>Diff for Gwydion Dylan --dump-od switch</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2179</link>
    <description>Index: compiler/main/main-unit-state.dylan
===================================================================
--- compiler/main/main-unit-state.dylan(revision 11909)
+++ compiler/main/main-unit-state.dylan(working copy)
&lt; at &gt;&lt; at &gt; -37,6 +37,8 &lt; at &gt;&lt; at &gt;
      required-init-keyword: command-line-features:;
    constant slot unit-log-dependencies :: &lt;boolean&gt;,
      required-init-keyword: log-dependencies:;
+  constant slot unit-log-text-du :: &lt;boolean&gt;,
+    required-init-keyword: log-text-du:;
    constant slot unit-target :: &lt;platform&gt;,
      required-init-keyword: target:;
    constant slot unit-no-binaries :: &lt;boolean&gt;,
Index: compiler/main/main.dylan
===================================================================
--- compiler/main/main.dylan(revision 11909)
+++ compiler/main/main.dylan(working copy)
&lt; at &gt;&lt; at &gt; -92,6 +92,7 &lt; at &gt;&lt; at &gt;
  "       -D, --define:      Define conditional compilation features.\n"
  "       -U, --undefine:    Undefine conditional compilation features. 
\n"
  "       -M, --log-deps:    Log dependencies t</description>
    <dc:creator>Dustin Voss</dc:creator>
    <dc:date>2008-08-21T13:18:23</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2178">
    <title>Library information file</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2178</link>
    <description>_______________________________________________
hackers mailing list
hackers&lt; at &gt;lists.opendylan.org
https://www.opendylan.org/mailman/listinfo/hackers
</description>
    <dc:creator>Dustin Voss</dc:creator>
    <dc:date>2008-08-04T03:43:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2177">
    <title>Re: socket error patch</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2177</link>
    <description>Carl Gay schrieb:

The thing that's jumping to my attention is that strerror() is not 
thread-safe.  You should use strerror_r() instead, which is reentrant.

Andreas
_______________________________________________
hackers mailing list
hackers&lt; at &gt;lists.opendylan.org
https://www.opendylan.org/mailman/listinfo/hackers

</description>
    <dc:creator>Andreas Bogk</dc:creator>
    <dc:date>2008-07-02T11:18:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2176">
    <title>socket error patch</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2176</link>
    <description>Could someone look over the attached patch before I commit it?  It
just tries to give a better error than "socket error 13".  Ultimately
I think we want to create real high-level conditions for this sort of
thing, but I figure this is a good start for now.  In particular, did
I get the C types right in linux-portability.dylan?  Thanks.

-Carl

ps. I don't have access to BSD, so can someone volunteer to implement
unix-strerror there?  Should be simple.

pps. I forgot to add unix-strerror to win32-portability.dylan (as odd
as that sounds) so I'll do that now but you won't see it in the patch.
_______________________________________________
hackers mailing list
hackers&lt; at &gt;lists.opendylan.org
https://www.opendylan.org/mailman/listinfo/hackers
</description>
    <dc:creator>Carl Gay</dc:creator>
    <dc:date>2008-07-02T10:04:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2175">
    <title>Re: status of DUIM</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2175</link>
    <description>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA384

Hi,

Kosta Welke wrote:

Well, we simply wrapped the class hierarchy of GObject as well as the
interfaces into a Dylan class hierarchy. So, no up/downcasts are needed.


Yes. Our GTK port uses one thread per window plus one thread for the
event loop. The threading is not an issue anymore on Open Dylan, we
traced the cases down and did proper locking for the gtk calls.


Great.


No, the gtk-2 is deprecated and no longer needed (removed from the
repository). It contained a binding for Open Dylan using meta, and no
type hierarchy.

As talked on IRC, setting OPEN_DYLAN_USER_REGISTRIES to
fundev/sources/registry solved this issue.


Yep. It generates .intr files, which are passed to melange; as well as
Dylan code which defines property-accessors.


Happy hacking,

Hannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIZ9qFRcuNlziBjRwRCdK9AKCqaJHkEcocwKIbKO2ZzTbdFmjtpQCbBhHu
CTNBqy2Gs2WFlWR4rx0N4GE=
=B+oa
-----END PGP SIGNATURE-----
_______</description>
    <dc:creator>Hannes Mehnert</dc:creator>
    <dc:date>2008-06-29T18:55:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2174">
    <title>Re: status of DUIM</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2174</link>
    <description>

Cool!


Nice. I never did anything with GTK (but lots of stuff with Qt), so this 
whole GObject thing is new to me. But it seems that you already did the 
hard stuff :)

in that post you wrote:

You said in chat that you use one thread per window. It looks to me that 
GTK, like Qt, and uses *one* event loop for everything (all windows, 
widgets, whatever). But I'll look into that after dealing with some very 
basic stuff. Maybe like adding colors.


Cool! Less branches to get confused with! :)


I tried to build a couple of stuff.

qa/test-apps/duim-test-suite ran and showed me lots of stuff to work on.

But:
Everything else would not build. I always get either one of the 
following errors:

| $ opendylan -build sources/duim/examples/reversi/reversi.lid
[...]
| Opened project reversi
| Internal error: : No such file or directory: Can't get the
| modification date of
| /usr/local/opendylan-1.0beta4/sources/gtk-2/gobject-2/gobject-2.lid
| Exiting with return code -1

I dont even have a gtk-2 folder, is it in</description>
    <dc:creator>Kosta Welke</dc:creator>
    <dc:date>2008-06-29T17:30:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2173">
    <title>Re: Registry project loaded from install directory?</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2173</link>
    <description>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA384

Hi Carl,

Carl Gay wrote:

I can't reproduce that bug. My opendylan uses the testworks from
fundev/sources (because that is the first in the environment variable).

Do other projects load fine? What happens when you rename the sources
directory at c:\program files\open dylan ? Does Open Dylan load
testworks from somewhere else? Or can't it find it anymore?


Regards,

Hannes

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIZYdTRcuNlziBjRwRCSlwAKC1e3RQzRnLizQZSzATweMia2B78ACeOh6f
U19/9/sQtbE+uJhNIiwOuwc=
=s34X
-----END PGP SIGNATURE-----
_______________________________________________
hackers mailing list
hackers&lt; at &gt;lists.opendylan.org
https://www.opendylan.org/mailman/listinfo/hackers

</description>
    <dc:creator>Hannes Mehnert</dc:creator>
    <dc:date>2008-06-28T00:35:31</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2172">
    <title>Re: status of DUIM</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2172</link>
    <description>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA384

Hi,



Kosta Welke wrote:

great.



which is outdated.

I merged my thougts into a wiki page,
http://wiki.opendylan.org/wiki/view.dsp?title=Project%3A%20DUIM%20GTK


This does not reflect the state of the code. More than a year ago I
posted "GTK+2 DUIM port" on comp.lang.dylan
http://groups.google.de/group/comp.lang.dylan/browse_thread/thread/4ac39fe2decd41cf

Changes to that mail are:
 *the whole stuff (ok, apart from modified melange) has been merged back
to trunk
 -&gt; code is at fundev/sources/gtk and fundev/sources/duim/gtk
 -&gt; branches/opendylan-melange contains the melange
 -&gt; you no longer need to modify your registry
 *from the "Some stuff which has to be done" list, the first three items
   have been actively worked on, as well as on Fonts
Open items are Colors, Pixmaps, Layouting.

But you can just use the duim-gui-test-suite and look what's broken.


Yes, well, probably the way would be:
 *trace opendylan-melange changes back to melange for gwydion
</description>
    <dc:creator>Hannes Mehnert</dc:creator>
    <dc:date>2008-06-28T00:15:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2171">
    <title>Re: status of DUIM</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2171</link>
    <description>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA384

Hi there,

Daniel Brumbaugh Keeney wrote:

No, Open Dylan also doesn't use C3 linearization. I just committed a lid
file and library for examples/linearization which shows the following
output:
The linearization in this compiler seems to be Dylan
The CPL is: #({class &lt;editable-scrollable-pane&gt;}, {class
&lt;scrollable-pane&gt;}, {class &lt;editable-pane&gt;}, {class &lt;pane&gt;}, {class
&lt;editing-mixin&gt;}, {class &lt;scrolling-mixin&gt;}, {class &lt;object&gt;})


hannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIZWblRcuNlziBjRwRCdlKAKCYKHSJmpGGU22o7yV1Rryoatu46ACgtx6J
6wrJCXEvAx0Gy0/sWkXYY5s=
=4FsU
-----END PGP SIGNATURE-----
_______________________________________________
hackers mailing list
hackers&lt; at &gt;lists.opendylan.org
https://www.opendylan.org/mailman/listinfo/hackers

</description>
    <dc:creator>Hannes Mehnert</dc:creator>
    <dc:date>2008-06-27T22:17:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2170">
    <title>Re: status of DUIM</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2170</link>
    <description>
Well all the hype I got was from Andreas Bogk.

But yeah, it gets mentioned surprisingly often. Like here:

http://steve-yegge.blogspot.com/2007/02/next-big-language.html

Cheers,

Kosta
_______________________________________________
hackers mailing list
hackers&lt; at &gt;lists.opendylan.org
https://www.opendylan.org/mailman/listinfo/hackers

</description>
    <dc:creator>Kosta Welke</dc:creator>
    <dc:date>2008-06-27T18:24:23</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2169">
    <title>Re: status of DUIM</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2169</link>
    <description>
I've found Dylan gets referenced surprisingly frequently, usually in
passing references to it's object model, being a lisp descendant with
non-lisp syntax (and keeping macros), or originating the C3 method
resolution order. (btw, does Dylan actually use C3? This bug:
https://www.opendylan.org/cgi-bin/bugzilla/show_bug.cgi?id=7044 makes
it look like d2c doesn't implement it, and I can't find references for
OpenDylan.) Personally, I think Dylan could use a little hype. :)

Daniel Brumbaugh Keeney (aka db-keen)
_______________________________________________
hackers mailing list
hackers&lt; at &gt;lists.opendylan.org
https://www.opendylan.org/mailman/listinfo/hackers

</description>
    <dc:creator>Daniel Brumbaugh Keeney</dc:creator>
    <dc:date>2008-06-27T17:57:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2168">
    <title>Re: status of DUIM</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2168</link>
    <description>There is hype?!  :-)

On Jun 27, 2008, at 4:13 AM, Kosta Welke wrote:


_______________________________________________
hackers mailing list
hackers&lt; at &gt;lists.opendylan.org
https://www.opendylan.org/mailman/listinfo/hackers

</description>
    <dc:creator>Dustin Voss</dc:creator>
    <dc:date>2008-06-27T14:53:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2167">
    <title>status of DUIM</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2167</link>
    <description>Hi there!

I recently could not resist the Hype anymore and had to try out dylan. 
It seems like a very nice language (from the extended hello-world i 
wrote) and solves many problems and annoyances I recently had in C++.

However, the lack of GUI in linux is simply unacceptable.

According to http://www.opendylan.org/gui.phtml

- opendylan: has outdated GTK+ Bindings. Should be updated to GTK+ 2.x. 
Some work has been done

Question: Is trunk/fundec/sources/gtk the newest version? What exactly 
is broken and how do I find it? Seems like hannes did something about 
gtk 2 about 4 months ago...

- gwydion dylan: needs work on melange, wrappers for GLib, GDK, GTK+, 
GNOME, dylan-like interfaces, and someone needs to implement DUIM.

Questions: Where can I find the unfinished work? Why would we need to 
wrap GLib, GDK? Wouldnt it, as a first step, just suffice to write some 
DUIM wrappers around GTK+? Or does GTK+ expose a lot of these internals?

Also, cant we just use most of the opendylan DUIM code for GTK+?
</description>
    <dc:creator>Kosta Welke</dc:creator>
    <dc:date>2008-06-27T11:13:40</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2166">
    <title>Registry project loaded from install directory?</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2166</link>
    <description>When I do Internal -&gt; Open Registry Project... -&gt; testworks, OD loads
the testworks project from my OD installation directory (i.e.,
C:\Program Files\...) rather than from where the registry entry says
to load it from.

These are my environment variables:

OPEN_DYLAN_USER_REGISTRIES=C:\cgay\dylan\trunk\libraries\registry;C:\cgay\dylan\trunk\fundev\sources\registry
OPEN_DYLAN_USER_ROOT=C:\cgay\dylan\user-root


I'm using the win32-environment I built from trunk, starting it with
"batch-debug win32-environment".  Can anyone shed any light on why
this might be happening?

Thanks.
-Carl
_______________________________________________
hackers mailing list
hackers&lt; at &gt;lists.opendylan.org
https://www.opendylan.org/mailman/listinfo/hackers

</description>
    <dc:creator>Carl Gay</dc:creator>
    <dc:date>2008-06-18T15:45:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2165">
    <title>CCC meets HPI? --- or what are ways to fund Dylan</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2165</link>
    <description>_______________________________________________
hackers mailing list
hackers&lt; at &gt;lists.opendylan.org
https://www.opendylan.org/mailman/listinfo/hackers
</description>
    <dc:creator>Peter Robisch</dc:creator>
    <dc:date>2008-06-15T11:37:49</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2164">
    <title>Re: Blog post on my Dylan-related projects</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2164</link>
    <description>Hallo Peter,

  Your blog (http://housel.livejournal.com/610.html ) contains many good
ideas to reinvent programming.

From my point of view I suggest to get in contact to

            Viewpoints Research Institute (VPRI), 
            1209 Grand Central Avenue, Glendale, CA 91201
            tel: (818) 332-3001 fax: (818) 244-9761

VPRI published an interesting report.
     
     STEPS Toward The Reinvention of Programming
     First Year Progress Report, Dec 2007

The report is accessible via http://vpri.org/pdf/steps_TR-2007-008.pdf 

I recommend a contact because

* you are very smart in think of steps towards the reinvention of
programming   (and that's the topic of the STEPS project of VPRI.
* you will meet at VPRI a principal investigator who knows the Harlequin
Dylan project well (Ian Piumarta).

and because 

* VPRI reached an interesting level of acceptance, they got accepted by
Funders (see page 4 of in the quoted report)

I wish you the best wishes for your future. Especially I wish you an
enviro</description>
    <dc:creator>Peter Robisch</dc:creator>
    <dc:date>2008-06-15T04:41:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2163">
    <title>Blog post on my Dylan-related projects</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2163</link>
    <description>In case people are interested, I have posted at 
http://housel.livejournal.com/610.html a detailed list of many of the 
Dylan-related subprojects I'm working on or thinking about.

Cheers,
-Peter-

_______________________________________________
hackers mailing list
hackers&lt; at &gt;lists.opendylan.org
https://www.opendylan.org/mailman/listinfo/hackers

</description>
    <dc:creator>Peter S. Housel</dc:creator>
    <dc:date>2008-06-06T21:25:14</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2162">
    <title>Re: Delivery Status Notification (Failure)</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.dylan.gwydion.devel/2162</link>
    <description>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA384

Hi,

Carl Gay wrote:

yes. They changed because of the PRNG issue in Debian
(http://www.debian.org/security/2008/dsa-1571); The new fingerprints are:
37:91:f3:4b:98:d0:cb:7e:15:c4:b0:a0:d5:3f:83:a8 (DSA)
d8:c1:ca:c8:53:eb:8c:4d:54:9f:11:1f:69:95:8a:6f (RSA)


Hannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFILLnfRcuNlziBjRwRCc3xAKCfyVNawPR/OQJbJpFr54UOOXzFpgCgnwiQ
6yqcZJ67b4kmj/2GjUq52aA=
=t1og
-----END PGP SIGNATURE-----
_______________________________________________
hackers mailing list
hackers&lt; at &gt;lists.opendylan.org
https://www.opendylan.org/mailman/listinfo/hackers

</description>
    <dc:creator>Hannes Mehnert</dc:creator>
    <dc:date>2008-05-15T22:32:00</dc:date>
  </item>
  <textinput about="http://search.gmane.org/?group=$group=gmane.comp.lang.dylan.gwydion.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.dylan.gwydion.devel</link>
  </textinput>
</rdf:RDF>
