search for: evalul

Displaying 9 results from an estimated 9 matches for "evalul".

Did you mean: evalue
2023 Jan 12
4
return value of {....}
Hello Akshay, R is quite inspired by LISP, where this is a common thing. It is not in fact that {...} returned something, rather any expression evalulates to some value, and for a compound statement that is the last evaluated expression. {...} might be seen as similar to LISPs (begin ...). Now this is a very different thing compared to {...} in something like C, even if it looks or behaves similarly. But in R {...} is in fact an expression and...
2023 Jan 13
1
return value of {....}
...s John Chambers et all didn't either. -Bill On Fri, Jan 13, 2023 at 2:28 AM Valentin Petzel <valentin at petzel.at> wrote: > Hello Akshay, > > R is quite inspired by LISP, where this is a common thing. It is not in > fact that {...} returned something, rather any expression evalulates to > some value, and for a compound statement that is the last evaluated > expression. > > {...} might be seen as similar to LISPs (begin ...). > > Now this is a very different thing compared to {...} in something like C, > even if it looks or behaves similarly. But in R {....
2023 Jan 15
3
return value of {....}
...g() [1] 1 2 3 4 5 106 107 108 109 110 On Fri, 13 Jan 2023 at 23:28, Valentin Petzel <valentin at petzel.at> wrote: > Hello Akshay, > > R is quite inspired by LISP, where this is a common thing. It is not in > fact that {...} returned something, rather any expression evalulates to > some value, and for a compound statement that is the last evaluated > expression. > > {...} might be seen as similar to LISPs (begin ...). > > Now this is a very different thing compared to {...} in something like C, > even if it looks or behaves similarly. But in R {....
2008 May 22
4
how to find out autoincrement id ?
Hi I need to push newly created item id to file. (ie. its autoincrement value) I tried this on controller but it wont work, it cant find id value for the newly created item. def create @imitem = Imitem.new(params[:imitem]) system "echo \"@imitem.id\" > /tmp/myid" any help ? --~--~---------~--~----~------------~-------~--~----~ You received this message because you
2023 Jan 16
1
return value of {....}
...g() [1] 1 2 3 4 5 106 107 108 109 110 On Fri, 13 Jan 2023 at 23:28, Valentin Petzel <valentin at petzel.at> wrote: > Hello Akshay, > > R is quite inspired by LISP, where this is a common thing. It is not in > fact that {...} returned something, rather any expression evalulates to > some value, and for a compound statement that is the last evaluated > expression. > > {...} might be seen as similar to LISPs (begin ...). > > Now this is a very different thing compared to {...} in something like C, > even if it looks or behaves similarly. But in R {....
2023 Jan 16
2
return value of {....}
...g() [1] 1 2 3 4 5 106 107 108 109 110 On Fri, 13 Jan 2023 at 23:28, Valentin Petzel <valentin at petzel.at> wrote: > Hello Akshay, > > R is quite inspired by LISP, where this is a common thing. It is not in > fact that {...} returned something, rather any expression evalulates to > some value, and for a compound statement that is the last evaluated > expression. > > {...} might be seen as similar to LISPs (begin ...). > > Now this is a very different thing compared to {...} in something like C, > even if it looks or behaves similarly. But in R {....
2023 Jan 09
3
return value of {....}
Dear Valentin, But why should {....} "return" a value? It could just as well evaluate all the expressions and store the resulting objects in whatever environment the interpreter chooses, and then it would be left to the user to manipulate any object he chooses. Don't you think returning the last, or any value, is redundant? We are living in the 21st century
2023 Jan 16
1
return value of {....}
...1] 1 2 3 4 5 106 107 108 109 110 On Fri, 13 Jan 2023 at 23:28, Valentin Petzel <valentin at petzel.at> wrote: > Hello Akshay, > > R is quite inspired by LISP, where this is a common thing. It is not > in fact that {...} returned something, rather any expression > evalulates to some value, and for a compound statement that is the > last evaluated expression. > > {...} might be seen as similar to LISPs (begin ...). > > Now this is a very different thing compared to {...} in something like > C, even if it looks or behaves similarly. But in R {...}...
2013 May 31
22
accidentally created a rails app in the home folder
Im a new user - I just installed rails, following directions here: http://rubyonrails.org/download however, when it came time to make a rails new path/etc/etc I get this message: Can''t initialize a new Rails application within the directory of another, please change to a non-Rails directory first. The only complication during the download was that I had to upgrade from version 1.8.6 to