From: haj@posteo.de (Harald Jörg)
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [OFFTOPIC] Re: Handling extensions of programming languages (Perl)
Date: Mon, 22 Mar 2021 23:05:22 +0100 [thread overview]
Message-ID: <87lfaergil.fsf@hajtower> (raw)
In-Reply-To: <jwvr1k7ote9.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 22 Mar 2021 15:58:55 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>>> That was my first thought as well. But then, the declarators appear in
>>>> places where other languages have their types.
>>>
>>> [ I think you use a very restricted definition of "other languages" here.
>>> It's definitely not the case for most of the statically typed languages
>>> I've used, except for C.
>>> I'm thinking of OCaml, SML, Haskell, Agda, Coq, Modula-2, Pascal, Ada, ... ]
>>
>> Guilty, your honor. In the last years I've dealt with Emacs Lisp (only
>> very recently), Perl, C, Java, JavaScript ... and before that with a
>> dialect of PL/1, assembly languages (68000, x86, /390) ... and before
>> that with FORTRAN, where everyone's type system seemed to be IMPLICIT
>> INTEGER I-N. So indeed, almost no intersection with your list.
>
> Of those the only ones that are statically typed seem to be C, Java,
> Fortran and PL/1; and AFAICT only 50% (C and Java) use a syntax where
> the type is placed at a location comparable to where `my` is placed in
> Perl, IMO.
Fortran, too, unless you do the IMPLICIT trick.
But anyway: Looking at the Emacs modes for Java and C, all keywords like
"private" and "static" (which, similar to "my" in Perl, define scope
rather than type) are in keyword-face. This would indicate that
keyword-face is to be preferred for the declarators, and type-face for
the types.
--
Cheers,
haj
next prev parent reply other threads:[~2021-03-22 22:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 18:53 Handling extensions of programming languages Harald Jörg
2021-03-20 17:02 ` Matt Armstrong
2021-03-20 23:40 ` Harald Jörg
2021-03-21 2:18 ` Clément Pit-Claudel
2021-03-21 11:41 ` Harald Jörg
2021-03-21 12:39 ` Stefan Monnier
2021-03-21 15:48 ` Harald Jörg
2021-03-21 17:59 ` Stefan Monnier
2021-03-22 14:08 ` Handling extensions of programming languages (Perl) Harald Jörg
2021-03-22 14:48 ` Stefan Monnier
2021-03-22 17:32 ` Harald Jörg
2021-03-22 18:27 ` Stefan Monnier
2021-03-22 19:31 ` Harald Jörg
2021-03-22 19:58 ` [OFFTOPIC] " Stefan Monnier
2021-03-22 22:05 ` Harald Jörg [this message]
2021-03-22 22:24 ` Stefan Monnier
2021-03-22 23:43 ` Harald Jörg
2021-03-23 3:49 ` [OFFTOPIC] " Stefan Monnier
2021-03-30 18:41 ` Handling extensions of programming languages Stephen Leake
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lfaergil.fsf@hajtower \
--to=haj@posteo.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).