The following warnings occurred:
Warning [2] Use of undefined constant SAPI_NAME - assumed 'SAPI_NAME' (this will throw an Error in a future version of PHP) - Line: 3388 - File: inc/functions.php PHP 7.4.33-nmm7 (Linux)
File Line Function
/inc/functions.php 3388 errorHandler->error
/showthread.php 116 build_archive_link
Warning [2] Use of undefined constant IN_ARCHIVE - assumed 'IN_ARCHIVE' (this will throw an Error in a future version of PHP) - Line: 3331 - File: inc/functions.php PHP 7.4.33-nmm7 (Linux)
File Line Function
/inc/functions.php 3331 errorHandler->error
/inc/functions.php 3324 build_forum_breadcrumb
/showthread.php 195 build_forum_breadcrumb
Warning [2] Use of undefined constant IN_ARCHIVE - assumed 'IN_ARCHIVE' (this will throw an Error in a future version of PHP) - Line: 3331 - File: inc/functions.php PHP 7.4.33-nmm7 (Linux)
File Line Function
/inc/functions.php 3331 errorHandler->error
/showthread.php 195 build_forum_breadcrumb




SphereCommunity / Sphere 0.56d / General Help v / problems with <call functionname>


Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
problems with <call functionname>
Author Message
wuffel
Apprentice
*

Posts: 28
Likes Given: 0
Likes Received: 4 in 2 posts
Joined: Mar 2012
Reputation: 1



Post: #9
RE: problems with <call functionname>
doesnt matter. posted a bug-report since it should work due to the revision changelog. as long as a function has a "return"-value the assignment of a value - even with a function - should work.

either local.value=<call functionname> nor if <call functionname> works.
09-01-2013 05:39 AM
Find all posts by this user Like Post Quote this message in a reply
Post Reply 


Messages In This Thread
problems with <call functionname> - wuffel - 08-28-2013, 12:15 AM
RE: problems with <call functionname> - wuffel - 09-01-2013 05:39 AM

Forum Jump:


User(s) browsing this thread: 6 Guest(s)

Contact Us | SphereCommunity | Return to Top | Return to Content | Mobile Version | RSS Syndication