mmo-ref/polserver
1
0
Fork 0
mirror of https://github.com/polserver/polserver synced 2026-08-13 08:23:08 -04:00
Code Issues Projects Releases Packages Wiki Activity
polserver/pol-core/bscript/compiler/analyzer/LocalVariableScope.cpp

59 lines
1.9 KiB
C++
Raw Permalink Normal View History

var statements in program blocks (#256) Adds: - analyzer/LocalVariableScope: tracks local variables created within a given scope. - Instantiated on the stack during semantic analysis, this registers itself with LocalVariableScopes during construction and deregisters itself during destruction. - Detects unused variables during deregistration - analyzer/LocalVariableScopes: this is what LocalVariableScope registers with. - keeps track of the stack of local scopes. - can provide the current local scope, for var statements. Other notes: "Shadowed" variables: this is when a variable in one scope hides a variable in another, like so: var a := 2; if (a) var a := 3; a := 4; endif print(a); // still 2 "debug_variables": We'll use these later when writing debug files.
2020-08-30 01:32:38 -07:00
#include "LocalVariableScope.h"
Properly scope the compiler includes to the Bscript folder. (#360)
2021-02-25 16:53:22 +01:00
#include "bscript/compiler/Report.h"
#include "bscript/compiler/analyzer/LocalVariableScopes.h"
#include "bscript/compiler/analyzer/Variables.h"
#include "bscript/compiler/file/SourceLocation.h"
#include "bscript/compiler/model/LocalVariableScopeInfo.h"
#include "bscript/compiler/model/Variable.h"
var statements in program blocks (#256) Adds: - analyzer/LocalVariableScope: tracks local variables created within a given scope. - Instantiated on the stack during semantic analysis, this registers itself with LocalVariableScopes during construction and deregisters itself during destruction. - Detects unused variables during deregistration - analyzer/LocalVariableScopes: this is what LocalVariableScope registers with. - keeps track of the stack of local scopes. - can provide the current local scope, for var statements. Other notes: "Shadowed" variables: this is when a variable in one scope hides a variable in another, like so: var a := 2; if (a) var a := 3; a := 4; endif print(a); // still 2 "debug_variables": We'll use these later when writing debug files.
2020-08-30 01:32:38 -07:00
namespace Pol::Bscript::Compiler
{
LocalVariableScope::LocalVariableScope( LocalVariableScopes& scopes,
Consolidate local variable scope information (#301) Adds: - model/LocalVariableScopeInfo.h Stores, for local variable blocks: - the names of the local variables in the block - the "base index" of those local variables within the current scope The code generator uses these to clean up local variables as they go out of scope. We also need this when writing debug information.
2020-09-12 09:31:52 -07:00
LocalVariableScopeInfo& local_variable_scope_info )
var statements in program blocks (#256) Adds: - analyzer/LocalVariableScope: tracks local variables created within a given scope. - Instantiated on the stack during semantic analysis, this registers itself with LocalVariableScopes during construction and deregisters itself during destruction. - Detects unused variables during deregistration - analyzer/LocalVariableScopes: this is what LocalVariableScope registers with. - keeps track of the stack of local scopes. - can provide the current local scope, for var statements. Other notes: "Shadowed" variables: this is when a variable in one scope hides a variable in another, like so: var a := 2; if (a) var a := 3; a := 4; endif print(a); // still 2 "debug_variables": We'll use these later when writing debug files.
2020-08-30 01:32:38 -07:00
: scopes( scopes ),
report( scopes.report ),
block_depth( scopes.local_variable_scopes.size() ),
prev_locals( scopes.local_variables.count() ),
Consolidate local variable scope information (#301) Adds: - model/LocalVariableScopeInfo.h Stores, for local variable blocks: - the names of the local variables in the block - the "base index" of those local variables within the current scope The code generator uses these to clean up local variables as they go out of scope. We also need this when writing debug information.
2020-09-12 09:31:52 -07:00
local_variable_scope_info( local_variable_scope_info )
var statements in program blocks (#256) Adds: - analyzer/LocalVariableScope: tracks local variables created within a given scope. - Instantiated on the stack during semantic analysis, this registers itself with LocalVariableScopes during construction and deregisters itself during destruction. - Detects unused variables during deregistration - analyzer/LocalVariableScopes: this is what LocalVariableScope registers with. - keeps track of the stack of local scopes. - can provide the current local scope, for var statements. Other notes: "Shadowed" variables: this is when a variable in one scope hides a variable in another, like so: var a := 2; if (a) var a := 3; a := 4; endif print(a); // still 2 "debug_variables": We'll use these later when writing debug files.
2020-08-30 01:32:38 -07:00
{
Consolidate local variable scope information (#301) Adds: - model/LocalVariableScopeInfo.h Stores, for local variable blocks: - the names of the local variables in the block - the "base index" of those local variables within the current scope The code generator uses these to clean up local variables as they go out of scope. We also need this when writing debug information.
2020-09-12 09:31:52 -07:00
local_variable_scope_info.base_index = prev_locals;
var statements in program blocks (#256) Adds: - analyzer/LocalVariableScope: tracks local variables created within a given scope. - Instantiated on the stack during semantic analysis, this registers itself with LocalVariableScopes during construction and deregisters itself during destruction. - Detects unused variables during deregistration - analyzer/LocalVariableScopes: this is what LocalVariableScope registers with. - keeps track of the stack of local scopes. - can provide the current local scope, for var statements. Other notes: "Shadowed" variables: this is when a variable in one scope hides a variable in another, like so: var a := 2; if (a) var a := 3; a := 4; endif print(a); // still 2 "debug_variables": We'll use these later when writing debug files.
2020-08-30 01:32:38 -07:00
scopes.local_variable_scopes.push_back( this );
}
LocalVariableScope::~LocalVariableScope()
{
scopes.local_variables.remove_all_but( prev_locals );
for ( auto& variable : shadowing )
{
scopes.local_variables.restore_shadowed( variable );
}
scopes.local_variable_scopes.pop_back();
}
std::shared_ptr<Variable> LocalVariableScope::create( const std::string& name, WarnOn warn_on,
const SourceLocation& source_location )
{
if ( auto existing = scopes.local_variables.find( name ) )
{
if ( existing->block_depth == block_depth )
{
report.error( source_location, "Variable '", name, "' is already in scope.\n",
" See previous definition at: ",
existing->source_location, "\n" );
return existing;
}
shadowing.push_back( existing );
}
auto local = scopes.local_variables.create( name, block_depth, warn_on,
source_location );
Consolidate local variable scope information (#301) Adds: - model/LocalVariableScopeInfo.h Stores, for local variable blocks: - the names of the local variables in the block - the "base index" of those local variables within the current scope The code generator uses these to clean up local variables as they go out of scope. We also need this when writing debug information.
2020-09-12 09:31:52 -07:00
local_variable_scope_info.variables.push_back( local );
var statements in program blocks (#256) Adds: - analyzer/LocalVariableScope: tracks local variables created within a given scope. - Instantiated on the stack during semantic analysis, this registers itself with LocalVariableScopes during construction and deregisters itself during destruction. - Detects unused variables during deregistration - analyzer/LocalVariableScopes: this is what LocalVariableScope registers with. - keeps track of the stack of local scopes. - can provide the current local scope, for var statements. Other notes: "Shadowed" variables: this is when a variable in one scope hides a variable in another, like so: var a := 2; if (a) var a := 3; a := 4; endif print(a); // still 2 "debug_variables": We'll use these later when writing debug files.
2020-08-30 01:32:38 -07:00
return local;
}
} // namespace Pol::Bscript::Compiler
Reference in a new issue Copy permalink