Jean Louis wrote:
> (defun elbf-char (n)
> (concat "(+ " (string-replace "*" "(*)" (make-string n ?*)) ")"))
>
> (defun elbf-string (string)
> (let ((list (string-to-list string)))
> (with-temp-buffer
> (insert "(string ")
> (while list
> (insert (elbf-char (pop list
* Akib Azmain Turja [2023-01-22 17:37]:
> I just made a language named "Emacs Lisp Fuck", and here's the
> "Hello, World!" program:
It needs a package.
(defun elbf-char (n)
(concat "(+ " (string-replace "*" "(*)" (make-string n ?*)) ")"))
(defun elbf-string (string)
(let ((list (string-to-l
* Akib Azmain Turja [2023-01-22 17:37]:
> I just made a language named "Emacs Lisp Fuck", and here's the
> "Hello, World!" program:
I knew it, as I already got it (ouch) on the mailing list.
> #+begin_src emacs-lisp
> (string
> (+(*)(+)(*)(*)(*)(*)(+)(+)(+)(+)(*)(*)(*)(+)(+)(*)(*)(*)(*)(+)(*)(*
> > (*) → "sex"
> The No. 1 thing to some people ...
We pretty much _all_ depend on it.
Until we start cloning people or we
develop human parthenogeny.
(There's in vitro fertilization, but
you still need two sexes there.)
Oh, sorry, didn't mean to leave out
the miracle of virgin birth.
Miracle
Akib Azmain Turja wrote:
>>> In my book, it is useful to have mathematically sound
>>> behavior by default. If you have a reason to handle some
>>> edge-cases differently in some application (which is
>>> totally possible!), then define your own function which
>>> does what you wish.
>>
>> Your bo
Emanuel Berg writes:
> Tassilo Horn wrote:
>
>> In my book, it is useful to have mathematically sound
>> behavior by default. If you have a reason to handle some
>> edge-cases differently in some application (which is totally
>> possible!), then define your own function which does what
>> you wis
Jean Louis wrote:
>>> In my book, it is useful to have mathematically sound
>>> behavior by default. If you have a reason to handle some
>>> edge-cases differently in some application (which is
>>> totally possible!), then define your own function which
>>> does what you wish.
>>
>> Your book? Ac
* Emanuel Berg [2023-01-22 08:55]:
> Tassilo Horn wrote:
>
> > In my book, it is useful to have mathematically sound
> > behavior by default. If you have a reason to handle some
> > edge-cases differently in some application (which is totally
> > possible!), then define your own function which do
Tassilo Horn wrote:
> In my book, it is useful to have mathematically sound
> behavior by default. If you have a reason to handle some
> edge-cases differently in some application (which is totally
> possible!), then define your own function which does what
> you wish.
Your book? Actually I think
Jean Louis writes:
>> >> Yes, and I think it's seriously wrong with
>> >>
>> >> : (+)
>> >> -> NIL
>> >>
>> >> where its docs say
>> >>
>> >> Returns the sum of all num arguments. When one of the arguments
>> >> evaluates to NIL, it is returned immediately.
>> >
>> > For some reason Pi
* Tassilo Horn [2023-01-20 16:14]:
> Jean Louis writes:
>
> >> Yes, and I think it's seriously wrong with
> >>
> >> : (+)
> >> -> NIL
> >>
> >> where its docs say
> >>
> >> Returns the sum of all num arguments. When one of the arguments
> >> evaluates to NIL, it is returned immediatel
* Drew Adams [2023-01-19 20:47]:
> > I'm out. Enough information has been
> > presented to you to enable you to learn.
> > But I cannot learn for you, you must do
> > it yourself.
> > Michael.
>
> Bingo. Ditto. Shoulda just considered it
> as trolling perhaps. In any case, shoulda
> stopped
Jean Louis writes:
>> Yes, and I think it's seriously wrong with
>>
>> : (+)
>> -> NIL
>>
>> where its docs say
>>
>> Returns the sum of all num arguments. When one of the arguments
>> evaluates to NIL, it is returned immediately.
>
> For some reason PicoLisp is quite different than ot
* Tassilo Horn [2023-01-20 12:12]:
> Jean Louis writes:
>
> >> Gosh, Jean, of course nobody would literally write (*) but (apply #'*
> >> ...), and you'll find occurrences in emacs:
> >
> > That has been said that is not necessarily problem or reason.
>
> I don't understand that sentence.
>
>
* Tassilo Horn [2023-01-19 18:35]:
> Jean Louis writes:
>
> > You found examples I am searching, though you can't provide references
> > where (*) is useful.
>
> Gosh, Jean, of course nobody would literally write (*) but (apply #'*
> ...), and you'll find occurrences in emacs:
That has been sa
Jean Louis writes:
>> Gosh, Jean, of course nobody would literally write (*) but (apply #'*
>> ...), and you'll find occurrences in emacs:
>
> That has been said that is not necessarily problem or reason.
I don't understand that sentence.
> Did you see reference to PicoLisp?
Yes, and I think
* Óscar Fuentes [2023-01-18 17:09]:
> Sure^2. I was talking about _why_ (*) and (* a) are supported in Elisp.
> Once the language designer chose to support those expressions and
> decided that they must return a number (instead of something else like a
> partially applied function) the value they
* Michael Heerdegen [2023-01-19 16:56]:
> I'm out. Enough information has been presented to you to enable you to
> learn. But I cannot learn for you, you must do it yourself.
I did not ask for outside information, only if it is useful in Lisp,
apart from funny jokes and sketching of program.
-
18 matches
Mail list logo
