search for: opengroup

...by R should be changed to be POSIX-compliants, or the manual edited to be more precise regarding . Many thanks. Rodrigo [1] https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Configure-and-cleanup [2] https://cran.r-project.org/doc/manuals/r-release/R-exts.html#FOOT25 [3] http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html [4] http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_04

...precise regarding . >> >> Many thanks. >> >> Rodrigo >> >> [1] >> https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Configure-and-cleanup >> [2] https://cran.r-project.org/doc/manuals/r-release/R-exts.html#FOOT25 >> [3] http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html >> [4] >> http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_04 >> >> ______________________________________________ >> R-devel at r-project.org mailing list >> https://stat.ethz....

...:38, "Tim R?hsen" <tim.ruehsen at gmx.de> wrote: [...] > With this change, the regression test fails (ssh dumps core). > 'addrs' stays NULL but is freed unconditionally a few lines further down. What platform is this on? POSIX says free(NULL) is a no-op. http://pubs.opengroup.org/onlinepubs/000095399/functions/free.html

<signal.h> in POSIX reserves the "sa_" prefix: https://pubs.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html#tag_15_02_02 Let's use "saddr_" instead. Signed-off-by: Laszlo Ersek <lersek at redhat.com> --- ocaml/helpers.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/ocaml/helpers.c b/ocaml/helpers.c ind...

Apologies if this is off topic. I'd like to decode the Kerberos PAC which is NDR decoded and I know Samba has all the code to decode a PAC. I looked at http://msdn.microsoft.com/en-us/library/cc237933.aspx as an example and read the opengroup document, but I am still lost. Is there a good book, link, course about NDR endocding/decoding ? Thank you Markus

...this depends on the assumption that the > function that created context A did not return to its caller before > the llvm.swapcontext that created context B was executed.  And while > I'm at it, what it the function that created context A made a tail > call in the meantime? Yep. The opengroup manpages are pretty bad about describing the limits of setcontext(): http://www.opengroup.org/onlinepubs/007908775/xsh/getcontext.html. Could you sketch out the restrictions in your document? They may be identical to setjmp/longjmp, which opengroup does document: http://www.opengroup.org/onlinepubs...

...seem to remember that POSIX says in various places that pointers > to functions and pointers to void have identical representation, and > also that pointers to void and pointers to structures have identical > representation. One of those locations is the dlsym() spec > <https://pubs.opengroup.org/onlinepubs/9699919799/functions/dlsym.html>. > The other locations elude me, unfortunately. I think at least one of > those "other" locations may be in one of the Conformance sections; Eric > will know better. > > Regardless, casting "free" to a pointer-to...

...or by ISO C. Now, I seem to remember that POSIX says in various places that pointers to functions and pointers to void have identical representation, and also that pointers to void and pointers to structures have identical representation. One of those locations is the dlsym() spec <https://pubs.opengroup.org/onlinepubs/9699919799/functions/dlsym.html>. The other locations elude me, unfortunately. I think at least one of those "other" locations may be in one of the Conformance sections; Eric will know better. Regardless, casting "free" to a pointer-to-object, just because str...

...s optional in the places there are used (like here in MCContext). Regarding the thread safety, this is what the open group says about getenv(): "The getenv() function need not be reentrant. A function that is not required to be reentrant is not required to be thread-safe." http://pubs.opengroup.org/onlinepubs/009696799/functions/getenv.html -- Regards, Dirkjan Bussink

Hi, LDTP (Linux Desktop Testing Project) hosted in http://gnomebangalore.org/ldtp About LDTP: *Problem:* In windows domain there are many GUI automation tools, which can recognize the GUI as "objects" and not just with co-ordinates. Unfortunately, Open Source Linux GUI automation tools are not matured up to that level - at least to my knowledge ;) . Without this advancement in the

I've used that patch to close the hole. This patch is temporary and doesn't fix real trouble maker - problem in new version in getenv() (after 6.3 it got changed to something monstrous and non-working right if environment has only one variable), hope it will get fixed soon. *** rtld.c.orig Tue Dec 1 16:55:13 2009 --- rtld.c Tue Dec 1 16:55:55 2009 *************** *** 357,374 ****

...e not allowed in a username is a standards >> problem. > > > That's not how the RFC rules are defined. But, rather than argue that > point at length, I'd point out that Open Group standards for usernames > are simple and will comply with the SMTP RFCs: > http://pubs.opengroup.org/onlinepubs/000095399/basedefs/xbd_chap03.html#tag_03_426 > > That is, [A-Za-z0-9._][A-Za-z0-9._-] > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos > I think there is a mis-unde...

> It is declared in <sys/termios.h> ... which is included by <termios.h>, which might be a bit more standard? At least, only <termios.h> is listed here: http://www.opengroup.org/onlinepubs/007908775/headix.html Cheers, Jay.

...iants, or the manual edited to be more precise regarding . > > Many thanks. > > Rodrigo > > [1] > https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Configure-and-cleanup > [2] https://cran.r-project.org/doc/manuals/r-release/R-exts.html#FOOT25 > [3] http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html > [4] > http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_04 > > ______________________________________________ > R-devel at r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-dev...

Hello I'm trying to use C random generator function drand48() which return floating-point values, uniformly distributed over [0,1], (http://www.opengroup.org/onlinepubs/007908799/xsh/drand48.html). When values are returned to R, they are not in [0,1]. A simple C program using drand48() gives values in [0,1] so I suppose there is a problem (type definition ?) between C and R. Here are R and C function and an example. # R function simulC <- fun...

...et_item' from incompatible pointer type auth-pam.c: At top level: auth-pam.c:842: warning: initialization from incompatible pointer type auth-pam.c:908: warning: initialization from incompatible pointer type auth-pam.c:1034: warning: initialization from incompatible pointer type [1] http://www.opengroup.org/tech/rfc/mirror-rfc/rfc86.0.txt [2] http://www.opengroup.org/onlinepubs/008329799/ ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

...no idea why and when readdir should return an entry with a 0 inode number. Is that historically? - Second, POSIX does not demand the existence of the d_ino member in dirent. Only systems which claim to be X/Open compatible are required to have the d_ino member in dirent. See http://www.opengroup.org/onlinepubs/009695399/basedefs/dirent.h.html and http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap02.html#tag_02_01_04 Since it's fairly tricky and time consuming to generate the correct inode number when running the Windows equivalent of readdir, the d_ino entry...

Hi All,

...s date, access time, file name". --http://us2.samba.org/samba/docs/man/Samba-HOWTO-Collection/AccessControls.html#id2562588 The UNIX standard says: "The <date and time> field shall contain the appropriate date and timestamp of when the file was last modified." --http://www.opengroup.org/onlinepubs/000095399/utilities/ls.html

...v w x y z 0 1 2 3 4 5 6 7 8 9 . _ -" "The <hyphen> character should not be used as the first character of a portable user name." This allows a bit more things that NAME_REGEX though, but this still looks fine to me. For more info, see: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_431 http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_278 -- You are receiving this mail because: You are watching all bug changes. -------------- next part -------------- An HTML attachment was scrubbed......