Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 18:43
    housel opened #1463
  • Nov 25 19:56

    housel on master

    release-notes: Add missed entri… (compare)

  • Nov 25 16:44

    housel on master

    dfmc-optimization: Fix the self… Merge pull request #1462 from h… (compare)

  • Nov 25 16:44
    housel closed #1462
  • Nov 25 05:28

    cgay on master

    Hacker Guide: fix broken link Bump copyright to 2022 Bump version to 2022.1 * 2020.… and 1 more (compare)

  • Nov 25 04:55
    housel opened #1462
  • Nov 25 03:42

    cgay on master

    2022.1.0 release notes: preppin… (compare)

  • Nov 25 03:10
    housel labeled #1461
  • Nov 25 03:10
    housel opened #1461
  • Nov 24 22:44

    abeaumont on add-missing-newline

    (compare)

  • Nov 24 22:44

    abeaumont on master

    Add missing newline when no sub… Merge pull request #30 from dyl… (compare)

  • Nov 24 22:44
    abeaumont closed #30
  • Nov 24 21:22
    pedro-w closed #29
  • Nov 24 21:22

    pedro-w on master

    Implement reference provider Changes from code review Merge pull request #29 from ped… (compare)

  • Nov 24 21:22
    pedro-w synchronize #29
  • Nov 24 20:05

    cgay on master

    Update dylan-tool submodule and… Update testworks submodule to v… Add testworks release notes (compare)

  • Nov 24 04:17
    cgay closed #42
  • Nov 24 02:12
    cgay commented #42
  • Nov 24 02:11
    cgay opened #43
  • Nov 24 01:47
    cgay opened #42
