search for: level4

...line continuation in the non-string situation (just continute at the new line). However, that doesn't work for strings because the new line character, "\n", is included in the resultant string. For example, if I type the following in a script: datadir=" X:/level1/level2 /level3/level4/ level5/level6" after executing the script, string variable "datadir" becomes "X:/level1/level2\n/level3/level4/\nlevel5/level6" Someone has suggested to use "paste()" for putting pieces of strings together, but I would like to see if there is any other simpler...

...ursive, because you may need to pass said stack frame through another function. e.g.: function level1() /* exports i, imports nothing */ { var i = 0; function level2() /* exports i, imports i */ { function level3() /* exports i & j, imports i */ { var j = 0; function level4() /* exports nothing, imports i & j */ { return i + j; } level4(); } level3(); } level2(); } There are numerous ways to pass the stack frames into the inner functions. The naive approach is to simply have each stack frame contain a pointer to the enclos...

So I read the Kaleidoscope tutorial, big thanks to Chris Latter. Good pace, still excellent coverage. Just at the end it mentions closures and I was wondering how those are done in llvm. The link was to wikipedia, and i do know what closures/blocks/continuations are, (i think) but maybe someone could point me to where to read about how to do them in llvm. Thanks Torsten

Dear Listers, I am wondering how to convert multiple dummy variables to 1 factor variable. Thanks. wensui

...ing the timeout from 250ms. ===================================== #include <stdio.h> #include <signal.h> #include <sys/time.h> #include <string.h> #define LEVEL1 { int x = rand(); printf ("", x); } #define LEVEL2 LEVEL1 LEVEL1 #define LEVEL3 LEVEL2 LEVEL2 #define LEVEL4 LEVEL3 LEVEL3 #define LEVEL5 LEVEL4 LEVEL4 #define LEVEL6 LEVEL5 LEVEL5 #define LEVEL7 LEVEL6 LEVEL6 #define LEVEL8 LEVEL7 LEVEL7 #define LEVEL9 LEVEL8 LEVEL8 #define LEVEL10 LEVEL9 LEVEL9 #define LEVEL11 LEVEL10 LEVEL10 #define LEVEL12 LEVEL11 LEVEL11 #define LEVEL13 LEVEL12 LEVEL12 #define LEVEL1...

...8-533060101-51835291-1642 /usr/local/samba/bin/wbinfo -Y S-1-5-21-2269603188-533060101-51835291-1642 10004 /usr/local/samba/bin/wbinfo -R 10004 winbind_lookup_rids failed Could not lookup RIDs 10004 ************ Review of the access rights ************ ls -al /samba/data/level1/level2/level3/level4 drwxrwsr-x+ 19 myadmin grp2 512 Aug 15 11:18 . drwxr-x--- 9 myadmin grp1 512 Aug 12 16:06 .. drwxrws---+ 3 myadmin grp2 512 Jun 27 10:58 general -rwxr-----+ 1 jdoe grp2 0 Aug 15 11:18 New Text Document from Windows.txt -rwxrw---- 1 jdoe grp2 44 Aug 15 11:14...

Platform: OpenVMS Alpha 7.3 Compiler: Compaq C T6.5-002 on OpenVMS Alpha V7.3 Comile flags: /WARN=ENABLE=(LEVEL4, QUESTCODE) Best guess at UNIX equivalents of above compile flags: LEVEL4 = All warnings QUESTCODE = Do LINT processing on source. -John wb8tyw@qsl.network Personal Opinion Only batch.c (char *) is being used as a type, when a generic structure is being passed. (void *) appears to be what is...

...t who got A is below 31 for boy, 10 for girl. Then we increase the difficulty level of the exam to level 2, the number of the student who got A is below 32 for boy, 10 for girl. We did this 10 times, we got the following table score gender level1 level2 levle3 level4 level5 level6 level7 level 8 level9 level10 boy 31 32 33 34 35 36 37 38 39 40 girl 10 10 10 10 10 10 10 10 10 10 My question is how to use chi-square test to test if score is independent of gender. That is whet...

