Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 18 Apr 2024 03:59:55 GMT
From:      Larry Rosenman <ler@FreeBSD.org>
To:        ports-committers@FreeBSD.org, dev-commits-ports-all@FreeBSD.org, dev-commits-ports-main@FreeBSD.org
Subject:   git: 6925b78750b2 - main - devel/cdecl: update to 16.3
Message-ID:  <202404180359.43I3xtMr057635@gitrepo.freebsd.org>

next in thread | raw e-mail | index | archive | help
The branch main has been updated by ler:

URL: https://cgit.FreeBSD.org/ports/commit/?id=6925b78750b2813d131f3a7129391baf1a4d5b8e

commit 6925b78750b2813d131f3a7129391baf1a4d5b8e
Author:     Larry Rosenman <ler@FreeBSD.org>
AuthorDate: 2024-04-18 03:59:03 +0000
Commit:     Larry Rosenman <ler@FreeBSD.org>
CommitDate: 2024-04-18 03:59:51 +0000

    devel/cdecl: update to 16.3
    
    ChangeLog:
    Better destructor parameter error message
    Attempting either to explain or declare a destructor having a parameter list now prints "destructors may not have parameters" explicitly.
    
    Defining a type more than once
    If a type is defined again where the current language is older than the language in which it was previously defined, the type's set of languages is now updated to be the current language and newer. For example, previously:
    
    cdecl> set c23
    cdecl> typedef int Int
    cdecl> show
    typedef int Int;
    cdecl> set c17
    cdecl> typedef int Int        // Already exists so did nothing.
    cdecl> show                   // Would NOT show anything.
    cdecl>
    Now the second typedef would update Int to make it available in C17 and newer so the second show would show it.
    
    Multiple conflicting declarations
    Now exhaustively checking multiple declarations for conflicts in C. Previously, multiple declarations of a variable or function with conflicting types that was separated by a different variable or function wasn't caught:
    
    int x, x;                     // OK in C
    int x, *x;                    // error (different types)
    int x, y, *x;                 // error, but wasn't caught
    Now it is.
    
    Using macros elsewhere
    Previously, attempting to use a macro where names are generally allowed would result in an error like:
    
    cdecl> #define N 5
    cdecl> explain int a[N]
                         ^
    15: syntax error: "N": ']' expected
    because "N" was returned as a macro token by the lexer. Now, the lexer ignores the fact that a name might be a macro.
---
 devel/cdecl/Makefile | 3 +--
 devel/cdecl/distinfo | 6 +++---
 2 files changed, 4 insertions(+), 5 deletions(-)

diff --git a/devel/cdecl/Makefile b/devel/cdecl/Makefile
index 1164420b11d9..cd972cf6df59 100644
--- a/devel/cdecl/Makefile
+++ b/devel/cdecl/Makefile
@@ -1,7 +1,6 @@
 PORTNAME=	cdecl
-PORTVERSION=	16.2.1
+PORTVERSION=	16.3
 DISTVERSIONPREFIX=	${PORTNAME}-
-PORTREVISION=	1
 CATEGORIES=	devel
 
 MAINTAINER=	ler@FreeBSD.org
diff --git a/devel/cdecl/distinfo b/devel/cdecl/distinfo
index 7975b6bd7e90..69f126200c8a 100644
--- a/devel/cdecl/distinfo
+++ b/devel/cdecl/distinfo
@@ -1,3 +1,3 @@
-TIMESTAMP = 1708489233
-SHA256 (paul-j-lucas-cdecl-cdecl-16.2.1_GH0.tar.gz) = 09b0ad9cf39f651dd07732c7baf46ef88c1c93e5dc2b0cd665c6887ccb852100
-SIZE (paul-j-lucas-cdecl-cdecl-16.2.1_GH0.tar.gz) = 963144
+TIMESTAMP = 1713412710
+SHA256 (paul-j-lucas-cdecl-cdecl-16.3_GH0.tar.gz) = ced9d93ad4bee071a8481867017c8db2b6621081178c27037e77fc9c16f102e9
+SIZE (paul-j-lucas-cdecl-cdecl-16.3_GH0.tar.gz) = 964259



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202404180359.43I3xtMr057635>