Re: Getting started with OpenDylan
Hannes Mehnert <[email protected]> Fri, 18 Oct 2013 12:11:15 +0200
| Newsgroups | gmane.comp.lang.dylan.gwydion.devel |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 Hi, sorry for the late reply. On 10/15/2013 00:15, Greg Miller wrote: > On 10/13/13, Bruce Mitchener <[email protected]> wrote: >> On Mon, Oct 14, 2013 at 10:08 AM, Greg Miller >> <[email protected]> wrote: >>> (3) Do I really need to manually edit variables in my .emacs >>> and my environment path every time I add a new project in order >>> to get this "registry" thing added? Or am I missing something? >>> >> >> The compiler will look in the current working directory for a >> registry and use that to supplement what is in the installation >> directory. What I normally do is to use git submodules to pull >> in dependencies and then set up a local registry to handle >> things. This way, there isn't a need to maintain an >> OPEN_DYLAN_USER_REGISTRIES environment variable. > > That's good. It seemed like a potential headache. I'm still unclear > on what the registries are for and how to use them correctly, > though. I'll have to play around with it. > > That being said, this does all raise the barrier to entry a bit > more. There are tons of other development environments out there > for various languages that manage to support large projects while > still supporting the "compiler -o hello-world hello-world.ext ; > ./hello-world" paradigm. > >> I don't use emacs, so I don't know what you need to do there. > > Well, the page on dylan-mode, DIME, etc. seems to imply that it's > mandatory to set a registry path in your .emacs when you add > dylan-mode to your configuration. An adjustment to the wording > might be helpful. I believe I'm responsible that the wording is there in this form. The reason for this is that most users start emacs via some application launchers -- and thus do not get the environment variables from .bashrc/.tcshrc/profile. Furthermore, the working directory from which emacs is started is most of the time not where the Dylan projects are. Thus, it is in my opinion less confusing to ask users to provide an absolute path to their Dylan projects within .emacs. The problem solved by registries is locating libraries. A registry can provide platform-dependent library files (.lid). Meaning if you have several independent large projects, and a registry for each of them, you do not need to specify in any of the projects where the others are located on your disk. >>> (4) Once I finally got through all the steps to build and run >>> hello-world, it hung and pegged a processor core. I've tried a >>> lot of languages, but this is the first time I've failed to >>> build and run a Hello, world example. >>> >> >> Could you attach with gdb and give us a stack trace? > > I'll see what I can do. I'm happy to help here. Which FreeBSD version and platform are you on? i386? amd64? Hannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQIcBAEBCQAGBQJSYQlDAAoJELyJZYjffCju2/MQAKJt8MLwO0Yma5DDnaBIyISy 7hzmoyR0j79yw4Xm0aZjqJPlHtP9IsWG/5l2+DXf2RnDyBkhopHuf22cEWwAA4EW Jdciyf6/gbh0Yz9t4fqfH49LfplT8oCTaPUSkIfqDg8OCLsizh2BoYyp0HE2hAck kwcO9dB+t3HmunR7Cu8qWyuHCoBEmtxtUXcNoWhpZg8SE2DAoukXLqU9gymSMeaG Tj/UZUEm/OAOb/qB/1fGVBWbJDzrF72lEHKGZHwI5Mf/F29lx1JOShVnIY0eiuuW dLFckT/6z7jge74ZQfVD3UtKIaMn0ijyk60esxeGMZJ8gPsgK8As5iXy2CG715oA uvRV/wT0BACfh40YDen5hg6F2FzCgNNLW7X++EcaCagArg7lgiSijP1JtSlwSFbB hA5fZIV7atB0farowmdvwAJXs1qAbLAXo5JdhUyS/pV1/cnX8UtWhiLfJW64N8tX eiPqOJ6X1UaVFIURTMR/3Jg2drrPdhC2dipxNB9u48hORJX+XA3sDVui/tJ8Znzr wjzIfaXpZ1lJZzWyvMbTZiVN9UekvKebH7y9ry5YKKitSWijUq0UqpTNC5cgsmPu Oxu8g44aeFaySXuIAkbkNoGRFFABbccsEGYty88O6vgfN7CxRuQtf2w47fpWfjh/ KOEWtbzOLZzjtLWjTBCr =1mSg -----END PGP SIGNATURE----- _______________________________________________ hackers mailing list [email protected] https://lists.opendylan.org/mailman/listinfo/hackers