freenode/#lisp - IRC Chatlog
Search
2:59:39
specbot
user-homedir-pathname: http://www.lispworks.com/reference/HyperSpec/Body/f_user_h.htm
3:03:28
loke`
The glossary entry doesn't say much on the subject: http://www.lispworks.com/documentation/HyperSpec/Body/26_glo_v.htm#valid_pathname_directory
3:08:47
loke`
Pathnames are the worst part of CL. It's both grossly overengineered and at the same time woefully incomplete.
3:10:08
specbot
Restrictions on Examining a Pathname Directory Component: http://www.lispworks.com/reference/HyperSpec/Body/19_bbdc.htm
3:40:48
loke`
I know how it works. It's jsut that the LCM installation is missingt he runtime library, so I don't even have the + function :-)
4:53:38
atgreen
I get a "Heap exhausted during garbage collection" when I try to (ql:quickload 'lisp-binary). sbcl 1.3.5 on Fedora x86_64. Any ideas? How can help debug?
8:46:52
beach
Every time I have to restart my computer after having installed software updates, I am furious that we are still using operating-system technology from half a century ago.
8:50:38
beach
That would be better, yes, but the best thing would be to move closer to the 21st century.
8:52:56
beach
splittist: A while ago, you hinted that you might do something about my suggested documentation system, or did I misunderstand?
8:55:42
splittist
beach: yes, I'm slowly thinking about it. Or thinking about writing up some outline documentation to start with.
9:19:46
rk[ghost]
i will share more details in the future.. may be recruiting once some new momentum is achieved.. but me and a friend have been heavily discussing replacing the current stack from top to bottom. in essence come up with a 10 year plan to break out of this current industry driven cycle of being fed garbage...
9:22:13
beach
Sounds like a plan. Yes, there is lots of momentum, mainly because people don't seem to call into question their current ways of working.
9:22:25
SAL9000
rk[ghost]: when you say top-to-bottom do you mean Lisp OS and working your way up from there, or...?
9:22:25
Colleen
SAL9000: drmeister said 10 hours, 52 minutes, 46 seconds ago: The docker directory mounting worked perfectly on Windows this morning. The 'run-docker' script on 'widgets-dev' works without modification.
9:25:56
rk[ghost]
beach: i think it is more because people are swindled so much by $ that they accept writing asldkfj softwarez all day and only spend their efforts afterwords complaining at the bars:P
9:26:37
rk[ghost]
SAL9000: you aren't thinking big enough. gotta have a lisp machine before you have a lisp OS
9:27:23
jackdaniel
but the initial effort is driven by people who are simply dissatisfied with current state
9:27:32
rk[ghost]
beach: i /know/ that.. but my point was.. that some hardware will need to change.. my true focus isn't on CL.. although i enjoy it much
9:27:43
jackdaniel
whenever they direct their effort in good direction is a question for which each answer will be merely an opinion
9:28:00
rk[ghost]
much of what me and my friend have been discussing starts with the networking stack.. and that'll require a few changes to some hardware along wit hthe protocols and software
9:29:37
rk[ghost]
so i have been toying around with writing a basic lisp interpreter for RV32IMAC; besides McArthys papers.. any other good suggestion resources for the fundamentals of the metacircular evaluator and such?
9:31:17
beach
The only reason I can see to write a Lisp interpreter would be in order to learn about language implementation.
9:32:22
rk[ghost]
jackdaniel: fair points.. but in the end.. the industry drive overrules anything of interest that comes out of academia or discontent programmers
9:33:09
rk[ghost]
beach: well a good chunk of it is to get back in the programming mindset.. quit my job about 1.5 years ago to go farm..
9:33:57
jackdaniel
risky statement, I'd say that it adapts some of it, but overruling is rather a rare exception
9:34:05
beach
rk[ghost]: If all you want is to program, there are more useful things to write than another Lisp interpreter.
9:35:23
rk[ghost]
beach: aye, but sorta /need/ (surely it is a want, but meh) an interpreter to move on to the next step of my toy project..
9:36:06
rk[ghost]
think CCL would compile for RV32IMAC.. i suppose i could have just tried and found out..
9:37:39
rk[ghost]
i have a Hifive1.. and i really really would prefer not to have to write C for interfacing with it.. next step is to write code for a humidity / temperature sensor..
9:38:59
rk[ghost]
well.. without the interpreter.. how is the board suppose to evaluate lisp code i send over UART?
9:42:25
rk[ghost]
risc-v 32i (mac << you can ignore this mostly.. just specific modules) architecture
9:50:51
jackdaniel
you may put eval there and repl, that's not overly hard. My point is, that having simply interpreter on the machine won't give you much
9:51:28
jackdaniel
and it will be awfully slow and limited, while if you write compiler to run somewhere else, you could have for instance macros etc, which get compiled and uploaed into that machine
9:52:36
jackdaniel
if you are interested in simply running interpreter, check out uLisp, armpit scheme, microscheme - your description fits most uLisp imo
9:53:19
jackdaniel
rk[ghost]: then take uLisp, provide the lacking glue and don't waste time on making same thing over again
9:54:28
jackdaniel
but I'd say that in my opinion it's far from being a start for software/hardware revolution / redo in better manner
9:54:46
jackdaniel
just convenience hack to scratch the itch (i.e live coding and love for parenthesis:)
9:54:50
rk[ghost]
is there a good framework for message passing in CL? (i know there is LFE.. but since this is CL channel.. thought i would ask)
9:57:21
rk[ghost]
cross compiling doesn't seem to work for my use case.. as that assume that the hifive1 is connected to another machine..
9:59:14
rk[ghost]
jackdaniel: oh! this toy project for lisp interpreter on rv32imac has 0 to do with my previous statements of software/hardware revolution.
10:04:13
rk[ghost]
anyhoot- thanks again for ya'lls comments. i quite understand that any of my effort is superfluous..
10:11:06
jackdaniel
that's not true, writing interpreter is a good learning experience. But if you want just some lisp on the machine, much more effective way would be porting one of the mentioned languages to your machine
11:31:39
james__
; The symbol "HOST-ENT-ADDRESS-TYPE" is not external in the SB-BSD-SOCKETS package.
12:02:56
beach
My idea for testing the Earley-based lambda-list parsers is to create simple ad-hoc hand-written parsers with skimpy error checking, and then compare the results of applying both parser types to the same lambda list.
12:06:44
beach
It beats the alternative, which is to check that the parse tree is correct by manually parsing the input of every test case.