The following zlib files need patches in order to compile using Compaq C on OpenVMS. These should work on any ANSI compliant compiler. Operating System: OpenVMS ALPHA V7.3 Compiler: Compaq C T6.5 Compiler switches: /WARN=ENABLE=(LEVEL4, QUESTCODE) fnmatch.c and mdfour.c. Compaq C on OpenVMS can not deal with relative path names in #include files. Also the local prototype for getenv() does not match the one in stdlib.h. -John wb8tyw@qsl.network Personal Opinion Only PROJECT_ROOT:[rsync_vms.LIB]FNMATCH.GDIFF;1 --- ref_lib...

Operating System: OpenVMS ALPHA V7.3 Compiler: Compaq C T6.5 Compiler switches: /WARN=ENABLE=(LEVEL4, QUESTCODE) syscall.c is missing the "const" qualifiers for several of it's functions. This patch should supercede the previous patch I submitted. This was discovered while working on resovling the conflicts between signed and unsigned values. -John wb8tyw@qsl.network Personal O...

...lib files need patches in order to compile using Compaq C on OpenVMS. These patches should also be needed on a Tru64 or LINUX on ALPHA using Compaq C. These should work on any ANSI compliant compiler. Operating System: OpenVMS ALPHA V7.3 Compiler: Compaq C T6.5 Compiler switches: /WARN=ENABLE=(LEVEL4, QUESTCODE) The module adler32.c is testing the unsigned value len to see if it is greater than 0. Since this value can never be less than zero, a more specific test is to check if the value is non-zero. trees.c and zutil.c have function definitions with empty parameters instead of having a...

...to compile using Compaq C on OpenVMS. These patches should also be needed on a Tru64 or LINUX on ALPHA using Compaq C. Except for the alloca issue, these should work on any ANSI compliant compiler. Operating System: OpenVMS ALPHA V7.3 Compiler: Compaq C T6.5 Compiler switches: /WARN=ENABLE=(LEVEL4, QUESTCODE) SYSTEM.H is doing tests on undefined macros, and if the target is not _GNUC__ or _AIX is assuming that a specific prototype exists. This patch prototypes the alloca() function to be more consistent, but since any platform that supports the alloca() function should be able to provi...

...op:36.0pt; mso-level-number-position:left; text-indent:-18.0pt; font-family:Symbol;} @list l0:level2 {mso-level-tab-stop:72.0pt; mso-level-number-position:left; text-indent:-18.0pt;} @list l0:level3 {mso-level-tab-stop:108.0pt; mso-level-number-position:left; text-indent:-18.0pt;} @list l0:level4 {mso-level-tab-stop:144.0pt; mso-level-number-position:left; text-indent:-18.0pt;} @list l0:level5 {mso-level-tab-stop:180.0pt; mso-level-number-position:left; text-indent:-18.0pt;} @list l0:level6 {mso-level-tab-stop:216.0pt; mso-level-number-position:left; text-indent:-18.0pt;} @list l0:...

Hi, here is the first public post of the patch-set to enable Linux to run under SEV-ES enabled hypervisors. The code is mostly feature-complete, but there are still a couple of bugs to fix. Nevertheless, given the size of the patch-set, I think it is about time to ask for initial feedback of the changes that come with it. To better understand the code here is a quick explanation of SEV-ES first.

Hi, here is the first public post of the patch-set to enable Linux to run under SEV-ES enabled hypervisors. The code is mostly feature-complete, but there are still a couple of bugs to fix. Nevertheless, given the size of the patch-set, I think it is about time to ask for initial feedback of the changes that come with it. To better understand the code here is a quick explanation of SEV-ES first.

Hi, here is the next version of changes to enable Linux to run as an SEV-ES guest. The code was rebased to v5.7-rc3 and got a fair number of changes since the last version. What is SEV-ES ============== SEV-ES is an acronym for 'Secure Encrypted Virtualization - Encrypted State' and means a hardware feature of AMD processors which hides the register state of VCPUs to the hypervisor by

Hi, here is the next version of changes to enable Linux to run as an SEV-ES guest. The code was rebased to v5.7-rc3 and got a fair number of changes since the last version. What is SEV-ES ============== SEV-ES is an acronym for 'Secure Encrypted Virtualization - Encrypted State' and means a hardware feature of AMD processors which hides the register state of VCPUs to the hypervisor by