Alfredo Beaumont
@abeaumont
emacs gives me a list to choose from with two items, one for the generic function and one for the specific method, but it points to the wrong lines and the wrong content, as the two versions of the file are different.
Alfredo Beaumont
@abeaumont
right window shows the list, it takes the lines from the file in ext/command-line-parser/command-lne-parser.dylan (shown in the left window, L708 at the top), but the content from /opt/opendylan/sources/lib/command-line-parser/command-line-parser.dylan
Carl
@carlgay:matrix.org
[m]
ok, thanks. That should be enough to track it down. (after dinner!)
Carl
@carlgay:matrix.org
[m]
@abeaumont: was OPEN_DYLAN_USER_REGISTRIES set?
Carl
@carlgay:matrix.org
[m]
Do we know who "kryptine musicdenotation@..." is? (The person who updated the MPS license.)
Peter S. Housel
@housel
I don't
Carl
@carlgay:matrix.org
[m]
Adding the credits to release notes. I just put "kryptine" and "phongphan".
Carl
@carlgay:matrix.org
[m]
@housel: I think what's left for the release (other than doing the actual builds) is (a) choosing versions to use for release-with-batteries.sh, (b) adding the release date to 2022.1.rst, (c) if you need to add more release notes for work you've done.
Peter S. Housel
@housel
Exactly
I’m fiddling with release-with-batteries now
Alfredo Beaumont
@abeaumont
@carlgay:matrix.org hmmm, no it wasn't. I created a workspace.json in the repo set to {"default-library": "dylan-lsp-server"}, maybe that changed the lookup of registries?
Carl
@carlgay:matrix.org
[m]
@abeaumont: to decide the working directory of the compiler we first look for a workspace.json and use its directory, then fall back to looking for a "registry" directory and use its containing directory.
(We should really stop doing anything with working-directory() and set the personal-root I guess.)
Carl Gay
@cgay
@kavalogic-inc_gitlab If I were to work on the style guide in earnest I guess I would move it to my own repo and essentially try to describe what I do myself and maybe try to justify it a little. I suppose the main use would be to give guidance to newcomers, as opposed to brow-beating people into using my style. (But my style is best and you should all follow it.)
Without re-reading the style guide, my recollection is that it's a mish-mash and some of it is out of date.
Carl
@carlgay:matrix.org
[m]
TIL: git diff --color-moved
Peter S. Housel
@housel
I took care of filling in missing release notes
Carl
@carlgay:matrix.org
[m]
Since you'll be doing most of the release building, what date shall we put on them? How about tomorrow? I'm happy to build x86_64-linux if it helps.
Peter S. Housel
@housel
I will need to test the batteries included build on x86_64-linux anyway; I’ll try to have that done by tonight
Traveling today and tomorrow, and I couldn’t get my RISC-V system booted before we left, so that build might have to wait a bit
(The AArch64-Linux system is running though)
Carl
@carlgay:matrix.org
[m]
ok, let me know if you need anything. I'm just working on LSP.
Carl
@carlgay:matrix.org
[m]
It's annoying that flymake changes all my code to red or orange when I save broken intermediate results. Eventually I want to find a way to display compiler warnings in a less intrusive way.
Peter S. Housel
@housel
I’ve overhauled build-with-batteries.sh enough that it builds LLVM 15.0.5 and bdwgc 8.2.2 on FreeBSD; testing it now on x86_64-linux
Carl Gay
@cgay
huh, 15.0.3 was the newest one on their download page yesterday. bleeding edge...
Peter S. Housel
@housel
Simplified things somewhat in that it no longer tries to use binary builds of LLVM, and it can now use the libunwind included in the base LLVM release (last time we needed fixes beyond what was in 10.0)
I may still need you to do the x86_64-linux build on Debian, since the only x86_64-linux VM I currently have is Ubuntu 22.4LTS, and Debian works better as a lowest-common denominator
Carl
@carlgay:matrix.org
[m]
ok, I'll check in the morning. I assume you'll submit the batteries changes.
Peter S. Housel
@housel
Yes
Peter S. Housel
@housel
x86_64-linux worked; I do still need to test macOS though
Peter Hull
@pedro-w
I tried to build on mac from a fresh git clone and I got
fdmake: build product /tmp/opendylan/_build/Bootstrap.3/sbin/dylan-tool missing
Peter S. Housel
@housel
Hmmm… That’s using the C back-end
Peter Hull
@pedro-w
I've got LLVM 15.0.3 installed, that's new enough isn't it
I've added config.log to the gist, at around line 593 there is a segfault running clang which I think causes configure to think LLVM isn't available
Peter S. Housel
@housel
I’m building the batteries-included on macOS so I can see if that works
XCode clang can compile the config test bitcode at least
Peter Hull
@pedro-w
I'm on a quite old MacOS (10.15). I've set CC & CXX to point to homebrew's version of clang and am retrying. I'll let you know, as it will take a while to get as far as stage 3 again
Peter S. Housel
@housel
I’m running Ventura, and I happen to be in Ventura at the moment
Peter Hull
@pedro-w
Hmm, I wish I was in Catalina! MacOS Manchester ... I can see why Tim Cook didn't go for that naming scheme
Peter S. Housel
@housel
I had to tweak build-with-batteries.sh a bit for the LLVM build, but once I did that it worked
Peter Hull
@pedro-w
OK, setting CC to homebrew's clang fixed it (at least, the build process completes without error) :thumbsup:
Carl
@carlgay:matrix.org
[m]
I'm doing a Linux build while I go out and "move biomass from here to there", as one does in a New England Autumn.
oh, I assumed you'd pushed build with batts already.
Peter S. Housel
@housel
It’s on a branch, waiting for one more small tweak
Carl
@carlgay:matrix.org
[m]
@pedro-w: The model I'm working with now for lsp-dylan is to store the project associated with each file in the <document> class. If the user sets a default project then that will take precedence, but if they don't, then multiple projects may be opened. (As a side-effect we get rid of the global variables like *project*, which I know were just there for getting this whole thing bootstrapped. \o/)
Peter S. Housel
@housel
Pushed the build-with-batteries PR (sitting in the car as my wife drives home)
Peter Hull
@pedro-w
@carlgay:matrix.org right, *project* et al were copied over from the dswank code.