search for: foon

...n, but I have scant experience in R. It would be very convenient in doing lots of plots to be able to do them in a loop that stepped through a vector of variable names. For example one could say x<-("mydates") y<-c("foo1","foo2","foo3") #where "foon" were vectors plot(x,y[1],type="n") points(x,y[1]) points(x,y[2],pch=2) points(x,y[3],pch=3) This is pretty easy in Perl, but of course Perl is not for plotting. Of course one could construct a data structure in R that would hold what was wanted and maybe that is the way to go. Bu...

...a feature, and the dot is not the issue here. R uses partial argument matching on function arguments. So: > f <- function(foobar = 0){print(foobar)} > f function(foobar = 0){print(foobar)} > > f(fo=1) [1] 1 > f(foo=1) [1] 1 > f(foob=1) [1] 1 > f(fooba=1) [1] 1 > f(foon=1) Error in f(foon = 1) : unused argument(s) (foon ...) > > f(foobar2=1) Error in f(foobar2 = 1) : unused argument(s) (foobar2 ...) This is mentioned in Venables & Ripley, MASS 4th edition on p. 55. I can't find it right now in the "Introduction to R" that is linked to on t...

...eal with both file-locking and group ownership. I have read that I need essentially the following in my smb.conf file: [lab] path = /usr2/lab available = yes public = yes guest only = no writeable = yes browseable = yes valid users = foonly, hart only user = no oplocks = No level2oplocks = No create mask = 770 directory mask = 770 force group = lab with the important lines being "create mask", "directory mask" and "force group". The problem is that whil...

...> ) >> >> >> >> I have a couple overall questions/concerns: >> >> >> 1. The ref graph can easily go quadratic. E.g. >> >> typedef void (*fp)(); >> fp funcs[] = { >> &foo1, >> &foo2, >> ... >> &fooN >> } >> void foo1() { funcs[something](); } >> void foo2() { funcs[something](); } >> ... >> void fooN() { funcs[something](); } >> >> One real-world case where this might come about is in the presence of >> vtables. >> >> The existing CGS...

...ollowed by a committer email address, followed by ':' and a 1-origin sequence number if the date/time pair is not unique in the repository; it refers to a commit without being VCS-specific. Thus, instead of "commit 304a53c2" or "r2355", "2011-10-25T15:11:09Z!fred at foonly.com". - http://www.catb.org/~esr/reposurgeon/reposurgeon.html Also, once we transition to native Git repositories, you will be able to amend the most recent commit before you push. This should reduce the number of "typo in previous commit" messages. -- Charles Lepple clepple at...

...t; I have a couple overall questions/concerns: >>> >>> >>> 1. The ref graph can easily go quadratic. E.g. >>> >>> typedef void (*fp)(); >>> fp funcs[] = { >>> &foo1, >>> &foo2, >>> ... >>> &fooN >>> } >>> void foo1() { funcs[something](); } >>> void foo2() { funcs[something](); } >>> ... >>> void fooN() { funcs[something](); } >>> >>> One real-world case where this might come about is in the presence of >>> vtables. &g...

...no transformation we can statically make in the CGSCC passes can ever cause us to need to merge SCC's in the ref graph. ) I have a couple overall questions/concerns: 1. The ref graph can easily go quadratic. E.g. typedef void (*fp)(); fp funcs[] = { &foo1, &foo2, ... &fooN } void foo1() { funcs[something](); } void foo2() { funcs[something](); } ... void fooN() { funcs[something](); } One real-world case where this might come about is in the presence of vtables. The existing CGSCC pass manager does not have this issue AFAIK because it does not consider the ref grap...

...ke in the CGSCC passes can ever > cause us to need to merge SCC's in the ref graph. > ) > I have a couple overall questions/concerns: > 1. The ref graph can easily go quadratic. E.g. > typedef void (*fp)(); > fp funcs[] = { > &foo1, > &foo2, > ... > &fooN > } > void foo1() { funcs[something](); } > void foo2() { funcs[something](); } > ... > void fooN() { funcs[something](); } > One real-world case where this might come about is in the presence of > vtables. > The existing CGSCC pass manager does not have this issue AFAIK...

...t; I have a couple overall questions/concerns: >>> >>> >>> 1. The ref graph can easily go quadratic. E.g. >>> >>> typedef void (*fp)(); >>> fp funcs[] = { >>> &foo1, >>> &foo2, >>> ... >>> &fooN >>> } >>> void foo1() { funcs[something](); } >>> void foo2() { funcs[something](); } >>> ... >>> void fooN() { funcs[something](); } >>> >>> One real-world case where this might come about is in the presence of vtables. >>> &g...

...e us to need to merge SCC's in the ref graph. > ) > > > > I have a couple overall questions/concerns: > > > 1. The ref graph can easily go quadratic. E.g. > > typedef void (*fp)(); > fp funcs[] = { > &foo1, > &foo2, > ... > &fooN > } > void foo1() { funcs[something](); } > void foo2() { funcs[something](); } > ... > void fooN() { funcs[something](); } > > One real-world case where this might come about is in the presence of vtables. > > The existing CGSCC pass manager does not have this issue AF...

