On Sat, Jan 23, 2016 at 02:10:46AM -0500, Peter Olson wrote:
[cut]
>
> I'm unhappy for two reasons:
>
> the failure mode of alloca is SIGSEGV or some other malfunction and there is
> no way to test for it
>
> the *buf &= ~0x20; breaks for UTF8 strings.
>
> Nevermind that the function impl
Le 22/01/2016 22:34, Rainer Weikusat a écrit :
Can the effect of the following C function
static void print_start(char const *name, char const *what)
{
char *buf, *p;
unsigned name_len, what_len, total;
name_len = strlen(name);
what_len = strlen(what);
total = name_len
The Free Software Foundation (FSF) is doing a survey until the end of
January:
https://my.fsf.org/civicrm/profile/create?gid=403&reset=1&pk_campaign=survey-launch&pk_kwd=survey
The FSF's blog post about it:
http://www.fsf.org/news/whats-your-vision-for-the-fsf-fill-out-our-survey-1
A couple quo
Le 23/01/2016 12:16, Didier Kryn a écrit :
I'm curious of the reason why you specify
static void print_start(char const *name, char const *what)
This means the pointers to the arrays of characters are constant
(not the characters). The effect of this cannot be to protect the
pointe
On Fri, 22 Jan 2016 21:34:28 +
Rainer Weikusat wrote:
> Can the effect of the following C function
>
> static void print_start(char const *name, char const *what)
> {
> char *buf, *p;
> unsigned name_len, what_len, total;
>
> name_len = strlen(name);
> what_len = strlen(what
Hi all,
Rainer's question brings up the concept of self-documenting code.
Here's an essay I wrote on the subject almost 2 decades ago:
http://troubleshooters.com/tpromag/199908/index.htm
SteveT
Steve Litt
January 2016 featured book: Twenty Eight Tales of Troubleshooting
http://www.troubleshoot
On Sat, Jan 23, 2016 at 04:45:05PM +0100, Didier Kryn wrote:
> Le 23/01/2016 12:16, Didier Kryn a écrit :
> >
> >I'm curious of the reason why you specify
> > static void print_start(char const *name, char const *what)
> >
> >This means the pointers to the arrays of characters are
> >cons
On Sat, Jan 23, 2016 at 11:45:30AM -0500, Steve Litt wrote:
> On Fri, 22 Jan 2016 21:34:28 +
> Rainer Weikusat wrote:
>
> > Can the effect of the following C function
> >
> > static void print_start(char const *name, char const *what)
> > {
> > char *buf, *p;
> > unsigned name_len, w
Le 23/01/2016 14:48, Hendrik Boom a écrit :
I've always said the C syntax for declarators was confusing.
Even those who understand it read it wrong!
(Yes, In understand the logic behind it. It is still confusing.)
I fully agree: it's confusing.
Actually, in a single statement one can
On Sat, Jan 23, 2016 at 06:59:10PM +0100, Didier Kryn wrote:
[cut]
>
> The syntax used by Rainer is usefull when declaring in the same
> statement constant and non-constant characters, which I, personnaly,
> try to avoid because it is confusing. Confusing statements simply
> boost the probab
Didier Kryn writes:
> Le 23/01/2016 12:16, Didier Kryn a écrit :
>>
>> I'm curious of the reason why you specify
>>static void print_start(char const *name, char const *what)
>>
>> This means the pointers to the arrays of characters are constant
>> (not the characters).
[...]
>
Peter Olson writes:
5>> On January 22, 2016 at 4:34 PM Rainer Weikusat
wrote:
[...]
>> p = buf = alloca(total);
[...]
> the failure mode of alloca is SIGSEGV or some other malfunction and
> there is no way to test for it
It's supposed to allocate memory in the current stack frame whic
On Sat, Jan 23, 2016 at 06:36:46PM +, Rainer Weikusat wrote:
> Peter Olson writes:
> 5>> On January 22, 2016 at 4:34 PM Rainer Weikusat
> wrote:
>
> [...]
>
> >> p = buf = alloca(total);
>
> [...]
>
> > the failure mode of alloca is SIGSEGV or some other malfunction and
> > there i
On Fri, 22 Jan 2016 00:09:23 -0500
Steve Litt wrote:
> different color terminals for
> ssh sessions
I had played a bit with the tiling and highly (GUI) configurable
"Terminator" but was bounced back to xterm very quickly due to its
footprint and wrote the following secremote.sh script. It has no
On Sat, Jan 23, 2016 at 08:10:31PM +0100, Florian Zieboll wrote:
> On Fri, 22 Jan 2016 00:09:23 -0500
> Steve Litt wrote:
>
> > different color terminals for
> > ssh sessions
>
> I had played a bit with the tiling and highly (GUI) configurable
> "Terminator" but was bounced back to xterm very qu
Katola2:
...
> void another_print_start(char *name, char *what){
>
> char c[3] = " :";
>
> c[2] = name[0] & ~0x20;
>
> write(2, c+2, 1);
> write(2, name+1, strlen(name) -1);
> write(2, c, 2);
> write(2, what, strlen(what));
>
> }
Why not just use writev(2) and write it one system call ?
On Sat, 23 Jan 2016 20:10:31 +0100
Florian Zieboll wrote:
> On Fri, 22 Jan 2016 00:09:23 -0500
> Steve Litt wrote:
>
> > different color terminals for
> > ssh sessions
>
> I had played a bit with the tiling and highly (GUI) configurable
> "Terminator" but was bounced back to xterm very quick
Le 23/01/2016 19:28, Rainer Weikusat a écrit :
Didier Kryn writes:
Le 23/01/2016 12:16, Didier Kryn a écrit :
I'm curious of the reason why you specify
static void print_start(char const *name, char const *what)
This means the pointers to the arrays of characters are constant
I really never thought I'd see an article on programming that managed to
pull both Grace Slick and Culture Club in as a relevant plot vehicles.
Well done, Steve.
:-D
- Nate
--
"The optimist proclaims that we live in the best of all
possible worlds. The pessimist fears this is true."
Ham rad
Hello Everybody,
I am not sure where I should post this question so I try it here first.
On my KVM VPS, I am trying to get the UnixBench score of kernel 4.1.5 to
the same level as the one of Devuan kernel 3.16.7-ckt11-1+deb8u3. The
issue is mainly on the performance of running parallel process
2016-01-23 21:44 GMT+01:00, Steve Litt :
> Suckless Tools terminals are very low footprint, but they also lack
> features necessary for certain tasks. IIRC you'd never use one for a
> login terminal, and IIRC they can't be told to run a certain script
> (like xterm -e). But they often suffice, and
On Fri, Jan 22, 2016 at 4:34 PM, Rainer Weikusat <
rainerweiku...@virginmedia.com> wrote:
> Can the effect of the following C function
>
> static void print_start(char const *name, char const *what)
> {
> char *buf, *p;
> unsigned name_len, what_len, total;
>
> name_len = strlen(name);
> On January 23, 2016 at 1:36 PM Rainer Weikusat
> wrote:
>
> Peter Olson writes:
> 5>> On January 22, 2016 at 4:34 PM Rainer Weikusat
> wrote:
>
> [...]
>
> >> p = buf = alloca(total);
>
> [...]
>
> > the failure mode of alloca is SIGSEGV or some other malfunction and
> > there is no
Hi
Does lightdm support a .face 95 x 95 px file /home as the image to display
on the login dialog?
Debian lightdm does.
Cheers
Ozi
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
24 matches
Mail list logo
