Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Sep 30 12:07
    memptr starred dylan-lang/opendylan
  • Sep 27 06:26
    elsvc starred dylan-hackers/marlais
  • Sep 26 03:57
    housel commented #1354
  • Sep 23 05:03
    elsvc starred dylan-lang/opendylan
  • Sep 22 23:02

    cgay on master

    Fix regular-expressions depende… (compare)

  • Sep 20 23:24

    cgay on master

    Fix lsp-dylan-test-suite regist… Update to latest dylan-tool Merge pull request #16 from cga… (compare)

  • Sep 20 23:24
    cgay closed #16
  • Sep 20 23:24
    cgay commented #16
  • Sep 20 18:57
    cgay opened #16
  • Sep 19 13:20
    esdnm starred dylan-lang/opendylan
  • Sep 19 04:49
    cgay closed #1373
  • Sep 19 04:49
    cgay commented #1373
  • Sep 19 04:46

    cgay on master

    libraries-test-suite: Stifle se… console compiler: exit with err… console compiler: add -allow-se… and 2 more (compare)

  • Sep 19 04:46
    cgay closed #1439
  • Sep 19 04:19
    cgay synchronize #1439
  • Sep 18 18:29
    cgay synchronize #1439
  • Sep 18 16:48
    cgay synchronize #1439
  • Sep 18 16:34
    cgay synchronize #1439
  • Sep 18 10:04
  • Sep 18 01:04
    Techcable starred dylan-lang/opendylan
Bruce Mitchener
@waywardmonkeys
I also need to dig up my design notes on a data fingerprinting / detection system ... would be relevant to some contract work that I'm doing (in Rust).
Where given lexical values, determine which possible types they might be, especially in the context of a column of data and a possible header / key name.
Which is also useful in the command stuff, since you want to take lexical values and convert them to useful types.
promovicz
@promovicz
ideally the command language should have three grammar levels: lexical (obvious, improve existing lexer), phrasal (some simple parser, pipes and command sequences, maybe blocks) and the command grammar. I'm on the fence about blocks because that would be a clone of unix shell. but why not. it's "easy" to do.
and then do object pipes and some table printing. and at some point do it in graphics because I like PowerGUI.
"given the time". but what exists in command-interface fits into that.
shorter-term goal: file completion. locators can't do it. that's a solvable problem.
and I'm going to generalize and remix the shell/editor classes so they are easy to use. that involves a trivial activity system on the terminal.
Bruce Mitchener
@waywardmonkeys
At the lexical level, I mean things like being able to specify "radians" and constrain the value appropriately ... or "latitude,longitude" or "64 bit address" or "x86_64 register name"
promovicz
@promovicz
(activities like on android - a stack of interactive widgets)
yeah, that sort of lexical option is why I allow for command grammar ambiguosity. that is specifically to allow for using external parsers and spares the command interface from any sort of lexing beyond string quoting.
Bruce Mitchener
@waywardmonkeys
(but also knowing that something is-a integer or is-a float or is-a string ... I had stuff like that kind back in the late 90s in a different command system ... it is occasionally tempting to just go back to that.
and yeah .. it would be separate, but I needed to find a good trait / design for integrating with completion and never ended up doing that.
promovicz
@promovicz
nice. I'm gonna turn in soon, but I'm glad for the insight.
Bruce Mitchener
@waywardmonkeys
I'd thought about using xsd types, I think ... but they have their own issues! there's a good need for stuff in this space.
Good night.
promovicz
@promovicz
klish goes the C route. some regex option support. limited to being router-cli like with no real language, not even pipes.
Bruce Mitchener
@waywardmonkeys
My daughter doesn't know it yet, but she needs the ability to execute some commands on some Arduino hardware to control her robotic car project via means other than Bluetooth LE.
I'm thinking about changing her from a tiny bit of C code to some Rust ... since I already do Rust on ESP32 ...
promovicz
@promovicz
@waywardmonkeys it's not for arduino but "oops I did that" - https://github.com/promovicz/qcli/blob/master/main.c
that code comes from deep embedded so it has no real dependencies except for stdio.
and it's less than 4k on x86, libc excluded.
Bruce Mitchener
@waywardmonkeys
Don't even need stdio ... some extra functions and a command enum will be enough for her for now, I think.
promovicz
@promovicz
sure :)
Jon Godbout
@Slids
Doing Advent of Code 2021 in Dylan this year (been meaning to try Dylan for a few years)
Carl Gay
@cgay
Hey Jon. (^^ the co-worker I was talking about)
I mentioned you were trying it out again.
Jon Godbout
@Slids
Amazing how muhc longer simple things take in a new language...
Carl Gay
@cgay
indeed
Carl Gay
@cgay
Interesting...even if I fix make-dylan-app AOC-1 to work, OD can't find the project file, apparently due to uppercase in the name. aoc-2 works fine.
It's something in the registry code because point OD at the .lid file works, though the compiler does downcase the name for output.
promovicz
@promovicz
@Slids welcome!
things might take longer in a new language, but then things are actually easier in some languages. Dylan does that for some things. especially complicated things IMO.
Jon Godbout
@Slids
For context I'm a common lisp dev at Google/ITA
Question: The dylan-emacs-mode github repo said it's available in melpa, but I couldn't find it, has it been removed?
and thanks for the welcome!
promovicz
@promovicz
@Slids are you on melpa-stable? I think I remember the dylan modes not being in there (yet).
so idk (I usually use blaze in the google monorepo)
promovicz
@promovicz
they are actually on melpa-stable. I just checked. would have created a ticket if they weren't present. :)
Jon Godbout
@Slids
okay, I see it now,
The thing I noticed first is how much easier it was to install Dylan now then when I tried in 2018
promovicz
@promovicz
it used to be just a simple tarball before that. I wasn't around during that time. LLVM support probably complicated things for a while.
opendylan shares the problem of needing bootstrap compilers with lisp of course.
Peter S. Housel
@housel
LLVM support wasn’t fully enabled until 2019
Jon Godbout
@Slids
It may have been 2019, probably was as I was at ELS and it was the first time I was away from my newborn
@cgay may remember?
Carl Gay
@cgay
fraid not
promovicz
@promovicz
I think I found a bug in the dylan vim highlighter.
-syn match      dylanNumber             "\<[0-9]\+\>\|\<0[xX][0-9a-fA-F]\+\>\|\<0[oO][0-7]\+\>"
+syn match      dylanNumber             "\<[0-9]\+\>\|\<#[xX][0-9a-fA-F]\+\>\|\<#[oO][0-7]\+\>"
Carl Gay
@cgay
Looks like it.
(Does it have #b?)