#cdecl — Public Fediverse posts

Infinitely annoying that in char *foo[100] foo is 100 pointers to chars, but in char (*foo)[100] foo is a pointer to 100 chars. 🤬

#c #cdecl

Infinitely annoying that in char *foo[100] foo is 100 pointers to chars, but in char (*foo)[100] foo is a pointer to 100 chars. 🤬

#c #cdecl

Infinitely annoying that in char *foo[100] foo is 100 pointers to chars, but in char (*foo)[100] foo is a pointer to 100 chars. 🤬

#c #cdecl

Infinitely annoying that in char *foo[100] foo is 100 pointers to chars, but in char (*foo)[100] foo is a pointer to 100 chars. 🤬

#c #cdecl

Infinitely annoying that in char *foo[100] foo is 100 pointers to chars, but in char (*foo)[100] foo is a pointer to 100 chars. 🤬

#c #cdecl

REPOST (JAN 2024): My first thoughts on #Psion's dialect of Object Oriented C for the Series 3 and related portable computers.

Includes the JPI/Clarion #TopSpeed #compiler, a proprietary preprocessor, the Eiffel programming language, and a handful of calling conventions.

Also, did somebody say Objective-C?

This is an old blog post from the beginning of the year. If you've been following my journey in recreating #CTRAN, this was written a week before I decided to take the plunge.

https://hackaday.io/project/161291-the-last-psion/log/226441-beginning-olib-an-entirely-uneducated-look-at-psions-proprietary-object-oriented-c

