Liste des Groupes | Revenir à c arch |
On 9/4/2024 3:18 PM, MitchAlsup1 wrote:I suspect that My 66000 is the only current ISA that efficientlyOn Wed, 4 Sep 2024 20:15:24 +0000, Brett wrote:>
>David Brown <david.brown@hesbynett.no> wrote:>On 03/09/2024 21:28, Stefan Monnier wrote:>>My impression - based on hearsay for Rust as I have no experience - is>
that
the key point of Rust is memory "safety". I use scare-quotes here,
since it
is simply about correct use of dynamic memory and buffers.
>
It is entirely possible to have correct use of memory in C,
If you look at the evolution of programming languages, "higher-level"
doesn't mean "you can do more stuff". On the contrary, making
a language "higher-level" means deciding what it is we want to make
harder or even impossible.
>
Agreed.
>
I've heard it said that the power of a programming language comes not
from what you can do with the language, but from what you cannot do.
Wrong, the last version of Swift added all the garbage programming
concepts
that one should avoid.
>
You have to give people the tools to do anything.
It is impossible to create a computer programming language where
the programmer cannot shoot himself in the foot.
A language could alternatively try to go in a direction like HolyC:
Take C:
Remove most advanced features;
Add some weird syntax tweaks;
Make all the types explicit sized.
>
>
Some of it is almost half tempting, except that I would probably make
the type-names lower-case to match with my existing usage (and save
needing to hit SHIFT as often).
>
Say:
u0: void
u1: _Bool
u8: unsigned char
u16: unsigned short
...
i16/s16: signed short
i32/s32: signed int
i64/s64: signed long long
f32: float
f64: double
m32: opaque 32-bit type
m64: opaque 64-bit type
m128: opaque 128-bit type
>
....
>
Then, say:
u0 foo(args...)
{
...
}
>
Where, args is exposed as an array of u32 or u64 depending on the target
architecture.
>
....
Les messages affichés proviennent d'usenet.