Interactive Common Lisp Development

Post by [deleted] » Tue, Nov 21, 2023, 7:12 PM UTC

IKantRead wrote: post #18

jimbokun wrote: post #16

Earlier quoted context omitted.

But is there is something inherent to Lisp that makes it "clunky" to work with matrices? Lisp can be at least as high level and expressive as any other language.

> But is there is something inherent to Lisp that makes it "clunky" to work with matrices? s-exps are basically coding at the level of the AST, which for many programming tasks is a powerful level of both abstraction and control. But this interface tends to work much better on tree-like structures (the most simple of which is the list, which in it's simplest case is a cons cell, Lisp's most fundamental particle). Mos…

Post by trealira » Tue, Nov 21, 2023, 8:30 PM UTC

medo-bear wrote: post #29

IKantRead wrote: post #18

Earlier quoted context omitted.

> But is there is something inherent to Lisp that makes it "clunky" to work with matrices? s-exps are basically coding at the level of the AST, which for many programming tasks is a powerful level of both abstraction and control. But this interface tends to work much better on tree-like structures (the most simple of which is the list, which in it's simplest case is a cons cell, Lisp's most fundamental particle). Mos…

I think matlab has the most succint language for writing matricies [1 2 3; 4 5 6; 7 8 9] then lisp #2A((1 2 3) (3 4 5) (7 8 9)) then python comma freak show [[1,2,3],[4,5,6],[7,8,9]] python's greatest achievement was bringing open source to matrix calculations and dethroning matlab. python is what it is today because it offered 99% of what matlab offered in open source and for $0 to uni students

  julia> [1,2,3] # An array of `Int`s
  3-element Vector{Int64}:
   1
   2
   3

  julia> [1:2, 4:5] # Has a comma, so no concatenation occurs.
  2-element Vector{UnitRange{Int64}}:
   1:2
   4:5

  julia> [1:2  4:5  7:8]
  2×3 Matrix{Int64}:
   1  4  7
   2  5  8

  julia> [[1,2]  [4,5]  [7,8]]
  2×3 Matrix{Int64}:
   1  4  7
   2  5  8

  julia> [1 2
          3 4]
  2×2 Matrix{Int64}:
   1  2
   3  4

  julia> a=[1 2 5 8 9; 3 4 2 1 33]
  2×5 Array{Int64,2}:
   1  2  5  8   9
   3  4  2  1  33

Post by yourapostasy » Tue, Nov 21, 2023, 9:34 PM UTC

vindarel wrote: post #4

To really discover what interactive, image-based CL development is about, my pointers: - https://www.youtube.com/watch?v=jBBS4FeY7XM (5min) my demo to show how to resume execution of a long running program, from the stack frame right before the bug, after having fixed and recompiled the function, without quitting the debugger hence without stopping the program, thus without restarting everything from zero. - https://…

Post by lenkite » Tue, Nov 21, 2023, 9:57 PM UTC

medo-bear wrote: post #31

lenkite wrote: post #23

Earlier quoted context omitted.

Python evolves through PEP's https://peps.python.org . Can you kindly correct my deplorable ignorance and point me to the Common LISP enhancement proposals ? Maybe I am missing something elementary.

i think it is more correct to say that machine learning saved python https://lwn.net/Articles/843660/

Post by ngcc_hk » Wed, Nov 22, 2023, 1:06 AM UTC

brabel wrote: post #26

ngcc_hk wrote: post #10

Earlier quoted context omitted.

If you look at the top post you can understand the disappointment when I click this link and got that. Yes there are a lot of content. Just the topic is …

For someone who knows Common Lisp but rarely plays with the redefinitions mentioned in the post, it's quite enlightening to learn those things. If you're not into Common Lisp you're definitely not the target audience for a post looking at the weird details of it like this one.