(Yes, I did say in the article that I definitely wouldn't be writing a compiler. I did say that.)

#RetroComputing #EPOC16 #CDECL #Clarion #TopSpeed #TopSpeedC #RetroProgramming #RetroDev #Smalltalk #ObjectPascal #preprocessor #Eiffel #OOP #ObjectiveC #compilers #ObjectOriented

REPOST (JAN 2024): My first thoughts on #Psion's dialect of Object Oriented C for the Series 3 and related portable computers.

Includes the JPI/Clarion #TopSpeed #compiler, a proprietary preprocessor, the Eiffel programming language, and a handful of calling conventions.

Also, did somebody say Objective-C?

This is an old blog post from the beginning of the year. If you've been following my journey in recreating #CTRAN, this was written a week before I decided to take the plunge.

https://hackaday.io/project/161291-the-last-psion/log/226441-beginning-olib-an-entirely-uneducated-look-at-psions-proprietary-object-oriented-c

(Yes, I did say in the article that I definitely wouldn't be writing a compiler. I did say that.)

#RetroComputing #EPOC16 #CDECL #Clarion #TopSpeed #TopSpeedC #RetroProgramming #RetroDev #Smalltalk #ObjectPascal #preprocessor #Eiffel #OOP #ObjectiveC #compilers #ObjectOriented

REPOST (JAN 2024): My first thoughts on #Psion's dialect of Object Oriented C for the Series 3 and related portable computers.

Includes the JPI/Clarion #TopSpeed #compiler, a proprietary preprocessor, the Eiffel programming language, and a handful of calling conventions.

Also, did somebody say Objective-C?

This is an old blog post from the beginning of the year. If you've been following my journey in recreating #CTRAN, this was written a week before I decided to take the plunge.

https://hackaday.io/project/161291-the-last-psion/log/226441-beginning-olib-an-entirely-uneducated-look-at-psions-proprietary-object-oriented-c

(Yes, I did say in the article that I definitely wouldn't be writing a compiler. I did say that.)

#RetroComputing #EPOC16 #CDECL #Clarion #TopSpeed #TopSpeedC #RetroProgramming #RetroDev #Smalltalk #ObjectPascal #preprocessor #Eiffel #OOP #ObjectiveC #compilers #ObjectOriented

REPOST (JAN 2024): My first thoughts on #Psion's dialect of Object Oriented C for the Series 3 and related portable computers.

Includes the JPI/Clarion #TopSpeed #compiler, a proprietary preprocessor, the Eiffel programming language, and a handful of calling conventions.

Also, did somebody say Objective-C?

This is an old blog post from the beginning of the year. If you've been following my journey in recreating #CTRAN, this was written a week before I decided to take the plunge.

https://hackaday.io/project/161291-the-last-psion/log/226441-beginning-olib-an-entirely-uneducated-look-at-psions-proprietary-object-oriented-c

(Yes, I did say in the article that I definitely wouldn't be writing a compiler. I did say that.)

#RetroComputing #EPOC16 #CDECL #Clarion #TopSpeed #TopSpeedC #RetroProgramming #RetroDev #Smalltalk #ObjectPascal #preprocessor #Eiffel #OOP #ObjectiveC #compilers #ObjectOriented

REPOST (JAN 2024): My first thoughts on #Psion's dialect of Object Oriented C for the Series 3 and related portable computers.

Includes the JPI/Clarion #TopSpeed #compiler, a proprietary preprocessor, the Eiffel programming language, and a handful of calling conventions.

Also, did somebody say Objective-C?

This is an old blog post from the beginning of the year. If you've been following my journey in recreating #CTRAN, this was written a week before I decided to take the plunge.

https://hackaday.io/project/161291-the-last-psion/log/226441-beginning-olib-an-entirely-uneducated-look-at-psions-proprietary-object-oriented-c

(Yes, I did say in the article that I definitely wouldn't be writing a compiler. I did say that.)

#RetroComputing #EPOC16 #CDECL #Clarion #TopSpeed #TopSpeedC #RetroProgramming #RetroDev #Smalltalk #ObjectPascal #preprocessor #Eiffel #OOP #ObjectiveC #compilers #ObjectOriented

I still have trouble with this part of #C 😥 – which is why I like the solution in #Go (https://go.dev/blog/declaration-syntax):

“Reading C Type Declarations” [2003], Steve Friedl (http://www.unixwiz.net/techtips/reading-cdecl.html).

Via HN: https://news.ycombinator.com/item?id=40387812

#Programming #CProgramming #CDecl

I still have trouble with this part of #C 😥 – which is why I like the solution in #Go (https://go.dev/blog/declaration-syntax):

“Reading C Type Declarations” [2003], Steve Friedl (http://www.unixwiz.net/techtips/reading-cdecl.html).

Via HN: https://news.ycombinator.com/item?id=40387812

#Programming #CProgramming #CDecl

I still have trouble with this part of #C 😥 – which is why I like the solution in #Go (https://go.dev/blog/declaration-syntax):

“Reading C Type Declarations” [2003], Steve Friedl (http://www.unixwiz.net/techtips/reading-cdecl.html).

Via HN: https://news.ycombinator.com/item?id=40387812

#Programming #CProgramming #CDecl

I still have trouble with this part of #C 😥 – which is why I like the solution in #Go (https://go.dev/blog/declaration-syntax):

“Reading C Type Declarations” [2003], Steve Friedl (http://www.unixwiz.net/techtips/reading-cdecl.html).

Via HN: https://news.ycombinator.com/item?id=40387812

#Programming #CProgramming #CDecl

I still have trouble with this part of #C 😥 – which is why I like the solution in #Go (https://go.dev/blog/declaration-syntax):

“Reading C Type Declarations” [2003], Steve Friedl (http://www.unixwiz.net/techtips/reading-cdecl.html).

Via HN: https://news.ycombinator.com/item?id=40387812

#Programming #CProgramming #CDecl

ICYMI: My first thoughts on #Psion's dialect of Object Oriented C for the Series 3 and related portable computers.

Includes the JPI/Clarion TopSpeed compiler, a proprietary preprocessor, the Eiffel programming language, and a handful of calling conventions.

Also, did somebody say Objective-C?

https://hackaday.io/project/161291-the-last-psion/log/226441-beginning-olib-an-entirely-uneducated-look-at-psions-proprietary-object-oriented-c

#RetroComputing #EPOC16 #CDECL #Clarion #TopSpeed #TopSpeedC #RetroProgramming #RetroDev #Smalltalk #ObjectPascal #preprocessor #Eiffel #OOP #ObjectiveC

ICYMI: My first thoughts on #Psion's dialect of Object Oriented C for the Series 3 and related portable computers.

Includes the JPI/Clarion TopSpeed compiler, a proprietary preprocessor, the Eiffel programming language, and a handful of calling conventions.

Also, did somebody say Objective-C?

https://hackaday.io/project/161291-the-last-psion/log/226441-beginning-olib-an-entirely-uneducated-look-at-psions-proprietary-object-oriented-c

#RetroComputing #EPOC16 #CDECL #Clarion #TopSpeed #TopSpeedC #RetroProgramming #RetroDev #Smalltalk #ObjectPascal #preprocessor #Eiffel #OOP #ObjectiveC

ICYMI: My first thoughts on #Psion's dialect of Object Oriented C for the Series 3 and related portable computers.

Includes the JPI/Clarion TopSpeed compiler, a proprietary preprocessor, the Eiffel programming language, and a handful of calling conventions.

Also, did somebody say Objective-C?

https://hackaday.io/project/161291-the-last-psion/log/226441-beginning-olib-an-entirely-uneducated-look-at-psions-proprietary-object-oriented-c

#RetroComputing #EPOC16 #CDECL #Clarion #TopSpeed #TopSpeedC #RetroProgramming #RetroDev #Smalltalk #ObjectPascal #preprocessor #Eiffel #OOP #ObjectiveC

ICYMI: My first thoughts on #Psion's dialect of Object Oriented C for the Series 3 and related portable computers.

Includes the JPI/Clarion TopSpeed compiler, a proprietary preprocessor, the Eiffel programming language, and a handful of calling conventions.

Also, did somebody say Objective-C?

https://hackaday.io/project/161291-the-last-psion/log/226441-beginning-olib-an-entirely-uneducated-look-at-psions-proprietary-object-oriented-c

#RetroComputing #EPOC16 #CDECL #Clarion #TopSpeed #TopSpeedC #RetroProgramming #RetroDev #Smalltalk #ObjectPascal #preprocessor #Eiffel #OOP #ObjectiveC

ICYMI: My first thoughts on #Psion's dialect of Object Oriented C for the Series 3 and related portable computers.

Includes the JPI/Clarion TopSpeed compiler, a proprietary preprocessor, the Eiffel programming language, and a handful of calling conventions.

Also, did somebody say Objective-C?

https://hackaday.io/project/161291-the-last-psion/log/226441-beginning-olib-an-entirely-uneducated-look-at-psions-proprietary-object-oriented-c

#RetroComputing #EPOC16 #CDECL #Clarion #TopSpeed #TopSpeedC #RetroProgramming #RetroDev #Smalltalk #ObjectPascal #preprocessor #Eiffel #OOP #ObjectiveC

Looking through some #Psion C code, I've seen `CDECL` a few times. Being a noob, I didn't know what they were or why they were there.

So, looking at Wikipedia...

#CDECL is a "caller clean-up" calling convention using the stack. This is pretty common in the x86 world, but is explicitly mentioned in Psion code. Why?

#TopSpeed C uses its own "callee clean-up" calling convention, using registers for the first 4 int parameters, which #EPOC16 really likes.

https://en.wikipedia.org/wiki/X86_calling_conventions

#RetroComputing

Looking through some #Psion C code, I've seen `CDECL` a few times. Being a noob, I didn't know what they were or why they were there.

So, looking at Wikipedia...

#CDECL is a "caller clean-up" calling convention using the stack. This is pretty common in the x86 world, but is explicitly mentioned in Psion code. Why?

#TopSpeed C uses its own "callee clean-up" calling convention, using registers for the first 4 int parameters, which #EPOC16 really likes.

https://en.wikipedia.org/wiki/X86_calling_conventions

#RetroComputing

Looking through some #Psion C code, I've seen `CDECL` a few times. Being a noob, I didn't know what they were or why they were there.

So, looking at Wikipedia...

#CDECL is a "caller clean-up" calling convention using the stack. This is pretty common in the x86 world, but is explicitly mentioned in Psion code. Why?

#TopSpeed C uses its own "callee clean-up" calling convention, using registers for the first 4 int parameters, which #EPOC16 really likes.

https://en.wikipedia.org/wiki/X86_calling_conventions

#RetroComputing

Looking through some #Psion C code, I've seen `CDECL` a few times. Being a noob, I didn't know what they were or why they were there.

So, looking at Wikipedia...

#CDECL is a "caller clean-up" calling convention using the stack. This is pretty common in the x86 world, but is explicitly mentioned in Psion code. Why?

#TopSpeed C uses its own "callee clean-up" calling convention, using registers for the first 4 int parameters, which #EPOC16 really likes.

https://en.wikipedia.org/wiki/X86_calling_conventions

#RetroComputing

Looking through some #Psion C code, I've seen `CDECL` a few times. Being a noob, I didn't know what they were or why they were there.

So, looking at Wikipedia...

#CDECL is a "caller clean-up" calling convention using the stack. This is pretty common in the x86 world, but is explicitly mentioned in Psion code. Why?

#TopSpeed C uses its own "callee clean-up" calling convention, using registers for the first 4 int parameters, which #EPOC16 really likes.

https://en.wikipedia.org/wiki/X86_calling_conventions

#RetroComputing