How to use *.rb files in xp/vx
- Thread starter Ulqiorra
- Start date
I know of two ways to run external .rb-files.
You can require them:
[rgss]$: << '.' # Add the current working directory
require 'my_file' # You don't have to write .rb, but you can do it
[/rgss]
Note that you cannot require .so-files like you can in Ruby.
The other way is to load the data of the file and then evaluate it:
[rgss]file = File.open('my_file.rb', 'r+')
data = f.read
file.close
eval(data)
[/rgss]
With this approach the file extension doesn't have to be .rb
The difference between the former and latter approach is that require only execute the file the first time where as the second way evaluates the data every time it is encountered. There probably are other differences although I doubt they will be of any significance except in rare situations.
*hugs*
- Zeriab
You can require them:
[rgss]$: << '.' # Add the current working directory
require 'my_file' # You don't have to write .rb, but you can do it
[/rgss]
Note that you cannot require .so-files like you can in Ruby.
The other way is to load the data of the file and then evaluate it:
[rgss]file = File.open('my_file.rb', 'r+')
data = f.read
file.close
eval(data)
[/rgss]
With this approach the file extension doesn't have to be .rb
The difference between the former and latter approach is that require only execute the file the first time where as the second way evaluates the data every time it is encountered. There probably are other differences although I doubt they will be of any significance except in rare situations.
*hugs*
- Zeriab
You run the code in the game environment which means that you can use all classes and etc. which is present. That includes the hidden classes.
@SolstICE:
Or perhaps that is exactly what you should use in case of F12.
If the code should not be executed more than once then require will take care of it.
If it overrides methods then you shouldn't use require.
It really depends on the situation.
@SolstICE:
Or perhaps that is exactly what you should use in case of F12.
If the code should not be executed more than once then require will take care of it.
If it overrides methods then you shouldn't use require.
It really depends on the situation.
One more question (for real this time).
How do I make a rescue for subclasses of the StandardError class?
Do I do this:
rescue StandardError::Error
or rescue Error
or what?
And can I have multiple rescue clauses in one begin/end?
Like:
begin
rescue Err1
rescue Err2
end
How do I make a rescue for subclasses of the StandardError class?
Do I do this:
rescue StandardError::Error
or rescue Error
or what?
And can I have multiple rescue clauses in one begin/end?
Like:
begin
rescue Err1
rescue Err2
end
You just rescue the particular classes you want.
You can have something like
[rgss]begin
 # some code
rescue ArgumentError
 # Rescue Argument Error
rescue NameError
 # Rescue Name Error
rescue StandardError
 # Rescue all other standard errors
rescue RuntimeError
 # This will never be called since 'rescue StandardError' catches this one as well.
end
[/rgss]
Do you see how this works? Look in the help file for checking which error classes are built-in.
Feel free to ask if there is anything you don't understand.
*hugs*
- Zeriab
You can have something like
[rgss]begin
 # some code
rescue ArgumentError
 # Rescue Argument Error
rescue NameError
 # Rescue Name Error
rescue StandardError
 # Rescue all other standard errors
rescue RuntimeError
 # This will never be called since 'rescue StandardError' catches this one as well.
end
[/rgss]
Do you see how this works? Look in the help file for checking which error classes are built-in.
Feel free to ask if there is anything you don't understand.
*hugs*
- Zeriab