gmane.comp.lang.dylan.gwydion.devel

Diff for Gwydion Dylan --dump-od switch

Dustin Voss — 2008-08-21T13:18:23

Index: compiler/main/main-unit-state.dylan =================================================================== --- compiler/main/main-unit-state.dylan(revision 11909) +++ compiler/main/main-unit-state.dylan(working copy) < at >< at > -37,6 +37,8 < at >< at > required-init-keyword: command-line-features:; constant slot unit-log-dependencies :: , required-init-keyword: log-dependencies:; + constant slot unit-log-text-du :: , + required-init-keyword: log-text-du:; constant slot unit-target :: , required-init-keyword: target:; constant slot unit-no-binaries :: , Index: compiler/main/main.dylan =================================================================== --- compiler/main/main.dylan(revision 11909) +++ compiler/main/main.dylan(working copy) < at >< at > -92,6 +92,7 < at >< at > " -D, --define: Define conditional compilation features.\n" " -U, --undefine: Undefine conditional compilation features. \n" " -M, --log-deps: Log dependencies t

Library information file

Dustin Voss — 2008-08-04T03:43:29

_______________________________________________ hackers mailing list hackers< at >lists.opendylan.org https://www.opendylan.org/mailman/listinfo/hackers

socket error patch

Carl Gay — 2008-07-02T10:04:48

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< at >lists.opendylan.org https://www.opendylan.org/mailman/listinfo/hackers

status of DUIM

Kosta Welke — 2008-06-27T11:13:40

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+?

Registry project loaded from install directory?

Carl Gay — 2008-06-18T15:45:39

When I do Internal -> Open Registry Project... -> 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< at >lists.opendylan.org https://www.opendylan.org/mailman/listinfo/hackers

CCC meets HPI? --- or what are ways to fund Dylan

Peter Robisch — 2008-06-15T11:37:49

_______________________________________________ hackers mailing list hackers< at >lists.opendylan.org https://www.opendylan.org/mailman/listinfo/hackers

Blog post on my Dylan-related projects

Peter S. Housel — 2008-06-06T21:25:14

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< at >lists.opendylan.org https://www.opendylan.org/mailman/listinfo/hackers

Me and IRC

Carl Gay — 2008-05-13T17:54:01

I don't have time to pay attention to #dylan anymore, so if you find a problem with my commits please either reply to my commit mail or send me email directly. I'll take a look at this: 80.244.253.241> make-regexp-positioner was renamed to ..-regex-... but where did translate go? < at >1206028618 193.34.25.61> could it have gone away entirely? < at >1206029688 80.244.253.241> http://article.gmane.org/gmane.comp.lang.dylan.gwydion.cvs/7119/match=translate < at >1206029696 80.244.253.241> there it got removed My recollection is that translate seemed to belong in string-extensions rather than regular-expressions, so I thought I moved it there, but I guess not. I'll try compiling melange to see what the problem is and fix it. -Carl _______________________________________________ hackers mailing list hackers< at >lists.opendylan.org https://www.opendylan.org/mailman/listinfo/hackers

logged-in?

Carl Gay — 2008-05-01T16:57:57

Hi. Does anyone know what replaced logged-in? in the web-framework library? It was removed in r11330 but I don't see what replaced it. Thanks. -Carl _______________________________________________ hackers mailing list hackers< at >lists.opendylan.org https://www.opendylan.org/mailman/listinfo/hackers

[hackers] simple build question on linux x86_64

Matthew Swank — 2008-04-24T02:40:02

Trying to compile the towers of hanoi example I get: Internal error: : Link failed: don't know how to build hanoi.o My build command is: /usr/local/opendylan-1.0beta5/bin/opendylan -build hanoi.hdp Where opendylan is a shell script similar to http://paste.lisp.org/display/44077 All the system dependencies seem to build ok. Matt _______________________________________________ hackers mailing list hackers< at >lists.opendylan.org https://www.opendylan.org/mailman/listinfo/hackers

wiki

Carl Gay — 2008-04-09T10:48:29

Does anyone know what the status of the wiki sources is? The code in libraries/network/wiki has been in a seriously broken state for quite some time now due to changes made in koala without updating all the callers. -Carl

Gwydion Dylan macro parsing error

Dustin Voss — 2008-02-15T03:06:20

