Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
Carl Gay
@cgay
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?)
Carl Gay
@cgay
early night for me. hasta mañana.
promovicz
@promovicz
indeed it doesn't. I'll add it. it seems like vim takes PRs via github these days.
any idea if neovim merges from vim or if I need to submit separately?
(floats are separate btw and they look correct)
Peter S. Housel
@housel
Do they handle d (<double-float>) or s (<single-float>) as well as e exponent?
promovicz
@promovicz
oh you can specify that!? is there an e for <extended-float> too?
Peter S. Housel
@housel
There's an x but we don't implement <extended-float> in OD
promovicz
@promovicz
I don't think it does. it misses the type specifier.
Peter S. Housel
@housel
e is just floating exponent without a type specified; DFMC picks a type based on how many digits of precision you include (not intuitive if you ask me)
promovicz
@promovicz
sure. I know we don't really do <extended-float>. I just recently considered adding it to marlais because it looked easy. which it isn't because libc and libm don't do a lot of long double.
while doing that I found out that single in C gets converted to double when you pass it to a varargs function.
that's why there is no format specifier for single.
Jon Godbout
@Slids
Okay, day 3 of AoC is done, anyone wishing to see pretty bad dylan code can look; https://github.com/Slids/advent-of-code-2021
question: Can I write lambdas in dylan?
Peter S. Housel
@housel
Yes, lambda is spelled method
    map(method(p) as(<directory-locator>, p) end,
        tokenize-environment-variable(path))
Jon Godbout
@Slids
tanks!
Jon Godbout
@Slids
having a programming language with the same name as a major artist leads to mediocre googling...
Carl Gay
@cgay
@housel what would be the best way to convert 8 big-endian bytes representing a two's complement int64 to a Dylan <integer>? I'm currently doing this: https://github.com/cgay/time/blob/master/tzif.dylan#L288 but it broken for a couple of reasons and I'm wondering if using <machine-word> and then coercing to integer would be a better way to go.
I can make it work with my current approach but getting the sign right and not overflowing unnecessarily is a bit finicky.
Carl Gay
@cgay
Just have a feeling I might be overlooking something obvious.
Peter S. Housel
@housel
No, that looks perfectly reasonable
Carl Gay
@cgay
ok :thumbsup:
promovicz
@promovicz
I plan to reintroduce "fluid" <big-integer> in Marlais. that will allow me to define anything from <byte> to <uint128> with no trouble. I wish it was that easy in OD. or is it?
I also stumbled once more over the question of where <byte-character> should be imported from. I remember having a conversation with bruce (IMO?) about this where he told me that it shouldn't matter much, and he is technically right. but I still find it a little bit annoying. I know it's not always trivial to do these changes, but I do think that they are worthwhile.
the characters should really just be in dylan. or common-dylan. it makes little difference to me.