similar to: [PATCH nbdkit 0/2] tests: Test that public headers are ANSI (ISO C90) compatible.

On 1/14/19 6:15 AM, Richard W.M. Jones wrote: > In commit 3775916120749e935d287f35cb29ff6c586656df (and before that in > discussions with Eric) we decided that we should try to allow plugins > to be compiled with C compilers other than GCC or Clang (or with very > old / peculiar / incompatible versions of those compilers). > > However until we test this we cannot guarantee that

In commit 3775916120749e935d287f35cb29ff6c586656df (and before that in discussions with Eric) we decided that we should try to allow plugins to be compiled with C compilers other than GCC or Clang (or with very old / peculiar / incompatible versions of those compilers). However until we test this we cannot guarantee that changes to the code will not break this in future, hence this test. Note

On 1/14/19 6:15 AM, Richard W.M. Jones wrote: > When an ANSI/C90 plugin compiled with ‘-pedantic’ uses > NBDKIT_HANDLE_NOT_NEEDED it gets the error: > > ISO C forbids conversion of function pointer to object pointer type While POSIX requires it to work. But such is life. > > This is because the existing macro worked by returning a function > pointer but in C90 function

When an ANSI/C90 plugin compiled with ‘-pedantic’ uses NBDKIT_HANDLE_NOT_NEEDED it gets the error: ISO C forbids conversion of function pointer to object pointer type This is because the existing macro worked by returning a function pointer but in C90 function pointers cannot be cast to data pointers since on some ancient architectures code and data pointers were incompatible. We only need a

On Fri, Jan 18, 2019 at 08:36:07AM -0600, Eric Blake wrote: > On 1/14/19 6:15 AM, Richard W.M. Jones wrote: > > When an ANSI/C90 plugin compiled with ‘-pedantic’ uses > > NBDKIT_HANDLE_NOT_NEEDED it gets the error: > > > > ISO C forbids conversion of function pointer to object pointer type > > While POSIX requires it to work. But such is life. > > >

This is what I've been playing with in response to my earlier question about what to do with 'nbdkit -s sh -' (https://www.redhat.com/archives/libguestfs/2020-April/msg00032.html) I'm still open to ideas on a better name, and/or whether adding <stdbool.h> to our public include files is a good idea (if not, returning int instead of bool is tolerable). Eric Blake (2):

On 1/18/19 8:47 AM, Richard W.M. Jones wrote: > On Fri, Jan 18, 2019 at 08:36:07AM -0600, Eric Blake wrote: >> On 1/14/19 6:15 AM, Richard W.M. Jones wrote: >>> When an ANSI/C90 plugin compiled with ‘-pedantic’ uses >>> NBDKIT_HANDLE_NOT_NEEDED it gets the error: >>> >>> ISO C forbids conversion of function pointer to object pointer type >>

Hi, Is there a way to drop the ANSI colour strings from log files? In particular, I've got JSON logging throwing logs over to ES, but they have the ANSI colour escape sequences. Ideally I don't want to lose coloured logs from the console though, and I can't "see" a way to do this. Ast 16 at the moment… Andrew -------------- next part -------------- An HTML attachment was

I have noticed anything using ANSI escape sequences to color text does not work if syslinux is in VESA mode. It only works if the \1#, \2#, or \3# are used. This means that libmenu which relies on csprint fails to render colors in VESA mode. I noticed the default color table has a complete table generated at runtime for all VGA color combinations, which csprint also does but from VGA attributes on

When R is run interactively in a terminal which supports colors, it is possible to use ANSI escape sequences in order to put colors in the prompt, such as options(prompt = "\033[0;31mThis is red\033[0m> ") Unfortunately, something goes wrong because for long command lines, the line continuation override the prompt instead of being written in the next line. The problem gets worse

Hi folks, does anybody know how to get a DOS executable to run that relies heavily on ansi.sys to simulate a text-based user interface? My wine version is "Wine release 20010305". Any help appreciated. Regards Lothar -- Lothar Birk -- Institute of Naval Architecture and Ocean Engineering E-mail L.Birk@ism.TU-Berlin.DE S-Mail TU Berlin Phone +49 (0)30 314 26010 (direct line) or

All, Having problems terminating to a Nuvox PRI, the tech at Nuvox is saying Asterisk is transmitting in CCITT (aka ITU?) when they're expecting (and will only accept) ANSI. The question is, is there a simple way to change this or am I stuck with rewriting code? I googled and checked the mailing list and found nothing, I could be barking up the wrong tree I guess. PRI is not my forte.

From: Randy Dunlap <randy.dunlap at oracle.com> Fix sparse warning for non-ANSI function declaration: arch/x86/xen/irq.c:129:30: warning: non-ANSI function declaration of function 'xen_init_irq_ops' Signed-off-by: Randy Dunlap <randy.dunlap at oracle.com> Cc: Jeremy Fitzhardinge <jeremy.fitzhardinge at citrix.com> --- arch/x86/xen/irq.c | 2 +- 1 file changed, 1

From: Randy Dunlap <randy.dunlap at oracle.com> Fix sparse warning for non-ANSI function declaration: arch/x86/xen/irq.c:129:30: warning: non-ANSI function declaration of function 'xen_init_irq_ops' Signed-off-by: Randy Dunlap <randy.dunlap at oracle.com> Cc: Jeremy Fitzhardinge <jeremy.fitzhardinge at citrix.com> --- arch/x86/xen/irq.c | 2 +- 1 file changed, 1

From: Randy Dunlap <randy.dunlap at oracle.com> Fix sparse warning for non-ANSI function declaration: arch/x86/xen/irq.c:129:30: warning: non-ANSI function declaration of function 'xen_init_irq_ops' Signed-off-by: Randy Dunlap <randy.dunlap at oracle.com> Cc: Jeremy Fitzhardinge <jeremy.fitzhardinge at citrix.com> --- arch/x86/xen/irq.c | 2 +- 1 file changed, 1

Hi, I'd like to use the compiler flags -ansi -pedantic -Wno-long-long in my project but some llvm headers cause errors with them. I tried to compile llvm with these flags but it proved to be quite difficult. The headers, however, seemed easier to fix. Almost all of the errors were commas at the ends of enum lists or extraneous semicolons after namespaces. I went ahead and hunted down

Anyone have a script or utility to convert an RTF file to ANSI? The main idea here is to preserve the color codes that are specified in the RTF file, so they can be displayed easily in a terminal window.

Hi All: It appears that the terminfo ansi-m file is no longer distributed with the CentOS 6.2 (along with many others). Can anyone advise how I can obtain this file? As a work around I have copied the file from a CentOS 4 box but that is probably not the "proper" way to do it. TIA Regards, Hugh -- Hugh E Cruickshank, Forward Software, www.forward-software.com

Hi, So far with the latest changes the projects I am trying to port works fine, except for a mismatch on what is considered the ansi behaviour of islower() in ctype.h: ----- i = 220 islower (i) = 0, ISLOWER (i) = 0 toupper (i) = 220, TOUPPER (i) = 220 i = 221 islower (i) = 0, ISLOWER (i) = 0 toupper (i) = 221, TOUPPER (i) = 221 i = 222 islower (i) = 0, ISLOWER (i) = 0 toupper (i) = 222, TOUPPER

Hi, Today I fiddled around a bit with my OpenSSH public key files, and I noticed that ssh-keygen prints most non-printable characters in the comment as-is when showing the fingerprint of a key. This can lead to confusing output on the terminal when the comment contains ANSI escape characters which are interpreted by the terminal. The attached public key file serves as an example, which, when