search for: mypattern

...art date and end date from this form using: # # Specifying station and reading from the opening form stn<-"03015795" myurl<-paste("http://ida.water.usgs.gov/ida/available_records.cfm?sn=",stn,sep="") mypage1 = readLines(myurl) # Getting the start and end dates mypattern = '<td align="center">([^<]*)</td>' datalines = grep(mypattern, mypage1[124], value=TRUE) getexpr = function(s,g)substring(s,g,g+attr(g,'match.length')-1) gg = gregexpr(mypattern, datalines) matches = mapply(getexpr,datalines,gg) result = gsub(mypattern,'...

Dear R-users, is there a way to pass a list of patterns to the grep function? I vaguely remember something with %in% operator... Thanks, St?phane. -- "La science a certes quelques magnifiques r?ussites ? son actif mais ? tout prendre, je pr?f?re de loin ?tre heureux plut?t qu'avoir raison." D. Adams -- AGC website <http://www.genoscope.cns.fr/agc> St?phane

...t adding a way to define a pattern that is independent of > the input text seems like it could be useful. > > > > I’d suggest that initially at least, the define-a-pattern directive would > take only “immediate” text, no embedded regexes. That is, you could do > > DEFPAT[MYPATTERN]: Define a pattern here > > but you couldn’t do > > DEFPAT[MYPATTERN]: Define {{some|any}} pattern here > > although it might be reasonable to allow > > DEFPAT[PATTERN1]: some > > DEFPAT[PATTERN2]: Define [[PATTERN1]] pattern here > > as the [[]] subs...

​Hi all, > I feel it might be confusing to have a CHECK becomes effectively a CHECK-NOT, > especially if the RUN line is far from the CHECK line (which is often the case when > a single RUN line drives several groups of CHECK directives (e.g. code generation > tested for several functions for a specific feature, like PIC). You also loose control > on where the NOT should be: