[api-issues] [Issue 69930] Functions allowed as LVALU ES in Basic

2010-11-12 Thread thocurgithe
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=69930





--- Additional comments from thocurgi...@openoffice.org Fri Nov 12 10:24:35 
+ 2010 ---
Created an attachment (id=74696)
silagra brand name viagra cumwithuscom


-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: issues-unsubscr...@api.openoffice.org
For additional commands, e-mail: issues-h...@api.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org



[api-issues] [Issue 69930] Functions allowed as LVALU ES in Basic

2007-01-15 Thread terrye
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=69930





--- Additional comments from [EMAIL PROTECTED] Mon Jan 15 01:28:48 -0800 
2007 ---
Andreas, I've checked the source. SbiRuntime::StepSTMNT even contains an
explicit check and tolerates this one.  Given that OOo Basic architecturally
tolerates a function call in the context of a subroutine call, and the compiler
as currently constructed defers the issue of binding a(i,j) to a function or an
external public variable at runtime, you can't error on this one.

My recommendation is to move this one to documentation and include an
appropriate note in the next StarBasic Manual.   

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[api-issues] [Issue 69930] Functions allowed as LVALU ES in Basic

2007-01-15 Thread terrye
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=69930





--- Additional comments from [EMAIL PROTECTED] Mon Jan 15 01:28:24 -0800 
2007 ---
Andreas, I've checked the source. SbiRuntime::StepSTMNT even contains an
explicit check and tolerates this one.  Given that OOo Basic architecturally
tolerates a function call in the context of a subroutine call, and the compiler
as currently constructed defers the issue of binding a(i,j) to a function or an
external public variable at runtime, you can't error on this one.

My recommendation is to move this one to documentation and include an
appropriate note in the next StarBasic Manual.   

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[api-issues] [Issue 69930] Functions allowed as LVALU ES in Basic

2006-12-19 Thread terrye
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=69930





--- Additional comments from [EMAIL PROTECTED] Tue Dec 19 15:10:40 -0800 
2006 ---
Having had a look at the compiler output, the code generator generate the same
code for:
  a(i) = a (i) + 1
that is:
  ARGC
  FIND  i;Variant
  ARGV
  FIND  a
  ARGC
  FIND  i;Variant
  ARGV
  FIND  a
  CONST 1
  PLUS  
  PUT
whether a is an array or a function.  This discrimination is carried out by the
RTS in StepFIND.  Not sure how to pick this one up in the current split of
compiler/RTS.  

Suggest that this is introduced as Documentation caveat.  

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[api-issues] [Issue 69930] Functions allowed as LVALU ES in Basic

2006-10-05 Thread ab
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=69930


User ab changed the following:

What|Old value |New value

  Ever confirmed|  |1

  Status|UNCONFIRMED   |STARTED

Target milestone|---   |OOo 2.x





--- Additional comments from [EMAIL PROTECTED] Thu Oct  5 01:59:06 -0700 
2006 ---
Started, OOo 2.x


-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[api-issues] [Issue 69930] Functions allowed as LVALU ES in Basic

2006-09-28 Thread terrye
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=69930
 Issue #|69930
 Summary|Functions allowed as LVALUES in Basic
   Component|api
 Version|OOo 2.0.3
Platform|All
 URL|
  OS/Version|All
  Status|UNCONFIRMED
   Status whiteboard|
Keywords|
  Resolution|
  Issue type|DEFECT
Priority|P3
Subcomponent|code
 Assigned to|ab
 Reported by|terrye





--- Additional comments from [EMAIL PROTECTED] Thu Sep 28 00:35:00 -0700 
2006 ---
In OO Basic functions are tolerated as Lvalues (This is not the case in VBA).  

Sub main()
  b = 1
  MsgBox b
End Sub
Function b()
  b = 3
End Function

This prints out 3.  This is particularly dangerous where programmers are NOT
using "Option Explicit" and have the routine in a separate module, so they think
that they are using an implicitly declared local variable.

OOB should throw up a compile error if functions are used as LVALUES as does 
VBA.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]