Gwydion Dylan seems to have a bug in its macro processing, which I've logged as #7369. The problem is that final semicolons can't be omitted from a defining macro call. The bug includes a brief sample to demonstrate the problem, and Open Dylan doesn't have a problem. I think I've fixed it, but I wanted to run it past the group before checking it in. The code had special logic for semicolon-separated fragment matching vs. comma-separated fragment matching, and there may have been a reason for that which I'm unaware of. Anyway, since the comma-separated fragment matching code works as I expect from reading the DRM (p. 151-152, http://www.opendylan.org/books/drm/Patterns) , my proposed fix simply applies the same logic to both the semicolon- and comma-separated cases. Here is the diff: Index: d2c/compiler/parser/support.dylan =================================================================== --- d2c/compiler/parser/support.dylan(revision 11673) +++ d2c/compiler/parser/support.dylan(worki

compile error - GNU/Linux - "S_IFMT" undeclared

Danny Milosavljevic — 2008-02-09T19:45:12

Hi, I just tried to update Gwydion Dylan from SVN on my Gentoo Linux box and got this: ---------------------------------------------------- gcc -Wall -Wno-unused-variable -I. -O2 -fno-strict-aliasing - D_POSIX_C_SOURCE -I/var/tmp/portage/dev-lang/gwydion-dylan-2.4.99/work/ src/d2c/runtime -I/var/tmp/portage/dev-lang/gwydion-dylan-2.4.99/work/src -DGD_PLATFORM_LINUX -D_POSIX_C_SOURCE -I/var/tmp/portage/dev-lang/ gwydion-dylan-2.4.99/work/src/common/io -c /var/tmp/portage/dev-lang/ gwydion-dylan-2.4.99/work/src/common/io/unix-portability.c -o unix- portability.o /var/tmp/portage/dev-lang/gwydion-dylan-2.4.99/work/src/common/io/unix- portability.c: In function 'io_fd_info': /var/tmp/portage/dev-lang/gwydion-dylan-2.4.99/work/src/common/io/unix- portability.c:17: error: 'S_IFMT' undeclared (first use in this function) /var/tmp/portage/dev-lang/gwydion-dylan-2.4.99/work/src/common/io/unix- portability.c:17: error: (Each undeclared identifier is reported only once /var/tmp/portage/dev-lang/gwydion-dylan-2.4.

new type hierarchy encoding

Kim Barrett — 2008-02-09T16:01:02

Just received my PoPL 2008 proceedings yesterday; this might be of interest to some of you. "Extensible Encoding of Type Hierarchies", Alavi, Gilbert, & Guerraoui, PoPL 2008. Abstract: The subtyping test consists of checking whether a type t is a descendant of a type r (Agrawal et al. 1989). We study how to perform such a test efficiently, assuming a dynamic hierarchy when new types are inserted at run-time. The goal is to achieve time and space efficiency, even as new types are inserted. We propose an extensible scheme, named ESE, that ensures (1) efficient insertion of new types, (2) efficient subtyping tests, and (3) small space usage. On the one hand ESE provides comparable test times to the most efficient existing static schemes (e.g.,Zibin et al. (2001)). On the other hand, ESE has comparable insertion times to the most efficient existing dynamic scheme (Baehni et al. 2007), while ESE outperforms it by a factor of 2-3 times in terms of space usage.

Proposing several wiki instances for the community'swebpresence

Peter Robisch — 2008-02-04T09:06:04

Good morning, Open Dylan Community, In my last email I stated that I currently use the current wiki instance to prepare the content a new Dylan book only. I presented in that email also a short content outline for such a book. Several reader might have a belly or a head ache with this. So let me introduce you to the big picture I have in mind. As the title of this email states I'm proposing here several wiki instances for the community's webpresence. I especially see two additional instances: * dylan-annotated.opendylan.org * dylan-reference-request.opendylan.org IMHO: As soon as the wiki is based on the parser system Monday it is time to start these instances. == dylan-annotated.opendylan.org == * I first thought drm-annotated is the name for this instance, but now I think it is better to use this more general name: dylan-annotated * The content of the dylan-annotated instance is outlined in a way that it is mostly in parallel to the chapters of the DR

Why and how I use both paste.lisp.org and the wiki

Peter Robisch — 2008-02-03T21:12:06

== Ways to promote Dylan == Here I describe my thoughts of promoting Dylan: "Publish a Dylan book directed to students of Computer Science" could be a way. * My contribution to the wiki are motivated by this goal. - I believe that the outline of the wiki can be a good base for a new Dylan book - I don't believe that the content of the wiki will ever have a ready-to-print quality. - I have the hope that at one day the wiki contains enough content that it is easy for several Open Dylan Community members to join to write the book - Attached to the end of this mail you will a section "Outlining a Dylan Book Project" * This also means - I'm not interest to do earlier drafts inside the wiki. Under an earlier drafting I understand to write down a sudden inspiration. Other ideas which to not relate to the book idea in mind, I paste to the #dylan channel via paste.lisp.org.

Koala update

Bastian Müller — 2008-02-03T01:57:11

Hej, as already discussed in #dylan, i'd like to put some effort into koala. The changes include: (1) Replace the simple URI handling with a mostly RFC 3986 compliant URI library soon to be put into /libraries/. Currently, koala percent-decodes the whole URL, ie. destroys it. (2) Replace the date handling in the logging functions with format-date. (4) Create some macros that keep the URL <=> responder mappings at a central place. hannes suggested something like (including my ideas): define responders "/foo/" (regex) // with argument-regex (see below) begin method1; // several methods method2; method3 end, "/bar/" (regex) method4, "/baz/" () // without argument-regex method5, "/blub", // normal page-responder method6, ... where regex is an optional "argument-regex" for the URL that contains named groups that the responders get called with. Examp

Chinese Dispatch for Multimethods

Gabor Greif — 2008-01-04T12:20:45

Hi Bjarne, I have just noticed your paper "Open Multi-Methods for C++" . Therein you hint a possible implementation variant using the chinese remainder theorem. Incidentally, I had this idea more than 10 years ago and finally came around to put it in words for the 2002 Dylan Hackers' Conference in Berlin. There I held a short talk. Thereafter I wrote up something that resembles a paper and checked it in the Dylan repository. Here it is, you might be interested in skimming it and comparing it with your approach: Back then I was an active developer of the d2c Dylan compiler, but only as a hobbyist. The paper has never been finished, thus never published. It is in a very rough state (figures that are taken from example documents, etc.), please excuse me of sending you such a rubbish... I can also make it to a pdf if you are interested. All in all I am

new release of ex-harlequin compiler

Hannes Mehnert — 2007-12-17T08:27:49

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 Hi, I would like to make a new release of the former harlequin compiler this week (after merging the bigger part of branches/opendylan-melange back to the trunk) if no one has any objections (show stoppers, local changes which are important, etc.). We had a lengthy name discussion back in May, but I don't see obvious results how the compiler should be named. If anyone can enlighten me, please do. I started a wiki page which currently contains some changes from beta 4 to beta 5, please take a look and add changes which are missing: http://wiki.opendylan.org/wiki/view.dsp?title=Open%20Dylan%201.0%20Beta%205 I'll hopefully be able to do the linux and freebsd tarballs as well as the windows installer. Of course people who want to do packages (debian, ubuntu, you name it) are welcome. Eric Gouriou volunteered for the mac os X packages (and Dustin Voss will provide the tarballs as far as I can see). Happy hacking, Hannes -----BEGIN PGP SIGNATURE----- Version:

Invitation to the Dylan project tables at 24c3

Hannes Mehnert — 2007-12-09T07:12:35

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 Hi, there'll be some tables at this years Chaos Communication Congress (http://events.ccc.de/congress/2007/) reserved for the Dylan project. So, everyone who wants to join the conference and talk to Dylan people, feel invited. You can add yourself to the list of participants at http://events.ccc.de/congress/2007/Dylan . Happy hacking, Hannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHW5ViRcuNlziBjRwRCcAdAJ9zeb9BYslN/3n918bhNOGroJYZGgCdFZCD HyElLvAhO00hbbIE186VaV0= =YQBn -----END PGP SIGNATURE-----

Building latest Open Dylan for Mac OS X

Dustin Voss — 2007-12-08T10:33:23

Hey all. I have gotten Open Dylan to compile on Mac OS X. The diff (against revision 11530) is at . Applying the diff gives you build instructions in README.txt. I will do the check-in a few days from now. The sticking point was the copy-bytes argument order change in the core libraries. Originally, libraries from 1.0beta4 were being linked in to the latest version (I'll call it beta5) to fill in for beta5 libraries that hadn't been compiled yet. Because of the argument order change, the copy-bytes methods and their callers weren't always in agreement about which argument meant what. This led to core dumps and anguish. The solution was to rewrite parts of the build system. Beta5 gets rid of the 4 bootstrap stages and replaces it with a 2-stage process. In the first stage (the bootstrap stage), the beta4 libraries and compiler are used to build the minimal beta5 libraries and compiler. In the second stage (the insta