pro April 2014

pro@common-lisp.net

26 participants
6 discussions

[pro] lisp on mobile platforms these days
by Attila Lendvai 01 May '14

01 May '14

dear lispers, what is the state of the art in running lisp (not just CL) on mobile platforms, preferably in a portable way? is mkcl viable to run as a native app both on iOS and android? if iOS has too many legal constraints and whatnot, then let's forget it for now. what are the downsides of connecting to the NDK (android C API)? how much of android is not available through the NDK? -- • attila lendvai • PGP: 963F 5D5F 45C7 DFCD 0A39 -- Paralysis through analysis.

8 12

[pro] Heartbleed?
by David McClain 29 Apr '14

29 Apr '14

Just curious for other opinions... but wouldn't this (Heartbleed) sort of buffer excess read-back failure have been prevented by utilizing a "safe" language like Lisp or SML? I used to be an "unsafe" language bigot -- having mastered C/C++ for many years, and actually producing C compilers for a living at one time. I felt there should be no barriers to me as master of my machine, and not the other way around. But today's software systems are so complex that it boggles the mind to keep track of everything needed. I found during my transition years that I could maintain code bases no larger than an absolute max of 500 KLOC, and that I actually started losing track of details around 100 KLOC. Making the transition to a higher level language like SML or Lisp enabled greater productivity within those limits for me. Dr. David McClain dbm(a)refined-audiometrics.com

12 42

[pro] write-char vs. 8-bit bytes
by Paul Tarvydas 14 Apr '14

14 Apr '14

I'm using sbcl to write-char a 16-bit unsigned integer to a socket as two separate unsigned 8-bit bytes, for example 141 should appear as #x00 #x8d. SBCL appears to convert the #x8d into a two-byte utf-8 char, resulting in 3 bytes written to the stream \#x00 #xcd #x8d. What is the proper incantation to achieve this? (SBCL on Windows, if that matters). thanks pt

12 21

Re: [pro] Heartbleed?
by Bob Cassels 12 Apr '14

12 Apr '14

That was always part of the Lisp dogma. It's probably even true. On Apr 12, 2014 5:52 PM, David McClain <dbm(a)refined-audiometrics.com> wrote: > > Just curious for other opinions... but wouldn't this (Heartbleed) sort of buffer excess read-back failure have been prevented by utilizing a "safe" language like Lisp or SML? > > I used to be an "unsafe" language bigot -- having mastered C/C++ for many years, and actually producing C compilers for a living at one time. I felt there should be no barriers to me as master of my machine, and not the other way around. > > But today's software systems are so complex that it boggles the mind to keep track of everything needed. I found during my transition years that I could maintain code bases no larger than an absolute max of 500 KLOC, and that I actually started losing track of details around 100 KLOC. Making the transition to a higher level language like SML or Lisp enabled greater productivity within those limits for me. > > Dr. David McClain > dbm(a)refined-audiometrics.com > > >

1 0

Formal Presentation and initial doubts.
by Alejandro Zamora Fonseca 11 Apr '14

11 Apr '14

Hello for everybody!!. My name is alejandro and I'm a new Common Lisp fan. I've been use it almost 1 year and I think is an awesome language. But I have some troubles with topics, like GUI for desktop apps, and Unicode characters. I use Clisp mainly, ECL, and Clozure CL too. Would you help me with some hints for these problems? Greetings, Alejandro -- Este mensaje le ha llegado mediante el servicio de correo electronico que ofrece Infomed para respaldar el cumplimiento de las misiones del Sistema Nacional de Salud. La persona que envia este correo asume el compromiso de usar el servicio a tales fines y cumplir con las regulaciones establecidas Infomed: http://www.sld.cu/

8 9

Re: [pro] write-char vs. 8-bit bytes
by Bob Cassels 11 Apr '14

11 Apr '14

Yes. From the original description, this is a binary operation, not a character operation. On Apr 10, 2014 10:45 PM, raito(a)raito.com wrote: > > I end up doing something like: > > (defmacro with-open-binary-file (args &rest rest) > `(with-open-file (,@args :element-type '(unsigned-byte 8)) ,@rest)) > > (defun write-word (word out) > (write-byte (ldb (byte 8 8) word) out) > (write-byte (ldb (byte 8 0) word) out)) > > only because I'm exclusively writing binary stuff to the files this code > serves, and because it parallels the C code that does the same thing > fairly well. I'm not writing to a socket stream, but this may help anyway. > It might need to account for endianness, but I'm not sure. It's been a > while since I've looked at it closely. > > Neil Gilmore > raito(a)raito.com > > > I can't easily verify right now, but check the :external-format on your > > stream: it may be defaulting to UTF-8 and you will need to specify > > something else. > > > > -tree > > > > Sent from my iPhone > > > >> On Apr 10, 2014, at 10:31, Paul Tarvydas <paultarvydas(a)gmail.com> wrote: > >> > >> I'm using sbcl to write-char a 16-bit unsigned integer to a socket as > >> two separate unsigned 8-bit bytes, for example 141 should appear as > >> > >> #x00 #x8d. > >> > >> SBCL appears to convert the #x8d into a two-byte utf-8 char, resulting > >> in 3 bytes written to the stream > >> > >> \#x00 #xcd #x8d. > >> > >> What is the proper incantation to achieve this? (SBCL on Windows, if > >> that matters). > >> > >> thanks > >> pt > >> > >> > >> _______________________________________________ > >> pro mailing list > >> pro(a)common-lisp.net > >> http://common-lisp.net/cgi-bin/mailman/listinfo/pro > > > > _______________________________________________ > > pro mailing list > > pro(a)common-lisp.net > > http://common-lisp.net/cgi-bin/mailman/listinfo/pro > > > > > > _______________________________________________ > pro mailing list > pro(a)common-lisp.net > http://common-lisp.net/cgi-bin/mailman/listinfo/pro

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

pro April 2014