search for: smallexamples

The R Language Definition manual should document comments. I think this should go after section 10.1 "The Parsing Process" and before 10.2 "Tokens". Here's some draft text. @node Comments, Tokens, The parsing process, Parser @comment node-name, next, previous, up @section Comments Comments in R are ignored by the parser. Any text from a \# character to the end of

Hi Can some one please point out where i am wrong. I am trying to position set of nodes column-wise in cytoscape using RCytoscape A----D B----E C----F ------------------- g <- new ('graphNEL', edgemode='undirected') cw <- CytoscapeWindow ('smallExample', graph=RCytoscape::makeSimpleGraph()) layout (cw, 'jgraph-spring') redraw(cw) nodesFr = c('A',

I want to include a multi-line code block in the details section of a R manual page. How do I get an appropriate verbatim-like environment? \verbatim{...} doesn't do the trick, neither does \code{...}. -Greg LEGAL NOTICE\ Unless expressly stated otherwise, this messag...{{dropped}}

Folks, The projects cleanup has been completed. The "ModuleMaker" project is now in projects/SmallExamples/ModuleMaker. Additionally there are two new programs in SmallExamples contributed by Valery Khamenya: Fibonacci and HowToUseJIT. Thanks Valery! You should "cvs update -PdR" in the projects directory to get the changes. Thanks, Reid.

Hello list, I am writing a paper for Rnews. I use Sweave to do it. I did not find information about writing a paper for Rnews using Sweave and have some questions: - Is there a problem to use the environment 'Sinput' in the place of 'example' or 'smallexample'. It works fine but perhaps there are some technical/editorial problems ? - I have some long lines of code in

...ought I'd give it a go with a recent CVS check-out. $ ./configure configure: WARNING: Unknown project (HowToUseJIT) won't be configured automatically configure: WARNING: Unknown project (ModuleMaker) won't be configured automatically configure: WARNING: Unknown project (SmallExamples) won't be configured automatically checking build system type... i386-unknown-openbsd3.8 checking host system type... i386-unknown-openbsd3.8 checking target system type... i386-unknown-openbsd3.8 checking type of operating system we're on... Unknown configure: error: Op...

...t a go with a recent CVS check-out. > > $ ./configure > configure: WARNING: Unknown project (HowToUseJIT) won't be configured automatically > configure: WARNING: Unknown project (ModuleMaker) won't be configured automatically > configure: WARNING: Unknown project (SmallExamples) won't be configured automatically > checking build system type... i386-unknown-openbsd3.8 > checking host system type... i386-unknown-openbsd3.8 > checking target system type... i386-unknown-openbsd3.8 > checking type of operating system we're on... Unknown >...

...t a go with a recent CVS check-out. > > $ ./configure > configure: WARNING: Unknown project (HowToUseJIT) won't be configured automatically > configure: WARNING: Unknown project (ModuleMaker) won't be configured automatically > configure: WARNING: Unknown project (SmallExamples) won't be configured automatically > checking build system type... i386-unknown-openbsd3.8 > checking host system type... i386-unknown-openbsd3.8 > checking target system type... i386-unknown-openbsd3.8 > checking type of operating system we're on... Unknown >...

Hi Josephm > I would like to test but the I modigied the configure to make unknown > = OpenBSD and Unix and go pretty far but it died right after 'supports > mkdir' yes... Could that have been `checking for mkdir...'? > then the next line was 'your system is unsupported'' Have you looked at ./config.log. ./configure creates this as it runs as a trace of the

...don't (easily) allow this do they? You can > only build one program per directory. Were you suggesting that you wanted me to > move the entire directories under a "small examples" directory? You're right. The simples way to do this would be to have: projects/ SmallExamples/ ModuleMaker/ HowToUseTheJIT/ FibBuilder/ etc. Each subsubdir would have a makefile and a .cpp file. -Chris > Chris Lattner wrote: > > > On Tue, 17 Aug 2004, Reid Spencer wrote: > > > > > >&...

I would like to test but the I modigied the configure to make unknown = OpenBSD and Unix and go pretty far but it died right after 'supports mkdir' yes... then the next line was 'your system is unsupported'' I have gcc 3.3 on OpenBSD 3.3 pro-police stack compiler... I am only really interested in testing the C/C++ but C primarily for my work. regards, Joseph Altea

On second thought, the makefiles don't (easily) allow this do they? You can only build one program per directory. Were you suggesting that you wanted me to move the entire directories under a "small examples" directory? Reid. Chris Lattner wrote: > On Tue, 17 Aug 2004, Reid Spencer wrote: > > >>That's pretty cute actually. Do you want this

On Tue, 17 Aug 2004, Reid Spencer wrote: > That's pretty cute actually. Do you want this "brilliant" :) example in the cvs > repository? I'd be happy to put it in. Here's an idea: how about we take the ModuleMaker, Valery's previous example, and this one and put them all in one "small examples" project? -Chris > Valery A.Khamenya wrote: > >

Hello, Here are some patches for R-intro.texi, to correct various typos, missing words, and minor inconsistencies in formatting. Each patch is preceeded by its corresponding 'wdiff' output to make it easier to see which words have changed. -- Brian Gough Network Theory Ltd, Publishing the R Reference Manuals --- http://www.network-theory.co.uk/R/