...> ) >> >> >> >> I have a couple overall questions/concerns: >> >> >> 1. The ref graph can easily go quadratic. E.g. >> >> typedef void (*fp)(); >> fp funcs[] = { >> &foo1, >> &foo2, >> ... >> &fooN >> } >> void foo1() { funcs[something](); } >> void foo2() { funcs[something](); } >> ... >> void fooN() { funcs[something](); } >> >> One real-world case where this might come about is in the presence of >> vtables. >> >> The existing CGS...

...cerns: >>>> >>>> >>>> 1. The ref graph can easily go quadratic. E.g. >>>> >>>> typedef void (*fp)(); >>>> fp funcs[] = { >>>> &foo1, >>>> &foo2, >>>> ... >>>> &fooN >>>> } >>>> void foo1() { funcs[something](); } >>>> void foo2() { funcs[something](); } >>>> ... >>>> void fooN() { funcs[something](); } >>>> >>>> One real-world case where this might come about is in the presence...

http://dragoman.org/tym Regards Tomas

http://bugzilla.mindrot.org/show_bug.cgi?id=769 Summary: dh-group-exchange should be configurable off in client and server Product: Portable OpenSSH Version: 3.7p1 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: ssh AssignedTo:

...> >>>> 1. The ref graph can easily go quadratic. E.g. > >>>> > >>>> typedef void (*fp)(); > >>>> fp funcs[] = { > >>>> &foo1, > >>>> &foo2, > >>>> ... > >>>> &fooN > >>>> } > >>>> void foo1() { funcs[something](); } > >>>> void foo2() { funcs[something](); } > >>>> ... > >>>> void fooN() { funcs[something](); } > >>>> > >>>> One real-world case where this...

...; 1. The ref graph can easily go quadratic. E.g. >>>>>> >>>>>> typedef void (*fp)(); >>>>>> fp funcs[] = { >>>>>> &foo1, >>>>>> &foo2, >>>>>> ... >>>>>> &fooN >>>>>> } >>>>>> void foo1() { funcs[something](); } >>>>>> void foo2() { funcs[something](); } >>>>>> ... >>>>>> void fooN() { funcs[something](); } >>>>>> >>>>>> One real-w...

...ership. > > I have read that I need essentially the following in my smb.conf file: > [lab] > path = /usr2/lab > available = yes > public = yes > guest only = no > writeable = yes > browseable = yes > valid users = foonly, hart > only user = no > oplocks = No > level2oplocks = No > create mask = 770 > directory mask = 770 > force group = lab > > with the important lines being "create mask", "directory mask" and "force...

...o Alterman <lalterman@nicira.com> Leo Song <liangs@marvell.com> Leo Yan <leoy@marvell.com> Leon Romanovsky <leon@leon.nu> Leonid Isaev <lisaev@umail.iu.edu> Leonid Shatz <leonid.shatz@ravellosystems.com> Leonid Yegoshin <yegoshin@mips.com> Ley Foon Tan <lftan@altera.com> Li Dongyang <Jerry87905@gmail.com> Li Fei <fei.li@intel.com> Li RongQing <roy.qing.li@gmail.com> Li Wang <wangli@kylinos.com.cn> Li Wei <lw@cn.fujitsu.com> Li Yang <leoli@freescale.com> Li Yu <raise.sail@gmail.com>...

...o Alterman <lalterman@nicira.com> Leo Song <liangs@marvell.com> Leo Yan <leoy@marvell.com> Leon Romanovsky <leon@leon.nu> Leonid Isaev <lisaev@umail.iu.edu> Leonid Shatz <leonid.shatz@ravellosystems.com> Leonid Yegoshin <yegoshin@mips.com> Ley Foon Tan <lftan@altera.com> Li Dongyang <Jerry87905@gmail.com> Li Fei <fei.li@intel.com> Li RongQing <roy.qing.li@gmail.com> Li Wang <wangli@kylinos.com.cn> Li Wei <lw@cn.fujitsu.com> Li Xun <xunleer.li@huawei.com> Li Yang <leoli@freescale.com&g...

...o Alterman <lalterman@nicira.com> Leo Song <liangs@marvell.com> Leo Yan <leoy@marvell.com> Leon Romanovsky <leon@leon.nu> Leonid Isaev <lisaev@umail.iu.edu> Leonid Shatz <leonid.shatz@ravellosystems.com> Leonid Yegoshin <yegoshin@mips.com> Ley Foon Tan <lftan@altera.com> Li Dongyang <Jerry87905@gmail.com> Li Fei <fei.li@intel.com> Li RongQing <roy.qing.li@gmail.com> Li Wang <wangli@kylinos.com.cn> Li Wei <lw@cn.fujitsu.com> Li Xun <xunleer.li@huawei.com> Li Yang <leoli@freescale.com&g...