freenode/#lisp - IRC Chatlog
Search
11:29:10
ECLIPSE
I need help with lisp file ,,,, I have FAS4 and lisp files malware ,, but I can not decompile or analysis this kind of malware, , ,, any help
11:31:44
scymtym
the "lisp" file extension is usually used for Common Lisp source code. there should be no need to decompile such a file
11:36:16
ECLIPSE
scymtym , I am sorry ,,, I have binary data named the first byte of it is AutoCAD-86 shape , and also I have FAS4 file ,, the both of files is malware's
11:37:43
ECLIPSE
I was able to decompile a bit of FAS file ,,,, but the tool I used is not working good ,, I need something that can convert it to assembly so I can read it and analysis
11:41:15
ECLIPSE
beach , the resources is less for this kind of malware , and think that maybe someone here have an idea about how to analysis it ,,,,,, becouse the malware is writen in Lisp language ,,
11:41:49
beach
Autocad is not written in Common Lisp, and Common Lisp is what this channel is about.
12:31:06
clothespin_
autocad will never move away from autolisp so long is there is an autocad because of the huge volumes of autolisp code out there
12:32:13
beach
However, there was a time when the company announced that they were going to rewrite it in Common Lisp. That project was canceled, though.
12:33:31
p_l
this led to situation where there was (still is?) a separate company providing an IDE for AutoLISP, because the VBA approach didn't win much support from userbase, no matter how much it was pushed
12:34:54
p_l
AFAIK it was due to AutoLISP that my parents home had a book called "LISP Programming Language", which set me on a slow, long road to Lisp :)
12:36:48
p_l
clothespin_: IIRC it started not on DOS but some Unix platform, but quickly cornered the market by going for DOS
12:37:48
p_l
and due to availability on random PCs, similarly to Turbo Pascal, it took over Poland in a storm
12:40:37
jackdaniel
in scale from -3 to +3 in on-topicness it has +0.001 because words phrases and "lisp" and "common lisp" pop up every now and then ,-)
12:41:59
thijso
Funnily enough, I used AutoCAD and never encountered Lisp during that time. Only much later did I learn about Lisp and retroactively saw that AutoLisp existed...
12:44:47
p_l
on more Common Lisp (well, pre-common but works on CL) CAD software, ICAD apparently was still available to some extent
12:45:47
clothespin_
dassault systemes bought ICAD and that was pretty much the end of new development
12:49:35
p_l
yes, in my infinite(simally small) free time, I was thinking of adding one of the things missing from the free software version back, using a lispy (scheme-y?) geometry library
12:50:09
p_l
because the FOSS version of gendl misses few components, due to them being dependant on closed-source commercial packages
12:53:19
p_l
... I just found that a project in which I had put my fingers a tiny bit and always thought was underfunded, has enough budget that if someone talked right way they could finance a lisp bonanza...
13:06:47
minion
The URL https://gitlab.common-lisp.net/users/sign_in?secret=c86b369e will be valid until 13:15 UTC.
14:48:59
rumbler3196
anyone having issues with paredit mode lately? Its letting me delete closing parens which is frustrating
15:03:03
Xach
rumbler3196: I don't use anything. If a form becomes too long to use simple paren balancing in the REPL, i write it in a file (sometimes a temporary one) to manage it.
15:38:08
pjb
note that paredit disables itself when parentheses become unbalanced in a buffer, outside of its control. So: (write-line "1) then repl is not a lisp buffer!")
15:43:50
rumbler3196
paredit in the scratch buffer works fine. I issue m-x slime and then activate paredit and parens don't keep
15:46:36
rumbler3196
this is where I get mixed up sometimes. I installed slime from the package manager, then after I installed quicklisp I installed the quicklisp-slime-helper
16:25:44
minion
The URL https://gitlab.common-lisp.net/users/sign_in?secret=97a2b8a1 will be valid until 16:30 UTC.
16:30:58
jasom
A stackless coroutine is a coroutine that cannot context-switch in a nested function.
16:32:30
samlamamma
Finally a proper reason to use Common Lisp. http://quickdocs.org/trivial-left-pad/api
16:32:57
jasom
Josh_2: so the "stackless" part is that the TCB for the coroutine need not include a separate stack.
16:37:00
Bike
wouldn't the issue be that you can only resume the yielded coroutine at certain points, that is while the condition is being handled? you can't actually return to the caller and do something you were already doing.
19:49:27
jcowan
Can sbcl statically type-check keyword actual arguments when the type of the corresponding lambda argument is known?
20:23:34
pfdietz
If you declaim the type of the function using FTYPE, it will flag the type incompatibility at the call.