search for: s_f

...ance. Hammadi. -------------- next part -------------- mat<- read.csv(file="mat.csv",head=FALSE,sep=";") y<-read.csv(file="y.csv",head=FALSE,sep=";") Y=y[,1] D_1=mat[,1] D_2=mat[,2] D_3=mat[,3] D_4=mat[,4] Y_1=mat[,5] Y_2=mat[,6] Y_3=mat[,7] Y_4=mat[,8] s_F=mat[,9] s_G=mat[,10] L.minor=data.frame(Y=Y,D_1=D_1,D_2=D_2,D_3=D_3,D_4=D_4,Y_1=Y_1,Y_2=Y_2,Y_3=Y_3,Y_4=Y_4,s_F=s_F,s_G=s_G) stdS=1/(sd(s_F)) stdG=1/(sd(s_G)) L.minor.m1<-nls(Y~a_1_1*D_1+a_2_1*D_2+a_3_1*D_3+a_4_1*D_4+a_1_2*(exp(-gamma_1_F*stdS*(s_F-c_1_F))+exp(gamma_2_F*stdS*(s_F-c_2_F)))/(1+exp...

Hi Tim, Sorry, I'm not sure I follow. Are you maybe thinking that if the identifiers were tagged to specify scope, people would still be trying to use acronyms or single letters? So that, what in future code might be F, would instead be _f and that would be worse than f_ or s_f? I was thinking instead F would be (for new or modified code) _function or _fnctn or _func (as an object of type Function). Again, sorry -- I don't see how prepended underscore is worse than an appended one. Could you supply some examples, please? -----Original Message----- From: Tim Northo...

I so agree. I have found scope based coding conventions very useful. My favorite was: * Static data member: s_<lowerCaseLetterThenCamelCase> * Non-static data members: _<lowerCaseLetterThenCamelCase> (This was allowed by the C++ standard I last read. It’s _<UpperCase> that is reserved) * Function argments:

Hello list. I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without modifications. How did I try it? Created a (non-root) build environment (not a mock ) Installed the kernel.scr.rpm and did a rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee prep-out.log The build failed at the end: Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL Checking