artemevil83 / app-inventor-for-android

Automatically exported from code.google.com/p/app-inventor-for-android
0 stars 0 forks source link

local variable in procedure with result block #17

Closed GoogleCodeExporter closed 6 years ago

GoogleCodeExporter commented 9 years ago
It would be usefull to have locale variable definition in procedure with result 
block.

We could compute a result and return it with out aving tu use a global variable 
to store and manipulate it.
Using a global variable for doing that is really ugly and a nest to bug 

Original issue reported on code.google.com by bruno.ro...@gmail.com on 9 Sep 2010 at 4:55

GoogleCodeExporter commented 9 years ago

Original comment by halabel...@google.com on 11 Sep 2010 at 2:51

GoogleCodeExporter commented 9 years ago
Gets my vote

Also a fixed constant would be handy (but not really essential)

Original comment by jimbrown...@gmail.com on 3 Oct 2010 at 11:44

GoogleCodeExporter commented 9 years ago
Local variables would also reduce the size of the My Definitions list

Original comment by Julie.Sm...@gmail.com on 9 Oct 2010 at 3:15

GoogleCodeExporter commented 9 years ago
Yes, local variables are a nice idea! :-)

Original comment by edgar.b....@gmail.com on 9 Oct 2010 at 4:02

GoogleCodeExporter commented 9 years ago
For good programming tecniques, local variables are essential.

Original comment by sammyde...@gmail.com on 27 Oct 2010 at 8:36

GoogleCodeExporter commented 9 years ago
Yep, im currently investigating a bug of mine that could easily be fixed with a 
local variable.

Original comment by imnotspa...@gmail.com on 1 Nov 2010 at 10:47

GoogleCodeExporter commented 9 years ago
Local variables would also enable recursion

Original comment by Julie.Sm...@gmail.com on 2 Nov 2010 at 2:08

GoogleCodeExporter commented 9 years ago
Issue 760 has been merged into this issue.

Original comment by halabel...@google.com on 21 Nov 2010 at 9:06

GoogleCodeExporter commented 9 years ago
the blocks editor should have a seperate page for each screen also, to remove 
alot a lot of clutter and make it easier to edit one screen.

Original comment by chrisyu...@gmail.com on 24 Nov 2010 at 4:11

GoogleCodeExporter commented 9 years ago
Love AI and what is being attempted. Congratulations Google! 

Having said that, from a software engineering principle, the absence of local 
variables make non-trivial applications a near impossibility  -- very difficult 
to maintain, extend, debug, etc. 

In my  opinion, this is one of those features without which AI becomes a toy 
language. It's not that the lack of this particular enhancement alone makes AI 
a toy language, but rather there are a number of missing features that mitigate 
the usefulness of AI (not being able to create arrays of objects is another 
one).

I feel that this issue is more important than the number of votes would imply 

Original comment by jim.rose...@gmail.com on 28 Dec 2010 at 9:43

GoogleCodeExporter commented 9 years ago

Original comment by sper...@google.com on 7 Jan 2011 at 12:38

GoogleCodeExporter commented 9 years ago
I really do hope that local variables will be a general feature of AI and not 
restricted to the "procedure with result" block.

Original comment by tippor...@gmail.com on 7 Jan 2011 at 9:03

GoogleCodeExporter commented 9 years ago
I think it is not just in result blocks that it is useful. A lot of times you 
would want to cache variables so that you don't have to recalculate it like the 
use of let in scheme. I would really like to see this implemented. For now I 
had to use ugly cache variables for different procedures.

Original comment by teongle...@gmail.com on 2 Feb 2011 at 6:19

GoogleCodeExporter commented 9 years ago
Local variables would also help with procedure signatures. So you don't have to 
define unique parameter names for procedures that take similar input. 

Original comment by phe...@gmail.com on 7 Feb 2011 at 9:09

GoogleCodeExporter commented 9 years ago
the current version of the appinventor.googlelabs.com website generates an App 
Inventor webpage that has most of its box labels and titles (other than those 
of the Palette Basic options) written in non-alphanumeric symbols resembling 
those used in assembler or machine language.  Can you revert this snafu back to 
where students can read what the box titles and labels mean in English, please ?

Baylor Gibson, GCC CSIS 180 student

Original comment by mngr...@gmail.com on 10 Mar 2011 at 11:34

GoogleCodeExporter commented 9 years ago
Local variable is fundamental, the variable destroyed after end of sub routine !
Other essential thing is SPEEEDDD of code execution, in other case WE WIL NEVER 
SEE
OPEN GL CUBE rotating at 15-25 fps second with app inventor, and never have 
more application than iphone ???? CAUSE SLOOOOOOW runtime !!!! 

Original comment by HektorBa...@gmail.com on 23 Mar 2011 at 2:40

GoogleCodeExporter commented 9 years ago
This is the first thing i noticed when i used the procedure with result.  using 
globals for this defeats the object!  Perhaps block called "set RETURN VALUE 
to" would be a step in the right direction

Original comment by michael....@gmail.com on 6 Jun 2011 at 1:16

GoogleCodeExporter commented 9 years ago
Issue 1670 has been merged into this issue.

Original comment by halabel...@google.com on 10 Jul 2011 at 1:22

GoogleCodeExporter commented 9 years ago
Issue 1722 has been merged into this issue.

Original comment by halabel...@google.com on 16 Jul 2011 at 10:30