Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - karijes

Pages1
#1
newLISP newS / Re: Crashing stable and development version on 64bit platfor
January 28, 2014, 06:50:11 PM
QuoteAlso, the -ltermcap and -lncurses specs are pretty old. I wonder if we still need them on Slackware and other Linux when -lreadline is present.

-ltermcap is still needed. I compiled the code without -lncurses.



Sorry for dumb questions, but I'm just curious why don't you rely on autoconf or cmake? They can simplify detection a lot, especially since you are targeting multiple platforms. Or do you target portable make? If not so, GNU make contains a bunch of advanced constructs like branching, evaluation, substitution and etc. which allows easier writing of more complex build code and can be done without autoconf or cmake.
#2
newLISP newS / Re: Crashing stable and development version on 64bit platfor
January 26, 2014, 02:16:58 AM
Thanks guys for pointers; and thanks Lutz for quick fix.



Btw. I noticed another issue: in makefiles marked as makefile_linux_*_ffi is missing -lffi for Slackware and other distros than Ubuntu.
#3
newLISP newS / Crashing stable and development version on 64bit platform
January 25, 2014, 06:31:37 AM
Hi,



Sorry for posting on forum, but is there a bug tracker for reporting bugs or what are practices for reporting issues? I found odd crashes in both stable (10.5.4) and development versions (10.5.6) when they gets compiled with makefile_linuxLP64_utf8_ffi. I'm running it on Slackware 14.1 64bit.



By running in REPL this:
Code Select

> (:button 32)

it will crash both mentioned interpreters. This is the stacktrace:
Code Select

Program received signal SIGSEGV, Segmentation fault.
0x00000000004096da in printCell (cell=0x20, printFlag=1, device=6700736) at newlisp.c:2514
2514    switch(cell->type)
(gdb) bt
#0  0x00000000004096da in printCell (cell=0x20, printFlag=1, device=6700736) at newlisp.c:2514
#1  0x000000000040b1c0 in printErrorMessage (errorNumber=15, expr=0x20, deleteFlag=0) at newlisp.c:3149
#2  0x000000000040aff4 in fatalError (errorNumber=15, expr=0x20, deleteFlag=0) at newlisp.c:3112
#3  0x000000000040aef6 in errorProcAll (errorNumber=15, expr=0x20, deleteFlag=0) at newlisp.c:3080
#4  0x000000000040af5f in errorProcExt (errorNumber=15, expr=0x20) at newlisp.c:3093
#5  0x00000000004147b2 in p_colon (params=0x7ffff7f33010) at newlisp.c:7185
#6  0x00000000004073a8 in evaluateExpression (cell=0x7ffff7f36350) at newlisp.c:1510
#7  0x0000000000406630 in evaluateStream (stream=0x7fffffffda80, outDevice=2, flag=0) at newlisp.c:1283
#8  0x0000000000406461 in executeCommandLine (command=0x6c12e0 "(:button 32)", outDevice=2, cmdStream=0x7fffffffdaf0) at newlisp.c:1230
#9  0x00000000004056d5 in main (argc=1, argv=0x7fffffffe028) at newlisp.c:901

:button wasn't declared anywhere, so it is nonexisting symbol. Any idea what could go wrong?
#4
So, what can you actually DO with newLISP? / Re: Mine two stories
January 18, 2014, 08:51:56 AM
Thanks for reply :)
QuoteIn newLISP's tokenizer the "[" character starts a symbol name and doesn't finish it until a closing "]" is found

Oh didn't know for this; a really nice feature for unique names for sure. I'm interested about design reasons behind this: to maybe support [text] tokens or something else?
#5
So, what can you actually DO with newLISP? / Mine two stories
January 17, 2014, 07:21:56 AM
Hi guys,



This is my first post here, so please be gentle :D



Regarding my usage of newLisp, I'm using it here and there for a couple of years with praises. I'll tell you about two 'war stories' where I found newLisp indispensable.



I) I'm maintaining a page for EDE project (http://edeproject.org">http://edeproject.org) and I can say it is happily powered with newLisp for more than a year.



Previous version was written in python some years ago as cgi script with templating engine, news parser and couple of other bits, but after some issues with the server, especially frequent python updates from administrators and python installation location changes, it was evident it is time to move on something else.



We are hosting pages on shared hosting, generously donated to the project for free so complaining would be quite unreasonable; for me, the only viable solution was to keep as much as possible things less dependent on system packages and/or installation.



newLisp happened a perfect tool here: a small binary without too many dependencies, fast and memory savvy and best of all, with batteries included. So I ended up with a full templating engine, rss feed fetcher and parser, caching facility and small amount of multithreading (thanks to 'spawn') in a single cgi script! Even python would be ashamed here.



II) Couple years ago, while working on faculty of science, I had to administer some old SPARCstations with, hm... if I can recall correctly 32MB of RAM and couple of MB of hard drive.



People who used those machines knows they are practically indestructible so they happened to be a perfect solution for DNS and DHCP hosting. However, the space was so tight I couldn't install anything larger than 30-40MB (you can forget about Perl CPAN or Python) and I needed something for scripting purposes.



Again newLisp, a single binary with batteries included saved the day; probably there are still a couple of scripts running there now, as I left the faculty 4 year ago...



So again, thanks for this wonderful implementation :)



PS: a question: is anyone used reader-event extensively and what is possible to achieve with it? I'm often using CL/Scheme where from time to time I change reader for readable DSLs... Is it possible to add, for example, [] to behave just like ()?



Thanks.
Pages1