Article <86plqd2zhf.fsf@linuxsc.com>

Warning: mysqli::__construct(): (HY000/1203): User howardkn already has more than 'max_user_connections' active connections in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\includes\artfuncs.php on line 21
Failed to connect to MySQL: (1203) User howardkn already has more than 'max_user_connections' active connections
Warning: mysqli::query(): Couldn't fetch mysqli in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\index.php on line 66
Article <86plqd2zhf.fsf@linuxsc.com>

Deutsch English Français Italiano

<86plqd2zhf.fsf@linuxsc.com>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!news.nobody.at!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Tim Rentsch <tr.17687@z991.linuxsc.com>
Newsgroups: comp.lang.c
Subject: Re: No warning at implicit removal of const. Was: relearning C: why does an in-place change to a char* segfault?
Date: Mon, 12 Aug 2024 14:38:36 -0700
Organization: A noiseless patient Spider
Lines: 22
Message-ID: <86plqd2zhf.fsf@linuxsc.com>
References: <IoGcndcJ1Zm83zb7nZ2dnZfqnPWdnZ2d@brightview.co.uk> <20240801174026.00002cda@yahoo.com> <v8gi7i$29iu1$1@dont-email.me> <slrnvaorkl.34j6.candycanearter07@candydeb.host.invalid> <87zfpvfdk4.fsf@nosuchdomain.example.com> <v8ii17$2q5p1$1@dont-email.me> <87v80ig4vt.fsf@nosuchdomain.example.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Date: Mon, 12 Aug 2024 23:38:36 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="f42e4005105099d89c60a754521770ce";
	logging-data="3643568"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+rZVwWdHP10FgxzA6XFz17Fsdy4Af9ht4="
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock: sha1:oS838adTom89XqqNbg2LqNgMKGc=
	sha1:9M3hkfHr0MHYV0s9ikFXfhZT27k=
Bytes: 1999

Keith Thompson <Keith.S.Thompson+u@gmail.com> writes:

> Richard Harnden <richard.nospam@gmail.invalid> writes:
> [...]
>
>> Is there any reason not to always write ...
>>
>> static const char *s = "hello, world";
>>
>> ... ?
>>
>> You get all the warnings for free that way.
>
> The "static", if this is at block scope, specifies that the
> pointer object, not the array object, has static storage duration.
> If it's at file scope it specifies that the name "s" is not
> visible to other translation units.  Either way, use it if that's
> what you want, don't use it if it isn't.
>
> There's no good reason not to use "const". [...]

Other people have different opinions on that question.