[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Shrinking the C core
From: |
Alfred M. Szmidt |
Subject: |
Re: Shrinking the C core |
Date: |
Mon, 21 Aug 2023 02:19:07 -0400 |
> Please keep the CC intact, not everyone subscribed.
Yes, that is some Gnus configuration "ghost" I must have done,
several people have pointed it out, but I have been unable to
locate it - so far.
I suppose that is also why I get a bounce from you?
> Hi!
>
> This is the MAILER-DAEMON, please DO NOT REPLY to this email.
>
> An error has occurred while attempting to deliver a message for
> the following list of recipients:
>
> incal@dataswamp.org: "stdin: 0 messages processed in 0.001 seconds"
Adding it here, since it seems impossible to send messages to your
swamp.
>>> If we talk about type checking, Elisp uses dynamic typing
>>> and compilation cannot do much about it.
>>> Native compilation also does not touch C subroutines - the
>>> place where typechecks are performed.
>>
>> SBCL implements a Lisp, Lisp by definition is
>> dynamically typed.
>
> Only for the kind of use (code) that we are used to.
> See this:
>
>
https://medium.com/@MartinCracauer/static-type-checking-in-the-programmable-programming-language-lisp-79bb79eb068a
>
> This has literally nothing to do with the difference between
> static typing, and dynamic typing.
They are checked at compile time and with declare one can
influence execution based on that. It doesn't say subsequent
execution won't have to check types, for that one would need
complete inference like they have in SML.
That is not the meaning of dynamically or statically typed.
Statically typed languages you know every type at compile time, in a
dynamically typed language you have no clue about it either at compile
time or run time. The article in question claims that Lisp is
statically typed, which is a total misunderstanding of the term.
That would be really nice to have BTW, are you saying that
isn't possible with Lisp? Why not?
Because you literally always have to check the type, even with a
declare/declaim you are allowed to pass garbage. The compiler can
produce a warning, but it isn't an error in Lisp, while it is an error
in a statically typed language already at compile time. In Lisp you
never know the types of things.
- Re: Shrinking the C core, (continued)
- Re: Shrinking the C core, Eli Zaretskii, 2023/08/20
- Re: Shrinking the C core, Ihor Radchenko, 2023/08/20
- Re: Shrinking the C core, Alfred M. Szmidt, 2023/08/20
- Re: Shrinking the C core, Eli Zaretskii, 2023/08/20
- Re: Shrinking the C core, Ihor Radchenko, 2023/08/21
- Re: Shrinking the C core, Eli Zaretskii, 2023/08/21
- Re: Shrinking the C core, Ihor Radchenko, 2023/08/21
- Re: Shrinking the C core, Eli Zaretskii, 2023/08/21
- Re: Shrinking the C core, Ihor Radchenko, 2023/08/23
- Re: Shrinking the C core, Emanuel Berg, 2023/08/20
- Re: Shrinking the C core,
Alfred M. Szmidt <=
- Re: Shrinking the C core, Ihor Radchenko, 2023/08/21
- Re: Shrinking the C core, Alfred M. Szmidt, 2023/08/21
- Re: Shrinking the C core, Ihor Radchenko, 2023/08/21
- Re: Shrinking the C core, Alfred M. Szmidt, 2023/08/21
- Re: Shrinking the C core, Ihor Radchenko, 2023/08/21
- Re: Shrinking the C core, Emanuel Berg, 2023/08/22
- Re: Shrinking the C core, Alfred M. Szmidt, 2023/08/23
- Re: Shrinking the C core, Emanuel Berg, 2023/08/23
- Re: Shrinking the C core, Emanuel Berg, 2023/08/25
- Re: Shrinking the C core, Emanuel Berg, 2023/08/20