Classes
The following classes are available globally.
-
A
LogFormatter
configured to be ideal for writing human-readable log files.By default, this formatter:
- Uses
.default
as theTimestampStyle
- Uses a custom
SeverityStyle
that pads the capitalized severity name - Uses
.hex
as theCallingThreadStyle
- Uses default field separator delimiters
- Outputs the source code filename and line number of the call site
Each of these settings can be overridden during instantiation.
See moreDeclaration
Swift
open class ReadableLogFormatter: StandardLogFormatter
- Uses
-
A
See moreLogFormatter
that outputs Xcode-bound trace information for eachLogEntry
that has aPayload
of.trace
.Declaration
Swift
public final class XcodeTraceLogFormatter: FieldBasedLogFormatter
-
A
See moreLogConfiguration
optimized for use when running within Xcode.Declaration
Swift
open class XcodeLogConfiguration: ConsoleLogConfiguration
-
A
LogRecorder
implementation that maintains a set of daily rotating log files, kept for a user-specified number of days.See moreImportant
ARotatingLogFileRecorder
instance assumes full control over the log directory specified by itsdirectoryPath
property. Please see the initializer documentation for details.Declaration
Swift
open class RotatingLogFileRecorder: LogRecorderBase
-
The
See moreStandardOutputLogRecorder
is anOutputStreamLogRecorder
that writes log messages to the standard output stream (`stdout`
) of the running process.Declaration
Swift
open class StandardOutputLogRecorder: OutputStreamLogRecorder
-
A
See moreLogConfiguration
that uses an underlyingRotatingLogFileRecorder
to maintain a directory of log files that are rotated on a daily basis.Declaration
Swift
open class RotatingLogFileConfiguration: BasicLogConfiguration
-
The
See moreOutputStreamLogRecorder
logs messages by writing to the standard output stream of the running process.Declaration
Swift
open class OutputStreamLogRecorder: LogRecorderBase
-
In case the name didn’t give it away, the
See moreBasicLogConfiguration
class provides a basic implementation of theLogConfiguration
protocol.Declaration
Swift
open class BasicLogConfiguration: LogConfiguration
-
The
BufferedLogRecorder
is a genericLogRecorder
that buffers the log messages passed to itsrecord()
function.Construction requires a
createBufferItem
function, which is responsible for converting theLogEntry
and formatted messageString
into the genericBufferItem
type.Three specific subclasses are also provided which will buffer a different
BufferItem
type for each call torecord()
:BufferedMessageRecorder
storesString
s containing the formatted log message.BufferedLogEntryRecorder
stores theLogEntry
values passed torecord()
.BufferedLogEntryMessageRecorder
stores a(LogEntry, String)
tuple containing theLogEntry
and formatted log message.
Declaration
Swift
open class BufferedLogRecorder<BufferItem>: LogRecorderBase
-
The
See moreBufferedMessageRecorder
buffers the formatted log messages passed to itsrecord()
function.Declaration
Swift
open class BufferedMessageRecorder: BufferedLogRecorder<String>
-
Declaration
Swift
open class BufferedLogEntryRecorder: BufferedLogRecorder<LogEntry>
-
The
See moreBufferedLogEntryMessageRecorder
buffers eachLogEntry
and formatted message passed to itsrecord()
function.Declaration
Swift
open class BufferedLogEntryMessageRecorder: BufferedLogRecorder<(LogEntry, String)>
-
A
LogRecorder
implementation that appends log entries to a file.See moreNote
FileLogRecorder
is a simple log appender that provides no mechanism for file rotation or truncation. Unless you manually manage the log file when aFileLogRecorder
doesn’t have it open, you will end up with an ever-growing file. Use aRotatingLogFileRecorder
instead if you’d rather not have to concern yourself with such details.Declaration
Swift
open class FileLogRecorder: LogRecorderBase
-
The
FieldBasedLogFormatter
provides a simple interface for constructing a customizedLogFormatter
by specifying different fields.Let’s say you wanted to construct a
LogFormatter
that outputs the following fields separated by tabs:- The
LogEntry
‘stimestamp
property as a UNIX time value - The
severity
of theLogEntry
as a numeric value - The
Payload
of theLogEntry
You could do this by constructing a
FieldBasedLogFormatter
as follows:
See morelet formatter = FieldBasedLogFormatter(fields: [.timestamp(.unix), .delimiter(.tab), .severity(.numeric), .delimiter(.tab), .payload])
Declaration
Swift
open class FieldBasedLogFormatter: ConcatenatingLogFormatter
- The
-
LogReceptacle
s provide the low-level interface for accepting log messages.Although you could use a
See moreLogReceptacle
directly to perform all logging functions, theLog
implementation provides a higher-level interface that’s more convenient to use within your code.Declaration
Swift
public final class LogReceptacle
-
The
See moreConcatenatingLogFormatter
lets you combine the output of multipleLogFormatter
s by concatenating their output and returning the result.Declaration
Swift
open class ConcatenatingLogFormatter: LogFormatter
-
A standard
LogConfiguration
that, by default, uses theos_log()
function (via theOSLogRecorder
), which is only available as of iOS 10.0, macOS 10.12, tvOS 10.0, and watchOS 3.0.If
See moreos_log()
is not available, or if theStandardLogConfiguration
is configured to bypass it, log messages will be written to either thestdout
orstderr
output stream of the running process.Declaration
Swift
open class ConsoleLogConfiguration: BasicLogConfiguration
-
The
StandardStreamsLogRecorder
is aLogRecorder
that writes log messages to either the standard output stream (`stdout`
) or the standard error stream (`stderr`
) of the running process.Messages are directed to the appropriate stream depending on the
severity
property of theLogEntry
being recorded.Messages having a severity of
See more.verbose
,.debug
and.info
will be directed tostdout
, while those with a severity of.warning
and.error
are directed tostderr
.Declaration
Swift
open class StandardStreamsLogRecorder: LogRecorderBase
-
A partial implementation of the
See moreLogRecorder
protocol.Declaration
Swift
open class LogRecorderBase: LogRecorder
-
The
See moreStandardErrorLogRecorder
is anOutputStreamLogRecorder
that writes log messages to the standard error stream (`stderr`
) of the running process.Declaration
Swift
open class StandardErrorLogRecorder: OutputStreamLogRecorder
-
A standard
See moreLogFormatter
that provides some common customization points.Declaration
Swift
open class StandardLogFormatter: FieldBasedLogFormatter
-
A
LogFormatter
configured to be ideal for writing machine-parsable log files.By default, this formatter:
- Uses
.unix
as theTimestampStyle
- Uses
.numeric
as theSeverityStyle
- Uses
.hex
as theCallingThreadStyle
- Uses
.tab
as theDelimiterStyle
- Outputs the source code filename and line number of the call site
Each of these settings can be overridden during instantiation.
See moreDeclaration
Swift
open class ParsableLogFormatter: StandardLogFormatter
- Uses
-
A
See moreLogFormatter
ideal for use within Xcode. This format is not well-suited for parsing.Declaration
Swift
public final class XcodeLogFormatter: LogFormatter


EXP InOut 360º 900 ms
ELASTIC InOut 270º 3000 ms
Cast Pyroclasm
Cast Ice
1-7 to change background. Use arrows to move the camera. See the
game test
. See the
source code
.


|
GML
Library
|
A struct templates for matrices of floating-point values. More...
#include <matrix_x.hpp>
Public Types | |
| using | MatT = Matrix< T, Major, Minor > |
| using | ColT = Vector< T, Minor > |
| using | RowT = Vector< T, Major > |
Public Member Functions | |
| MatT ()=default | |
| Default constructor. Elements of the Matrix are initialised to 0.0f by default. | |
| RowT | getRow (unsigned int idx) const |
| Constructs and returns a specific row of the Matrix. More... | |
| MatT | transpose () const |
| Calculates and returns the transpose matrix of the Matrix. More... | |
| template<typename = typename std::enable_if<Major == Minor>::type> | |
| MatT | minor () |
| template<typename = typename std::enable_if<Major == Minor>::type> | |
| MatT | cofactor () |
| template<typename = typename std::enable_if<Major == Minor>::type> | |
| MatT | adjoint () |
| template<typename = typename std::enable_if<Major == Minor>::type> | |
| MatT | inverse () |
| Calculates and returns the inverse matrix of the Matrix. More... | |
| template<typename = typename std::enable_if<Major == Minor>::type> | |
| float | determinant () const |
| Calculates and returns the determinant of the Matrix. More... | |
| ColT & | operator[] (unsigned int idx) |
| Accesses the columns of the Matrix using a given index. More... | |
| const ColT & | operator[] (unsigned int idx) const |
| Accesses the columns of the Matrix4 using a given index. More... | |
| MatT & | operator+= (const Matrix< T, Major, Minor > &rhs) |
| Adds another Matrix4 to the Matrix. More... | |
| MatT & | operator-= (const Matrix< T, Major, Minor > &rhs) |
| Subtracts another Matrix from the Matrix. More... | |
| MatT & | operator *= (float s) |
| Multiplies the elements of the Matrix by a scalar value. More... | |
| MatT & | operator/= (float s) |
| Divides the elements of the Matrix by a scalar value. More... | |
| MatT | operator- () const |
| Creates a copy of the Matrix with all components' signs flipped. More... | |
Public Attributes | |
| ColT | columns [Major] |
| The columns of the Matrix4. | |
A struct templates for matrices of floating-point values.
This struct is used to represent two-dimensional matrices of various sizes.
&someMatrix[0][0];
. This provides a pointer to the matrix's first element. Definition at line 19 of file matrix_x.hpp.
|
inline |
Calculates and returns the determinant of the Matrix.
Definition at line 133 of file matrix_x.hpp.
|
inline |
Constructs and returns a specific row of the Matrix.
| idx | The index of the row to return. |
Definition at line 38 of file matrix_x.hpp.
|
inline |
Calculates and returns the inverse matrix of the Matrix.
In 3D graphics, the inverse of a matrix is useful to reverse the original matrix's transformation.
Definition at line 123 of file matrix_x.hpp.
|
inline |
Multiplies the elements of the Matrix by a scalar value.
| s | A scalar value to multiply each Matrix element by. |
Definition at line 216 of file matrix_x.hpp.
|
inline |
|
inline |
Creates a copy of the Matrix with all components' signs flipped.
Definition at line 239 of file matrix_x.hpp.
|
inline |
|
inline |
Divides the elements of the Matrix by a scalar value.
| s | A scalar value to multiply each Matrix element by. |
Definition at line 228 of file matrix_x.hpp.
|
inline |
Accesses the columns of the Matrix using a given index.
| idx | The specified index of the column to return. |
Definition at line 169 of file matrix_x.hpp.
|
inline |
Accesses the columns of the Matrix4 using a given index.
| idx | The specified index of the column to return. |
Definition at line 180 of file matrix_x.hpp.
|
inline |
Calculates and returns the transpose matrix of the Matrix.
The transpose of a matrix is the same matrix but with elements of rows and columns switch around. In other words the matrix rows become the columns and the columns become the rows.
Definition at line 51 of file matrix_x.hpp.


I alwasys had interest in becoming a developer and I finally had time to start learning. I already coded a few static websites in the past 5 years using mostly HTML and CSS and I am now expanding my knowledge by becoming a Full Stack Developer. I am currently finishing a course with a focus on Ruby and Ruby on Rails with an additional overview of Bootstrap, REACT, SQL, JavaScript and AJAX.


Before Change
known_scope_infos = [GlobalOptionsRegistrar.get_scope_info()]
// Add scopes for all needed subsystems via a union of all known subsystem sets.
subsystems = Subsystem.closure(
GoalRunner.subsystems() | Goal.subsystems() | build_configuration.subsystems()
)
for subsystem in subsystems:
known_scope_infos.append(subsystem.get_scope_info())
// Add scopes for all tasks in all goals.
After Change
set(Goal.get_optionables()))
known_scope_infos = sorted({
si for optionable in top_level_optionables for si in optionable.known_scope_infos()
})
// Now that we have the known scopes we can get the full options.
options = options_bootstrapper.get_full_options(known_scope_infos)
distinct_optionable_classes = sorted({si.optionable_cls for si in known_scope_infos},
key=lambda o: o.options_scope)
for optionable_cls in distinct_optionable_classes:
optionable_cls.register_options_on_scope(options)


SAP Fiori: Lessons from the Greenhouse
Nigel James
@njames
@squarecloud
@ui5io
Greenhouse
Warm
Humid
Hothouse
Growth
MASTER is AWAYS DEPLOYABLE
Learning
Mountain
Don't be an island
TEAM is everything
MASTER is AWAYS DEPLOYABLE
Tooling
WebIDE
Eclipse
Intellij / WebStorm
Sublime Text - Atom
Source
Deploy
MASTER is AWAYS DEPLOYABLE
Minify
Issues
Contribute
Questions?
MASTER is AWAYS DEPLOYABLE
Handy Urls
Grunt
Contribute
Nigel James
@njames
@squarecloud
@ui5io


EDM NIGHT
DAY:- Sunday
TIME:- 7:30pm - 9:00pm
VENUE:- Ground
Event Details:
Electronic dance music (EDM), also known as dance music, club music, or simply dance, is a broad range of percussive electronic music genres made largely for nightclubs, raves and festivals. EDM producers also perform their music live in a concert
The Golden Rule of Dance ~ "Here's to now and to nothing else. In a crowd all by yourself."


Before Change
["ks", "registry", "add", "kubeflow", kubeflow_registry], cwd=app_dir)
// Install required packages
packages = ["kubeflow/core", "kubeflow/tf-serving", "kubeflow/tf-job"]
for p in packages:
util.run(["ks", "pkg", "install", p], cwd=app_dir)
After Change
libraries[pkg] = {"gitVersion":{"commitSha": "fake", "refSpec": "fake"}, "name": pkg, "registry": "kubeflow"}
app_yaml["libraries"] = libraries
with open(app_file, "w") as f:
yaml.dump(app_yaml, f)
// Create vendor directory with a symlink to the src
// so that we use the code at the desired commit.
target_dir = os.path.join(app_dir, "vendor", "kubeflow")
REPO_ORG = "kubeflow"
REPO_NAME = "kubeflow"


{% block related_items_header %}Artworks in Location{% endblock %}
{% include 'catalogue/search/search_bar.html' with artwork_search_form=artwork_search_form location_search_form=location_search_form exhibition_search_form=exhibition_search_form %}
{% include 'catalogue/search/elm_search_results.html' with object_list=search_results %}


Let's change the below HTML attribute.
In this case JavaScript changes the value of the src (source) attribute of an image.
Turn on bulb
Turn off light


| PERLXS(1) | Perl Programmers Reference Guide | PERLXS(1) |
Before writing XS, read the "CAVEATS" section below.
An XSUB forms the basic unit of the XS interface. After compilation by the xsubpp compiler, each XSUB amounts to a C function definition which will provide the glue between Perl calling conventions and C calling conventions.
The glue code pulls the arguments from the Perl stack, converts these Perl values to the formats expected by a C function, call this C function, transfers the return values of the C function back to Perl. Return values here may be a conventional C return value or any C function arguments that may serve as output parameters. These return values may be passed back to Perl either by putting them on the Perl stack, or by modifying the arguments supplied from the Perl side.
The above is a somewhat simplified view of what really happens. Since Perl allows more flexible calling conventions than C, XSUBs may do much more in practice, such as checking input parameters for validity, throwing exceptions (or returning undef/empty list) if the return value from the C function indicates failure, calling different C functions based on numbers and types of the arguments, providing an object-oriented interface, etc.
Of course, one could write such glue code directly in C. However, this would be a tedious task, especially if one needs to write glue for multiple C functions, and/or one is not familiar enough with the Perl stack discipline and other such arcana. XS comes to the rescue here: instead of writing this glue C code in long-hand, one can write a more concise short-hand description of what should be done by the glue, and let the XS compiler xsubpp handle the rest.
The XS language allows one to describe the mapping between how the C routine is used, and how the corresponding Perl routine is used. It also allows creation of Perl routines which are directly translated to C code and which are not related to a pre-existing C function. In cases when the C interface coincides with the Perl interface, the XSUB declaration is almost identical to a declaration of a C function (in K&R style). In such circumstances, there is another tool called "h2xs" that is able to translate an entire C header file into a corresponding XS file that will provide glue to the functions/macros described in the header file.
The XS compiler is called xsubpp. This compiler creates the constructs necessary to let an XSUB manipulate Perl values, and creates the glue necessary to let Perl call the XSUB. The compiler uses typemaps to determine how to map C function parameters and output values to Perl values and back. The default typemap (which comes with Perl) handles many common C types. A supplementary typemap may also be needed to handle any special structures and types for the library being linked. For more information on typemaps, see perlxstypemap.
A file in XS format starts with a C language section which goes until the first "MODULE =" directive. Other XS directives and XSUB definitions may follow this line. The "language" used in this part of the file is usually referred to as the XS language. xsubpp recognizes and skips POD (see perlpod) in both the C and XS language sections, which allows the XS file to contain embedded documentation.
See perlxstut for a tutorial on the whole extension creation process.
Note: For some extensions, Dave Beazley's SWIG system may provide a significantly more convenient mechanism for creating the extension glue code. See <http://www.swig.org/> for more information.
bool_t rpcb_gettime(const char *host, time_t *timep);
From C this function will be called with the following statements.
#include <rpc/rpc.h> bool_t status; time_t timep; status = rpcb_gettime( "localhost", &timep );
If an XSUB is created to offer a direct translation between this function and Perl, then this XSUB will be used from Perl with the following code. The $status and $timep variables will contain the output of the function.
use RPC; $status = rpcb_gettime( "localhost", $timep );
The following XS file shows an XS subroutine, or XSUB, which demonstrates one possible interface to the rpcb_gettime() function. This XSUB represents a direct translation between C and Perl and so preserves the interface even from Perl. This XSUB will be invoked from Perl with the usage shown above. Note that the first three #include statements, for "EXTERN.h", "perl.h", and "XSUB.h", will always be present at the beginning of an XS file. This approach and others will be expanded later in this document. A #define for "PERL_NO_GET_CONTEXT" should be present to fetch the interpreter context more efficiently, see perlguts for details.
#define PERL_NO_GET_CONTEXT #include "EXTERN.h" #include "perl.h" #include "XSUB.h" #include <rpc/rpc.h> MODULE = RPC PACKAGE = RPC bool_t rpcb_gettime(host,timep) char *host time_t &timep OUTPUT: timep
Any extension to Perl, including those containing XSUBs, should have a Perl module to serve as the bootstrap which pulls the extension into Perl. This module will export the extension's functions and variables to the Perl program and will cause the extension's XSUBs to be linked into Perl. The following module will be used for most of the examples in this document and should be used from Perl with the "use" command as shown earlier. Perl modules are explained in more detail later in this document.
package RPC; require Exporter; require DynaLoader; @ISA = qw(Exporter DynaLoader); @EXPORT = qw( rpcb_gettime ); bootstrap RPC; 1;
Throughout this document a variety of interfaces to the rpcb_gettime() XSUB will be explored. The XSUBs will take their parameters in different orders or will take different numbers of parameters. In each case the XSUB is an abstraction between Perl and the real C rpcb_gettime() function, and the XSUB must always ensure that the real rpcb_gettime() function is called with the correct parameters. This abstraction will allow the programmer to create a more Perl-like interface to the C function.
The following XSUB allows a Perl program to access a C library function called sin(). The XSUB will imitate the C function which takes a single argument and returns a single value.
double sin(x) double x
Optionally, one can merge the description of types and the list of argument names, rewriting this as
double sin(double x)
This makes this XSUB look similar to an ANSI C declaration. An optional semicolon is allowed after the argument list, as in
double sin(double x);
Parameters with C pointer types can have different semantic: C functions with similar declarations
bool string_looks_as_a_number(char *s); bool make_char_uppercase(char *c);
are used in absolutely incompatible manner. Parameters to these functions could be described xsubpp like this:
char * s char &c
Both these XS declarations correspond to the "char*" C type, but they have different semantics, see "The & Unary Operator".
It is convenient to think that the indirection operator "*" should be considered as a part of the type and the address operator "&" should be considered part of the variable. See perlxstypemap for more info about handling qualifiers and unary operators in C types.
The function name and the return type must be placed on separate lines and should be flush left-adjusted.
INCORRECT CORRECT double sin(x) double double x sin(x) double x
The rest of the function description may be indented or left-adjusted. The following example shows a function with its body left-adjusted. Most examples in this document will indent the body for better readability.
CORRECT double sin(x) double x
More complicated XSUBs may contain many other sections. Each section of an XSUB starts with the corresponding keyword, such as INIT: or CLEANUP:. However, the first two lines of an XSUB always contain the same data: descriptions of the return type and the names of the function and its parameters. Whatever immediately follows these is considered to be an INPUT: section unless explicitly marked with another keyword. (See "The INPUT: Keyword".)
An XSUB section continues until another section-start keyword is found.
XSUBs refer to their stack arguments with the macro ST(x), where x refers to a position in this XSUB's part of the stack. Position 0 for that function would be known to the XSUB as ST(0). The XSUB's incoming parameters and outgoing return values always begin at ST(0). For many simple cases the xsubpp compiler will generate the code necessary to handle the argument stack by embedding code fragments found in the typemaps. In more complex cases the programmer must supply the code.
If the XSUB has a return type of "void" then the compiler will not declare a RETVAL variable for that function. When using a PPCODE: section no manipulation of the RETVAL variable is required, the section may use direct stack manipulation to place output values on the stack.
If PPCODE: directive is not used, "void" return value should be used only for subroutines which do not return a value, even if CODE: directive is used which sets ST(0) explicitly.
Older versions of this document recommended to use "void" return value in such cases. It was discovered that this could lead to segfaults in cases when XSUB was truly "void". This practice is now deprecated, and may be not supported at some future version. Use the return value "SV *" in such cases. (Currently "xsubpp" contains some heuristic code which tries to disambiguate between "truly-void" and "old-practice-declared-as-void" functions. Hence your code is at mercy of this heuristics unless you use "SV *" as return value.)
void alpha() PPCODE: ST(0) = newSVpv("Hello World",0); sv_2mortal(ST(0)); XSRETURN(1); SV * beta() CODE: RETVAL = newSVpv("Hello World",0); OUTPUT: RETVAL
This is quite useful as it usually improves readability. While this works fine for an "SV *", it's unfortunately not as easy to have "AV *" or "HV *" as a return value. You should be able to write:
AV * array() CODE: RETVAL = newAV(); /* do something with RETVAL */ OUTPUT: RETVAL
But due to an unfixable bug (fixing it would break lots of existing CPAN modules) in the typemap file, the reference count of the "AV *" is not properly decremented. Thus, the above XSUB would leak memory whenever it is being called. The same problem exists for "HV *", "CV *", and "SVREF" (which indicates a scalar reference, not a general "SV *"). In XS code on perls starting with perl 5.16, you can override the typemaps for any of these types with a version that has proper handling of refcounts. In your "TYPEMAP" section, do
AV* T_AVREF_REFCOUNT_FIXED
to get the repaired variant. For backward compatibility with older versions of perl, you can instead decrement the reference count manually when you're returning one of the aforementioned types using "sv_2mortal":
AV * array() CODE: RETVAL = newAV(); sv_2mortal((SV*)RETVAL); /* do something with RETVAL */ OUTPUT: RETVAL
Remember that you don't have to do this for an "SV *". The reference documentation for all core typemaps can be found in perlxstypemap.
The following example will start the XS code and will place all functions in a package named RPC.
MODULE = RPC
MODULE = RPC PACKAGE = RPC [ XS code in package RPC ] MODULE = RPC PACKAGE = RPCB [ XS code in package RPCB ] MODULE = RPC PACKAGE = RPC [ XS code in package RPC ]
The same package name can be used more than once, allowing for non-contiguous code. This is useful if you have a stronger ordering principle than package names.
Although this keyword is optional and in some cases provides redundant information it should always be used. This keyword will ensure that the XSUBs appear in the desired package.
This keyword should follow the PACKAGE keyword when used. If PACKAGE is not used then PREFIX should follow the MODULE keyword.
MODULE = RPC PREFIX = rpc_ MODULE = RPC PACKAGE = RPCB PREFIX = rpcb_
This keyword will normally be used to complement the CODE: keyword. The RETVAL variable is not recognized as an output variable when the CODE: keyword is present. The OUTPUT: keyword is used in this situation to tell the compiler that RETVAL really is an output variable.
The OUTPUT: keyword can also be used to indicate that function parameters are output variables. This may be necessary when a parameter has been modified within the function and the programmer would like the update to be seen by Perl.
bool_t rpcb_gettime(host,timep) char *host time_t &timep OUTPUT: timep
The OUTPUT: keyword will also allow an output parameter to be mapped to a matching piece of code rather than to a typemap.
bool_t rpcb_gettime(host,timep) char *host time_t &timep OUTPUT: timep sv_setnv(ST(1), (double)timep);
xsubpp emits an automatic "SvSETMAGIC()" for all parameters in the OUTPUT section of the XSUB, except RETVAL. This is the usually desired behavior, as it takes care of properly invoking 'set' magic on output parameters (needed for hash or array element parameters that must be created if they didn't exist). If for some reason, this behavior is not desired, the OUTPUT section may contain a "SETMAGIC: DISABLE" line to disable it for the remainder of the parameters in the OUTPUT section. Likewise, "SETMAGIC: ENABLE" can be used to reenable it for the remainder of the OUTPUT section. See perlguts for more details about 'set' magic.
With this keyword present "The RETVAL Variable" is created, and in the generated call to the subroutine this variable is assigned to, but the value of this variable is not going to be used in the auto-generated code.
This keyword makes sense only if "RETVAL" is going to be accessed by the user-supplied code. It is especially useful to make a function interface more Perl-like, especially when the C return value is just an error condition indicator. For example,
NO_OUTPUT int delete_file(char *name) POSTCALL: if (RETVAL != 0) croak("Error %d while deleting file '%s'", RETVAL, name);
Here the generated XS function returns nothing on success, and will die() with a meaningful error message on error.
The following XSUB is for a C function which requires special handling of its parameters. The Perl usage is given first.
$status = rpcb_gettime( "localhost", $timep );
The XSUB follows.
bool_t rpcb_gettime(host,timep) char *host time_t timep CODE: RETVAL = rpcb_gettime( host, &timep ); OUTPUT: timep RETVAL
bool_t rpcb_gettime(host,timep) char *host time_t &timep INIT: printf("# Host is %s\n", host ); OUTPUT: timep
Another use for the INIT: section is to check for preconditions before making a call to the C function:
long long lldiv(a,b) long long a long long b INIT: if (a == 0 && b == 0) XSRETURN_UNDEF; if (b == 0) croak("lldiv: cannot divide by 0");
The following example shows a variation of the rpcb_gettime() function. This function uses the timep variable only as an output variable and does not care about its initial contents.
bool_t rpcb_gettime(host,timep) char *host time_t &timep = NO_INIT OUTPUT: timep
TYPEMAP: <<HERE ... your typemap code here ... HERE
where the "TYPEMAP" keyword must appear in the first column of a new line.
Refer to perlxstypemap for details on writing typemaps.
The following code demonstrates how to supply initialization code for function parameters. The initialization code is eval'ed within double quotes by the compiler before it is added to the output so anything which should be interpreted literally [mainly "$", "@", or "\\"] must be protected with backslashes. The variables $var, $arg, and $type can be used as in typemaps.
bool_t rpcb_gettime(host,timep) char *host = (char *)SvPV_nolen($arg); time_t &timep = 0; OUTPUT: timep
This should not be used to supply default values for parameters. One would normally use this when a function parameter must be processed by another library function before it can be used. Default parameters are covered in the next section.
If the initialization begins with "=", then it is output in the declaration for the input variable, replacing the initialization supplied by the typemap. If the initialization begins with ";" or "+", then it is performed after all of the input variables have been declared. In the ";" case the initialization normally supplied by the typemap is not performed. For the "+" case, the declaration for the variable will include the initialization from the typemap. A global variable, %v, is available for the truly rare case where information from one initialization is needed in another initialization.
Here's a truly obscure example:
bool_t rpcb_gettime(host,timep) time_t &timep; /* \$v{timep}=@{[$v{timep}=$arg]} */ char *host + SvOK($v{timep}) ? SvPV_nolen($arg) : NULL; OUTPUT: timep
The construct "\$v{timep}=@{[$v{timep}=$arg]}" used in the above example has a two-fold purpose: first, when this line is processed by xsubpp, the Perl snippet "$v{timep}=$arg" is evaluated. Second, the text of the evaluated snippet is output into the generated C file (inside a C comment)! During the processing of "char *host" line, $arg will evaluate to ST(0), and $v{timep} will evaluate to ST(1).
To allow the XSUB for rpcb_gettime() to have a default host value the parameters to the XSUB could be rearranged. The XSUB will then call the real rpcb_gettime() function with the parameters in the correct order. This XSUB can be called from Perl with either of the following statements:
$status = rpcb_gettime( $timep, $host ); $status = rpcb_gettime( $timep );
The XSUB will look like the code which follows. A CODE: block is used to call the real rpcb_gettime() function with the parameters in the correct order for that function.
bool_t rpcb_gettime(timep,host="localhost") char *host time_t timep = NO_INIT CODE: RETVAL = rpcb_gettime( host, &timep ); OUTPUT: timep RETVAL
If a variable is declared inside a CODE: section it will follow any typemap code that is emitted for the input parameters. This may result in the declaration ending up after C code, which is C syntax error. Similar errors may happen with an explicit ";"-type or "+"-type initialization of parameters is used (see "Initializing Function Parameters"). Declaring these variables in an INIT: section will not help.
In such cases, to force an additional variable to be declared together with declarations of other variables, place the declaration into a PREINIT: section. The PREINIT: keyword may be used one or more times within an XSUB.
The following examples are equivalent, but if the code is using complex typemaps then the first example is safer.
bool_t rpcb_gettime(timep) time_t timep = NO_INIT PREINIT: char *host = "localhost"; CODE: RETVAL = rpcb_gettime( host, &timep ); OUTPUT: timep RETVAL
For this particular case an INIT: keyword would generate the same C code as the PREINIT: keyword. Another correct, but error-prone example:
bool_t rpcb_gettime(timep) time_t timep = NO_INIT CODE: char *host = "localhost"; RETVAL = rpcb_gettime( host, &timep ); OUTPUT: timep RETVAL
Another way to declare "host" is to use a C block in the CODE: section:
bool_t rpcb_gettime(timep) time_t timep = NO_INIT CODE: { char *host = "localhost"; RETVAL = rpcb_gettime( host, &timep ); } OUTPUT: timep RETVAL
The ability to put additional declarations before the typemap entries are processed is very handy in the cases when typemap conversions manipulate some global state:
MyObject mutate(o) PREINIT: MyState st = global_state; INPUT: MyObject o; CLEANUP: reset_to(global_state, st);
Here we suppose that conversion to "MyObject" in the INPUT: section and from MyObject when processing RETVAL will modify a global variable "global_state". After these conversions are performed, we restore the old value of "global_state" (to avoid memory leaks, for example).
There is another way to trade clarity for compactness: INPUT sections allow declaration of C variables which do not appear in the parameter list of a subroutine. Thus the above code for mutate() can be rewritten as
MyObject mutate(o) MyState st = global_state; MyObject o; CLEANUP: reset_to(global_state, st);
and the code for rpcb_gettime() can be rewritten as
bool_t rpcb_gettime(timep) time_t timep = NO_INIT char *host = "localhost"; C_ARGS: host, &timep OUTPUT: timep RETVAL
To support potentially complex type mappings, if a typemap entry used by an XSUB contains a comment like "/*scope*/" then scoping will be automatically enabled for that XSUB.
To enable scoping:
SCOPE: ENABLE
To disable scoping:
SCOPE: DISABLE
The following example shows how the input parameter "timep" can be evaluated late, after a PREINIT.
bool_t rpcb_gettime(host,timep) char *host PREINIT: time_t tt; INPUT: time_t timep CODE: RETVAL = rpcb_gettime( host, &tt ); timep = tt; OUTPUT: timep RETVAL
The next example shows each input parameter evaluated late.
bool_t rpcb_gettime(host,timep) PREINIT: time_t tt; INPUT: char *host PREINIT: char *h; INPUT: time_t timep CODE: h = host; RETVAL = rpcb_gettime( h, &tt ); timep = tt; OUTPUT: timep RETVAL
Since INPUT sections allow declaration of C variables which do not appear in the parameter list of a subroutine, this may be shortened to:
bool_t rpcb_gettime(host,timep) time_t tt; char *host; char *h = host; time_t timep; CODE: RETVAL = rpcb_gettime( h, &tt ); timep = tt; OUTPUT: timep RETVAL
(We used our knowledge that input conversion for "char *" is a "simple" one, thus "host" is initialized on the declaration line, and our assignment "h = host" is not performed too early. Otherwise one would need to have the assignment "h = host" in a CODE: or INIT: section.)
Parameters preceded by "OUTLIST"/"IN_OUTLIST"/"OUT"/"IN_OUT" keywords are considered to be used by the C subroutine via pointers. "OUTLIST"/"OUT" keywords indicate that the C subroutine does not inspect the memory pointed by this parameter, but will write through this pointer to provide additional return values.
Parameters preceded by "OUTLIST" keyword do not appear in the usage signature of the generated Perl function.
Parameters preceded by "IN_OUTLIST"/"IN_OUT"/"OUT" do appear as parameters to the Perl function. With the exception of "OUT"-parameters, these parameters are converted to the corresponding C type, then pointers to these data are given as arguments to the C function. It is expected that the C function will write through these pointers.
The return list of the generated Perl function consists of the C return value from the function (unless the XSUB is of "void" return type or "The NO_OUTPUT Keyword" was used) followed by all the "OUTLIST" and "IN_OUTLIST" parameters (in the order of appearance). On the return from the XSUB the "IN_OUT"/"OUT" Perl parameter will be modified to have the values written by the C function.
For example, an XSUB
void day_month(OUTLIST day, IN unix_time, OUTLIST month) int day int unix_time int month
should be used from Perl as
my ($day, $month) = day_month(time);
The C signature of the corresponding function should be
void day_month(int *day, int unix_time, int *month);
The "IN"/"OUTLIST"/"IN_OUTLIST"/"IN_OUT"/"OUT" keywords can be mixed with ANSI-style declarations, as in
void day_month(OUTLIST int day, int unix_time, OUTLIST int month)
(here the optional "IN" keyword is omitted).
The "IN_OUT" parameters are identical with parameters introduced with "The & Unary Operator" and put into the "OUTPUT:" section (see "The OUTPUT: Keyword"). The "IN_OUTLIST" parameters are very similar, the only difference being that the value C function writes through the pointer would not modify the Perl parameter, but is put in the output list.
The "OUTLIST"/"OUT" parameter differ from "IN_OUTLIST"/"IN_OUT" parameters only by the initial value of the Perl parameter not being read (and not being given to the C function - which gets some garbage instead). For example, the same C function as above can be interfaced with as
void day_month(OUT int day, int unix_time, OUT int month);
or
void day_month(day, unix_time, month) int &day = NO_INIT int unix_time int &month = NO_INIT OUTPUT: day month
However, the generated Perl function is called in very C-ish style:
my ($day, $month); day_month($day, time, $month);
void dump_chars(char *s, short l) { short n = 0; while (n < l) { printf("s[%d] = \"\\%#03o\"\n", n, (int)s[n]); n++; } } MODULE = x PACKAGE = x void dump_chars(char *s, short length(s))
should be called as "dump_chars($string)".
This directive is supported with ANSI-type function declarations only.
The host parameter for the rpcb_gettime() XSUB can be optional so the ellipsis can be used to indicate that the XSUB will take a variable number of parameters. Perl should be able to call this XSUB with either of the following statements.
$status = rpcb_gettime( $timep, $host ); $status = rpcb_gettime( $timep );
The XS code, with ellipsis, follows.
bool_t rpcb_gettime(timep, ...) time_t timep = NO_INIT PREINIT: char *host = "localhost"; CODE: if( items > 1 ) host = (char *)SvPV_nolen(ST(1)); RETVAL = rpcb_gettime( host, &timep ); OUTPUT: timep RETVAL
For example, suppose that a C function is declared as
symbolic nth_derivative(int n, symbolic function, int flags);
and that the default flags are kept in a global C variable "default_flags". Suppose that you want to create an interface which is called as
$second_deriv = $function->nth_derivative(2);
To do this, declare the XSUB as
symbolic nth_derivative(function, n) symbolic function int n C_ARGS: n, function, default_flags
The actual difference between PPCODE: and CODE: sections is in the initialization of "SP" macro (which stands for the current Perl stack pointer), and in the handling of data on the stack when returning from an XSUB. In CODE: sections SP preserves the value which was on entry to the XSUB: SP is on the function pointer (which follows the last parameter). In PPCODE: sections SP is moved backward to the beginning of the parameter list, which allows "PUSH*()" macros to place output values in the place Perl expects them to be when the XSUB returns back to Perl.
The generated trailer for a CODE: section ensures that the number of return values Perl will see is either 0 or 1 (depending on the "void"ness of the return value of the C function, and heuristics mentioned in "The RETVAL Variable"). The trailer generated for a PPCODE: section is based on the number of return values and on the number of times "SP" was updated by "[X]PUSH*()" macros.
Note that macros ST(i), "XST_m*()" and "XSRETURN*()" work equally well in CODE: sections and PPCODE: sections.
The following XSUB will call the C rpcb_gettime() function and will return its two output values, timep and status, to Perl as a single list.
void rpcb_gettime(host) char *host PREINIT: time_t timep; bool_t status; PPCODE: status = rpcb_gettime( host, &timep ); EXTEND(SP, 2); PUSHs(sv_2mortal(newSViv(status))); PUSHs(sv_2mortal(newSViv(timep)));
Notice that the programmer must supply the C code necessary to have the real rpcb_gettime() function called and to have the return values properly placed on the argument stack.
The "void" return type for this function tells the xsubpp compiler that the RETVAL variable is not needed or used and that it should not be created. In most scenarios the void return type should be used with the PPCODE: directive.
The EXTEND() macro is used to make room on the argument stack for 2 return values. The PPCODE: directive causes the xsubpp compiler to create a stack pointer available as "SP", and it is this pointer which is being used in the EXTEND() macro. The values are then pushed onto the stack with the PUSHs() macro.
Now the rpcb_gettime() function can be used from Perl with the following statement.
($status, $timep) = rpcb_gettime("localhost");
When handling output parameters with a PPCODE section, be sure to handle 'set' magic properly. See perlguts for details about 'set' magic.
$timep = rpcb_gettime( "localhost" );
The following XSUB uses the "SV *" return type as a mnemonic only, and uses a CODE: block to indicate to the compiler that the programmer has supplied all the necessary code. The sv_newmortal() call will initialize the return value to undef, making that the default return value.
SV * rpcb_gettime(host) char * host PREINIT: time_t timep; bool_t x; CODE: ST(0) = sv_newmortal(); if( rpcb_gettime( host, &timep ) ) sv_setnv( ST(0), (double)timep);
The next example demonstrates how one would place an explicit undef in the return value, should the need arise.
SV * rpcb_gettime(host) char * host PREINIT: time_t timep; bool_t x; CODE: if( rpcb_gettime( host, &timep ) ){ ST(0) = sv_newmortal(); sv_setnv( ST(0), (double)timep); } else{ ST(0) = &PL_sv_undef; }
To return an empty list one must use a PPCODE: block and then not push return values on the stack.
void rpcb_gettime(host) char *host PREINIT: time_t timep; PPCODE: if( rpcb_gettime( host, &timep ) ) PUSHs(sv_2mortal(newSViv(timep))); else{ /* Nothing pushed on stack, so an empty * list is implicitly returned. */ }
Some people may be inclined to include an explicit "return" in the above XSUB, rather than letting control fall through to the end. In those situations "XSRETURN_EMPTY" should be used, instead. This will ensure that the XSUB stack is properly adjusted. Consult perlapi for other "XSRETURN" macros.
Since "XSRETURN_*" macros can be used with CODE blocks as well, one can rewrite this example as:
int rpcb_gettime(host) char *host PREINIT: time_t timep; CODE: RETVAL = rpcb_gettime( host, &timep ); if (RETVAL == 0) XSRETURN_UNDEF; OUTPUT: RETVAL
In fact, one can put this check into a POSTCALL: section as well. Together with PREINIT: simplifications, this leads to:
int rpcb_gettime(host) char *host time_t timep; POSTCALL: if (RETVAL == 0) XSRETURN_UNDEF;
REQUIRE: 1.922
See examples in "The NO_OUTPUT Keyword" and "Returning Undef And Empty Lists".
The POSTCALL: block does not make a lot of sense when the C subroutine call is supplied by user by providing either CODE: or PPCODE: section.
This keyword may be used any time after the first MODULE keyword and should appear on a line by itself. The first blank line after the keyword will terminate the code block.
BOOT: # The following message will be printed when the # bootstrap function executes. printf("Hello from the bootstrap!\n");
To enable version checking:
VERSIONCHECK: ENABLE
To disable version checking:
VERSIONCHECK: DISABLE
Note that if the version of the PM module is an NV (a floating point number), it will be stringified with a possible loss of precision (currently chopping to nine decimal places) so that it may not match the version of the XS module anymore. Quoting the $VERSION declaration to make it a string is recommended if long version numbers are used.
Please specify prototyping behavior for Foo.xs (see perlxs manual)
To enable prototypes:
PROTOTYPES: ENABLE
To disable prototypes:
PROTOTYPES: DISABLE
bool_t rpcb_gettime(timep, ...) time_t timep = NO_INIT PROTOTYPE: $;$ PREINIT: char *host = "localhost"; CODE: if( items > 1 ) host = (char *)SvPV_nolen(ST(1)); RETVAL = rpcb_gettime( host, &timep ); OUTPUT: timep RETVAL
If the prototypes are enabled, you can disable it locally for a given XSUB as in the following example:
void rpcb_gettime_noproto() PROTOTYPE: DISABLE ...
The following example will create aliases "FOO::gettime()" and "BAR::getit()" for this function.
bool_t rpcb_gettime(host,timep) char *host time_t &timep ALIAS: FOO::gettime = 1 BAR::getit = 2 INIT: printf("# ix = %d\n", ix ); OUTPUT: timep
If any function has the OVERLOAD: keyword, several additional lines will be defined in the c file generated by xsubpp in order to register with the overload magic.
Since blessed objects are actually stored as RV's, it is useful to use the typemap features to preprocess parameters and extract the actual SV stored within the blessed RV. See the sample for T_PTROBJ_SPECIAL below.
To use the OVERLOAD: keyword, create an XS function which takes three input parameters (or use the C-style '...' definition) like this:
SV * cmp (lobj, robj, swap) My_Module_obj lobj My_Module_obj robj IV swap OVERLOAD: cmp <=> { /* function defined here */}
In this case, the function will overload both of the three way comparison operators. For all overload operations using non-alpha characters, you must type the parameter without quoting, separating multiple overloads with whitespace. Note that "" (the stringify overload) should be entered as \"\" (i.e. escaped).
Since, as mentioned above, bitwise operators may take extra arguments, you may want to use something like "(lobj, robj, swap, ...)" (with literal "...") as your parameter list.
MODULE = RPC PACKAGE = RPC FALLBACK: TRUE ...
where FALLBACK can take any of the three values TRUE, FALSE, or UNDEF. If you do not set any FALLBACK value when using OVERLOAD, it defaults to UNDEF. FALLBACK is not used except when one or more functions using OVERLOAD have been defined. Please see "fallback" in overload for more details.
For example, if you have 4 C functions multiply(), divide(), add(), subtract() all having the signature:
symbolic f(symbolic, symbolic);
you can make them all to use the same XSUB using this:
symbolic interface_s_ss(arg1, arg2) symbolic arg1 symbolic arg2 INTERFACE: multiply divide add subtract
(This is the complete XSUB code for 4 Perl functions!) Four generated Perl function share names with corresponding C functions.
The advantage of this approach comparing to ALIAS: keyword is that there is no need to code a switch statement, each Perl function (which shares the same XSUB) knows which C function it should call. Additionally, one can attach an extra function remainder() at runtime by using
CV *mycv = newXSproto("Symbolic::remainder", XS_Symbolic_interface_s_ss, __FILE__, "$$"); XSINTERFACE_FUNC_SET(mycv, remainder);
say, from another XSUB. (This example supposes that there was no INTERFACE_MACRO: section, otherwise one needs to use something else instead of "XSINTERFACE_FUNC_SET", see the next section.)
The default value is "XSINTERFACE_FUNC" and "XSINTERFACE_FUNC_SET". An INTERFACE keyword with an empty list of functions can be omitted if INTERFACE_MACRO keyword is used.
Suppose that in the previous example functions pointers for multiply(), divide(), add(), subtract() are kept in a global C array "fp[]" with offsets being "multiply_off", "divide_off", "add_off", "subtract_off". Then one can use
#define XSINTERFACE_FUNC_BYOFFSET(ret,cv,f) \ ((XSINTERFACE_CVT_ANON(ret))fp[CvXSUBANY(cv).any_i32]) #define XSINTERFACE_FUNC_BYOFFSET_set(cv,f) \ CvXSUBANY(cv).any_i32 = CAT2( f, _off )
in C section,
symbolic interface_s_ss(arg1, arg2) symbolic arg1 symbolic arg2 INTERFACE_MACRO: XSINTERFACE_FUNC_BYOFFSET XSINTERFACE_FUNC_BYOFFSET_set INTERFACE: multiply divide add subtract
in XSUB section.
The file Rpcb1.xsh contains our "rpcb_gettime()" function:
bool_t rpcb_gettime(host,timep) char *host time_t &timep OUTPUT: timep
The XS module can use INCLUDE: to pull that file into it.
INCLUDE: Rpcb1.xsh
If the parameters to the INCLUDE: keyword are followed by a pipe ("|") then the compiler will interpret the parameters as a command. This feature is mildly deprecated in favour of the "INCLUDE_COMMAND:" directive, as documented below.
INCLUDE: cat Rpcb1.xsh |
Do not use this to run perl: "INCLUDE: perl |" will run the perl that happens to be the first in your path and not necessarily the same perl that is used to run "xsubpp". See "The INCLUDE_COMMAND: Keyword".
INCLUDE_COMMAND: cat Rpcb1.xsh INCLUDE_COMMAND: $^X -e ...
A CASE: might switch via a parameter of the XSUB, via the "ix" ALIAS: variable (see "The ALIAS: Keyword"), or maybe via the "items" variable (see "Variable-length Parameter Lists"). The last CASE: becomes the default case if it is not associated with a conditional. The following example shows CASE switched via "ix" with a function "rpcb_gettime()" having an alias "x_gettime()". When the function is called as "rpcb_gettime()" its parameters are the usual "(char *host, time_t *timep)", but when the function is called as "x_gettime()" its parameters are reversed, "(time_t *timep, char *host)".
long rpcb_gettime(a,b) CASE: ix == 1 ALIAS: x_gettime = 1 INPUT: # 'a' is timep, 'b' is host char *b time_t a = NO_INIT CODE: RETVAL = rpcb_gettime( b, &a ); OUTPUT: a RETVAL CASE: # 'a' is host, 'b' is timep char *a time_t &b = NO_INIT OUTPUT: b RETVAL
That function can be called with either of the following statements. Note the different argument lists.
$status = rpcb_gettime( $host, $timep ); $status = x_gettime( $timep, $host );
EXPORT_XSUB_SYMBOLS: ENABLE
in your XS code, the XSUBs following this line will not be declared "static". You can later disable this with
EXPORT_XSUB_SYMBOLS: DISABLE
which, again, is the default that you should probably never change. You cannot use this keyword on versions of perl before 5.16 to make XSUBs "static".
This is useful to avoid a CODE: block for a C function which takes a parameter by reference. Typically, the parameter should be not a pointer type (an "int" or "long" but not an "int*" or "long*").
The following XSUB will generate incorrect C code. The xsubpp compiler will turn this into code which calls "rpcb_gettime()" with parameters "(char *host, time_t timep)", but the real "rpcb_gettime()" wants the "timep" parameter to be of type "time_t*" rather than "time_t".
bool_t rpcb_gettime(host,timep) char *host time_t timep OUTPUT: timep
That problem is corrected by using the "&" operator. The xsubpp compiler will now turn this into code which calls "rpcb_gettime()" correctly with parameters "(char *host, time_t *timep)". It does this by carrying the "&" through, so the function call looks like "rpcb_gettime(host, &timep)".
bool_t rpcb_gettime(host,timep) char *host time_t &timep OUTPUT: timep
Comments can be added to XSUBs by placing a "#" as the first non-whitespace of a line.  The simplest way to prevent this is to put whitespace in front of the "#".
If you use preprocessor directives to choose one of two versions of a function, use
#if ... version1 #else /* ... version2 */ #endif
and not
#if ... version1 #endif #if ... version2 #endif
because otherwise xsubpp will believe that you made a duplicate definition of the function. Also, put a blank line before the #else/#endif so it will not be seen as part of the function body.
If the return type of the XSUB includes "static", the method is considered to be a static method. It will call the C++ function using the class::method() syntax. If the method is not static the function will be called using the THIS->method() syntax.
The next examples will use the following C++ class.
class color { public: color(); ~color(); int blue(); void set_blue( int ); private: int c_blue; };
The XSUBs for the blue() and set_blue() methods are defined with the class name but the parameter for the object (THIS, or "self") is implicit and is not listed.
int color::blue() void color::set_blue( val ) int val
Both Perl functions will expect an object as the first parameter. In the generated C++ code the object is called "THIS", and the method call will be performed on this object. So in the C++ code the blue() and set_blue() methods will be called as this:
RETVAL = THIS->blue(); THIS->set_blue( val );
You could also write a single get/set method using an optional argument:
int color::blue( val = NO_INIT ) int val PROTOTYPE $;$ CODE: if (items > 1) THIS->set_blue( val ); RETVAL = THIS->blue(); OUTPUT: RETVAL
If the function's name is DESTROY then the C++ "delete" function will be called and "THIS" will be given as its parameter. The generated C++ code for
void color::DESTROY()
will look like this:
color *THIS = ...; // Initialized as in typemap delete THIS;
If the function's name is new then the C++ "new" function will be called to create a dynamic C++ object. The XSUB will expect the class name, which will be kept in a variable called "CLASS", to be given as the first argument.
color * color::new()
The generated C++ code will call "new".
RETVAL = new color();
The following is an example of a typemap that could be used for this C++ example.
TYPEMAP color * O_OBJECT OUTPUT # The Perl object is blessed into 'CLASS', which should be a # char* having the name of the package for the blessing. O_OBJECT sv_setref_pv( $arg, CLASS, (void*)$var ); INPUT O_OBJECT if( sv_isobject($arg) && (SvTYPE(SvRV($arg)) == SVt_PVMG) ) $var = ($type)SvIV((SV*)SvRV( $arg )); else{ warn("${Package}::$func_name() -- " . "$var is not a blessed SV reference"); XSRETURN_UNDEF; }
Identify the C functions with input/output or output parameters. The XSUBs for these functions may be able to return lists to Perl.
Identify the C functions which use some inband info as an indication of failure. They may be candidates to return undef or an empty list in case of failure. If the failure may be detected without a call to the C function, you may want to use an INIT: section to report the failure. For failures detectable after the C function returns one may want to use a POSTCALL: section to process the failure. In more complicated cases use CODE: or PPCODE: sections.
If many functions use the same failure indication based on the return value, you may want to create a special typedef to handle this situation. Put
typedef int negative_is_failure;
near the beginning of XS file, and create an OUTPUT typemap entry for "negative_is_failure" which converts negative values to "undef", or maybe croak()s. After this the return value of type "negative_is_failure" will create more Perl-like interface.
Identify which values are used by only the C and XSUB functions themselves, say, when a parameter to a function should be a contents of a global variable. If Perl does not need to access the contents of the value then it may not be necessary to provide a translation for that value from C to Perl.
Identify the pointers in the C function parameter lists and return values. Some pointers may be used to implement input/output or output parameters, they can be handled in XS with the "&" unary operator, and, possibly, using the NO_INIT keyword.  When the semantic is clear, it is advisable to put the translation into a typemap file.
Identify the structures used by the C functions. In many cases it may be helpful to use the T_PTROBJ typemap for these structures so they can be manipulated by Perl as blessed objects. (This is handled automatically by "h2xs -x".)
If the same C type is used in several different contexts which require different translations, "typedef" several new types mapped to this C type, and create separate typemap entries for these new types. Use these types in declarations of return type and parameters to XSUBs.
The following XS code shows the getnetconfigent() function which is used with ONC+ TIRPC. The getnetconfigent() function will return a pointer to a C structure and has the C prototype shown below. The example will demonstrate how the C pointer will become a Perl reference. Perl will consider this reference to be a pointer to a blessed object and will attempt to call a destructor for the object. A destructor will be provided in the XS source to free the memory used by getnetconfigent(). Destructors in XS can be created by specifying an XSUB function whose name ends with the word DESTROY. XS destructors can be used to free memory which may have been malloc'd by another XSUB.
struct netconfig *getnetconfigent(const char *netid);
A "typedef" will be created for "struct netconfig". The Perl object will be blessed in a class matching the name of the C type, with the tag "Ptr" appended, and the name should not have embedded spaces if it will be a Perl package name. The destructor will be placed in a class corresponding to the class of the object and the PREFIX keyword will be used to trim the name to the word DESTROY as Perl will expect.
typedef struct netconfig Netconfig; MODULE = RPC PACKAGE = RPC Netconfig * getnetconfigent(netid) char *netid MODULE = RPC PACKAGE = NetconfigPtr PREFIX = rpcb_ void rpcb_DESTROY(netconf) Netconfig *netconf CODE: printf("Now in NetconfigPtr::DESTROY\n"); free( netconf );
This example requires the following typemap entry. Consult perlxstypemap for more information about adding new typemaps for an extension.
TYPEMAP Netconfig * T_PTROBJ
This example will be used with the following Perl statements.
use RPC; $netconf = getnetconfigent("udp");
When Perl destroys the object referenced by $netconf it will send the object to the supplied XSUB DESTROY function. Perl cannot determine, and does not care, that this object is a C struct and not a Perl object. In this sense, there is no difference between the object created by the getnetconfigent() XSUB and an object created by a normal Perl subroutine.
Although primarily designed for use with multi-threaded Perl, the macros have been designed so that they will work with non-threaded Perl as well.
It is therefore strongly recommended that these macros be used by all XS modules that make use of static data.
The easiest way to get a template set of macros to use is by specifying the "-g" ("--global") option with h2xs (see h2xs).
Below is an example module that makes use of the macros.
#define PERL_NO_GET_CONTEXT #include "EXTERN.h" #include "perl.h" #include "XSUB.h" /* Global Data */ #define MY_CXT_KEY "BlindMice::_guts" XS_VERSION typedef struct { int count; char name[3][100]; } my_cxt_t; START_MY_CXT MODULE = BlindMice PACKAGE = BlindMice BOOT: { MY_CXT_INIT; MY_CXT.count = 0; strcpy(MY_CXT.name[0], "None"); strcpy(MY_CXT.name[1], "None"); strcpy(MY_CXT.name[2], "None"); } int newMouse(char * name) PREINIT: dMY_CXT; CODE: if (MY_CXT.count >= 3) { warn("Already have 3 blind mice"); RETVAL = 0; } else { RETVAL = ++ MY_CXT.count; strcpy(MY_CXT.name[MY_CXT.count - 1], name); } OUTPUT: RETVAL char * get_mouse_name(index) int index PREINIT: dMY_CXT; CODE: if (index > MY_CXT.count) croak("There are only 3 blind mice."); else RETVAL = MY_CXT.name[index - 1]; OUTPUT: RETVAL void CLONE(...) CODE: MY_CXT_CLONE;
MY_CXT REFERENCE
#define MY_CXT_KEY "MyModule::_guts" XS_VERSION
Declare a typedef named "my_cxt_t" that is a structure that contains all the data that needs to be interpreter-local.
typedef struct { int some_value; } my_cxt_t;
It must be called exactly once, typically in a BOOT: section. If you are maintaining multiple interpreters, it should be called once in each interpreter instance, except for interpreters cloned from existing ones. (But see "MY_CXT_CLONE" below.)
typedef struct { int index; } my_cxt_t;
then use this to access the "index" member
dMY_CXT; MY_CXT.index = 2;
void sub1() { dMY_CXT; MY_CXT.index = 1; sub2(aMY_CXT); } void sub2(pMY_CXT) { MY_CXT.index = 2; }
Analogously to "pTHX", there are equivalent forms for when the macro is the first or last in multiple arguments, where an underscore represents a comma, i.e. "_aMY_CXT", "aMY_CXT_", "_pMY_CXT" and "pMY_CXT_".
Note that these macros will only work together within the same source file; that is, a dMY_CTX in one source file will access a different structure than a dMY_CTX in another source file.
This wrapping happens always when compiling Perl core source (PERL_CORE is defined) or the Perl core extensions (PERL_EXT is defined). When compiling XS code outside of the Perl core, the wrapping does not take place before Perl 5.28. Starting in that release you can
#define PERL_REENTRANT
in your code to enable the wrapping. It is advisable to do so if you are using such functions, as intermixing the "_r"-forms (as Perl compiled for multithreaded operation will do) and the "_r"-less forms is neither well-defined (inconsistent results, data corruption, or even crashes become more likely), nor is it very portable. Unfortunately, not all systems have all the "_r" forms, but using this "#define" gives you whatever protection that Perl is aware is available on each system.
#define PERL_NO_GET_CONTEXT #include "EXTERN.h" #include "perl.h" #include "XSUB.h" #include <rpc/rpc.h> typedef struct netconfig Netconfig; MODULE = RPC PACKAGE = RPC SV * rpcb_gettime(host="localhost") char *host PREINIT: time_t timep; CODE: ST(0) = sv_newmortal(); if( rpcb_gettime( host, &timep ) ) sv_setnv( ST(0), (double)timep ); Netconfig * getnetconfigent(netid="udp") char *netid MODULE = RPC PACKAGE = NetconfigPtr PREFIX = rpcb_ void rpcb_DESTROY(netconf) Netconfig *netconf CODE: printf("NetconfigPtr::DESTROY\n"); free( netconf );
File "typemap": Custom typemap for RPC.xs. (cf. perlxstypemap)
TYPEMAP Netconfig * T_PTROBJ
File "RPC.pm": Perl module for the RPC extension.
package RPC; require Exporter; require DynaLoader; @ISA = qw(Exporter DynaLoader); @EXPORT = qw(rpcb_gettime getnetconfigent); bootstrap RPC; 1;
File "rpctest.pl": Perl test program for the RPC extension.
use RPC; $netconf = getnetconfigent(); $a = rpcb_gettime(); print "time = $a\n"; print "netconf = $netconf\n"; $netconf = getnetconfigent("tcp"); $a = rpcb_gettime("poplar"); print "time = $a\n"; print "netconf = $netconf\n";
Some modules have an event loop, waiting for user-input. It is highly unlikely that two such modules would work adequately together in a single Perl application.
In general, the perl interpreter views itself as the center of the universe as far as the Perl program goes. XS code is viewed as a help-mate, to accomplish things that perl doesn't do, or doesn't do fast enough, but always subservient to perl. The closer XS code adheres to this model, the less likely conflicts will occur.
One area where there has been conflict is in regards to C locales. (See perllocale.) perl, with one exception and unless told otherwise, sets up the underlying locale the program is running in to the locale passed into it from the environment. This is an important difference from a generic C language program, where the underlying locale is the "C" locale unless the program changes it. As of v5.20, this underlying locale is completely hidden from pure Perl code outside the lexical scope of "use locale" except for a couple of function calls in the POSIX module which of necessity use it. But the underlying locale, with that one exception is exposed to XS code, affecting all C library routines whose behavior is locale-dependent. Your XS code better not assume that the underlying locale is "C". The exception is the "LC_NUMERIC" locale category, and the reason it is an exception is that experience has shown that it can be problematic for XS code, whereas we have not had reports of problems with the other locale categories. And the reason for this one category being problematic is that the character used as a decimal point can vary. Many European languages use a comma, whereas English, and hence Perl are expecting a dot (U+002E: FULL STOP). Many modules can handle only the radix character being a dot, and so perl attempts to make it so. Up through Perl v5.20, the attempt was merely to set "LC_NUMERIC" upon startup to the "C" locale. Any setlocale() otherwise would change it; this caused some failures. Therefore, starting in v5.22, perl tries to keep "LC_NUMERIC" always set to "C" for XS code.
To summarize, here's what to expect and how to handle locales in XS code:
The current locale is exposed to XS code except possibly "LC_NUMERIC" (explained in the next paragraph). There have not been reports of problems with the other categories. Perl initializes things on start-up so that the current locale is the one which is indicated by the user's environment in effect at that time. See "ENVIRONMENT" in perllocale.
However, up through v5.20, Perl initialized things on start-up so that "LC_NUMERIC" was set to the "C" locale. But if any code anywhere changed it, it would stay changed. This means that your module can't count on "LC_NUMERIC" being something in particular, and you can't expect floating point numbers (including version strings) to have dots in them. If you don't allow for a non-dot, your code could break if anyone anywhere changed the locale. For this reason, v5.22 changed the behavior so that Perl tries to keep "LC_NUMERIC" in the "C" locale except around the operations internally where it should be something else. Misbehaving XS code will always be able to change the locale anyway, but the most common instance of this is checked for and handled.
But, starting with Perl v5.28, locales are thread-safe on platforms that support this functionality. Windows has this starting with Visual Studio 2005. Many other modern platforms support the thread-safe POSIX 2008 functions. The C "#define" "USE_THREAD_SAFE_LOCALE" will be defined iff this build is using these. From Perl-space, the read-only variable "${SAFE_LOCALES}" is 1 if either the build is not threaded, or if "USE_THREAD_SAFE_LOCALE" is defined; otherwise it is 0.
The way this works under-the-hood is that every thread has a choice of using a locale specific to it (this is the Windows and POSIX 2008 functionality), or the global locale that is accessible to all threads (this is the functionality that has always been there). The implementations for Windows and POSIX are completely different. On Windows, the runtime can be set up so that the standard setlocale(3) function either only knows about the global locale or the locale for this thread. On POSIX, "setlocale" always deals with the global locale, and other functions have been created to handle per-thread locales. Perl makes this transparent to perl-space code. It continues to use "POSIX::setlocale()", and the interpreter translates that into the per-thread functions.
All other locale-senstive functions automatically use the per-thread locale, if that is turned on, and failing that, the global locale. Thus calls to "setlocale" are ineffective on POSIX systems for the current thread if that thread is using a per-thread locale. If perl is compiled for single-thread operation, it does not use the per-thread functions, so "setlocale" does work as expected.
If you have loaded the "POSIX" module you can use the methods given in perlcall to call "POSIX::setlocale" to safely change or query the locale (on systems where it is safe to do so), or you can use the new 5.28 function "Perl_setlocale" in perlapi instead, which is a drop-in replacement for the system setlocale(3), and handles single-threaded and multi-threaded applications transparently.
There are some locale-related library calls that still aren't thread-safe because they return data in a buffer global to all threads. In the past, these didn't matter as locales weren't thread-safe at all. But now you have to be aware of them in case your module is called in a multi-threaded application. The known ones are
asctime() ctime() gcvt() [POSIX.1-2001 only (function removed in POSIX.1-2008)] getdate() wcrtomb() if its final argument is NULL wcsrtombs() if its final argument is NULL wcstombs() wctomb()
Some of these shouldn't really be called in a Perl application, and for others there are thread-safe versions of these already implemented:
asctime_r() ctime_r() Perl_langinfo()
The "_r" forms are automatically used, starting in Perl 5.28, if you compile your code, with
#define PERL_REENTRANT
See also "Perl_langinfo" in perlapi. You can use the methods given in perlcall, to get the best available locale-safe versions of these
POSIX::localeconv() POSIX::wcstombs() POSIX::wctomb()
And note, that some items returned by "Localeconv" are available through "Perl_langinfo" in perlapi.
The others shouldn't be used in a threaded application.
Some modules may call a non-perl library that is locale-aware. This is fine as long as it doesn't try to query or change the locale using the system "setlocale". But if these do call the system "setlocale", those calls may be ineffective. Instead, "Perl_setlocale" works in all circumstances. Plain setlocale is ineffective on multi-threaded POSIX 2008 systems. It operates only on the global locale, whereas each thread has its own locale, paying no attention to the global one. Since converting these non-Perl libraries to "Perl_setlocale" is out of the question, there is a new function in v5.28 "switch_to_global_locale" that will switch the thread it is called from so that any system "setlocale" calls will have their desired effect. The function "sync_locale" must be called before returning to perl.
This thread can change the locale all it wants and it won't affect any other thread, except any that also have been switched to the global locale. This means that a multi-threaded application can have a single thread using an alien library without a problem; but no more than a single thread can be so-occupied. Bad results likely will happen.
In perls without multi-thread locale support, some alien libraries, such as "Gtk" change locales. This can cause problems for the Perl core and other modules. For these, before control is returned to perl, starting in v5.20.1, calling the function sync_locale() from XS should be sufficient to avoid most of these problems. Prior to this, you need a pure Perl statement that does this:
POSIX::setlocale(LC_ALL, POSIX::setlocale(LC_ALL));
or use the methods given in perlcall.
Maintained since 1996 by The Perl Porters<EMAIL_ADDRESS>| 2019-10-21 | perl v5.30.3 |


The Goodness of Beans
lima beans
Also known as butter beans.
navy beans
Also known as haricot beans, it is one of several types of white beans, including lima beans and cannellini beans.
pinto beans
The most popular bean in Northern Mexico and Southwestern United States, according to Wikipedia.
kidney beans
One of two types of red beans. The other is the smaller adzuki bean, not featured here.
garbanzo beans
Also known as chickpeas. Chana Masala is a staple Indian chickpea dish.
black beans
Also known as black turtle beans; it is popular in Latin America. In Asia, black soya beans are also called black beans.
lentils
Lentils come in several colors, including orange, green and brown. A staple of Indian cuisine.
soya beans
Also known as soybeans, its nutritional profile is slightly different from the other beans. Eat it whole for optimum nutrition.
Hover your mouse over the images for more information.
Data: whfoods.org
Vitamin B1 thiamine
Vitamin B2 riboflavin
Vitamin B3 niacin
Vitamin B5 pantothenic acid
Vitamin B6 pyridoxine
Vitamin B9 folic acid
Vitamin C
Vitamin E
Vitamin K1 phylloquinone
Zinc
Iron
Copper
Magnesium
Potassium
Calcium
Phosphorus
Manganese
Selenium
Omega-3 Fatty Acids


/* //TODO: rename socket.etc. // Right now, it replaces the color layer on top of each layer. // It should, instead, clear the previous layer and add a new one each time. // Also, second problem is it has to send some kind of message to server inorder to retrieve data. -> and use localhost:3000/test1.html to see all messages sent via Socket IO. FILES required by this html: - data.json (for now - will fetch via HTTP later) - border_data.js (containing coordinate for library borders) */


Turn node's process.version into something useful.
var nodeVersion = require('parse-node-version')(process.version);
console.log(
nodeVersion.major,
nodeVersion.minor,
nodeVersion.patch,
nodeVersion.pre,
nodeVersion.build
);
Takes a node version string (usually process.version
) and returns an object with the major
/minor
/patch
(which will all be numbers) and pre
/build
keys (which will always be a string). If the version doesn't contain any pre-release or build information, the properties will be returned as empty string.
MIT


| Año Nuevo |
Every Spanish speaking countries |
January 1st/Celebration of the beginning of the year. Fireworks, etc. |
| Carnival |
Most Spanish speaking countries |
Usually ends on the day before Ash Wednesday/A celebration before fasting associated with Lent. Parades, costumes, dances, Carnival Queen elections, and fireworks |
| Les Fogueres de Sant Joan |
Spain only |
June 19th to 24th/Fireworks, parties, big bonfires |
| Innaculada Concepción |
Spain Only |
December 8th/ Feast celebrating the birth of Mary, the mother of Jesus Christ. |
| La siesta |
Every Spanish speaking country |
Mid-afternoon nap/ Not as popular from modern changes, but still exists. |
| Cinco de Mayo |
Mexico |
May 5th; a holiday that celebrates the date of the Mexican army’s 1862 victory over France at the Battle of Puebla during the Franco-Mexican War. |
| Día de Muertos |
Mexico |
Octobber 31-November 2; The multi-day holiday focuses on gatherings of family and friends to pray for and remember friends and family members who have died, and help support their spiritual journey. |


People all of over the world likes to play video games and some people struggle while gaming. People find gaming entertaining and informative. But playing a lot of video games has its pros and cons,people through all ages have probably experienced these factors.
★ ★ ★ ★ ☆ 4.0 stars85% of people are addicted to gaming once you are addicted you can't stop and it's kinda like a habit.
It's unhealthy for the brain.
Can cause people to become aggressive to certain things.
You can become a better puzzle solver .
Also become more creative.
A stronger brain growth (depends if the games has strategy).


logo copy
Created with Sketch Beta.
Chowdown
Keto Quesadillas
Bear Lasagna
Beef Kofta
Blueberry Cobbler
Buffalo Wings
Bunty's Naan
Gordon Ramsay Squash Curry
El Oso Meatloaf
Coconut Curry
Cottage Pie
Enchilada Bowl
Bang Bang Shrimp
Honey Sriracha Chicken Wings
Keto Fried Chicken
A quick Conversion Guide
Keto Taquitos
KFC Style Chicken
Lubia Polo Meatballs
Meatballs (Delish)
Parmesan Chicken
Peanut Butter Chocos
Sweet Chili Sticky Asian Chicken Wings
Peri-Peri Chicken With Pepper And Tomato Cauliflower rice
Spicy Ramen Bowl
Sweet & Sour Pork
Zucchini Bread
Updates whenever new recipes tested. Feel free to send a recipe for me to try.


Programming Assignment 3 - Transformations
Oops ... your browser doesn't support the HTML5 canvas element


Written by: Brian Boyle
Transcribed by: Samantha Stein
[Scene: Monica and Chandlers apartment, everyone except Ross is decorating the tree.]
Chandler: Let me ask you, why is everybody using these tiny lights nowadays? I remember when people used to use big lights.
Rachel: Thats a good story, Grandpa.
(Ross enters)
Ross: Hey
All: Hey
Ross: Wow, Monicas letting other people help decorate her tree! Did someone get her drunk again or?
Monica: Having a perfectly decorated tree is not what Christmas is about. Its about being with the people that you love.
Phoebe: That is nice and were done. TADA!
(Her side of the tree looks a complete mess)
Chandler: I dunno what it is, it just doesnt quite feel like Christmas to me.
Monica: Oh, here.
(She turns the tree around so that her side, which is perfectly decorated, is showing)
Chandler: See now it feels like Christmas!
Opening Credits
[Scene: Central Perk, everyone except Phoebe and Joey are there.]
Ross: and thats the story of the dreidle. Now, some people trace the Christmas tree back to the Egyptians, who used to bring green palm branches into their huts on the shortest day of the year, symbolising lifes triumph over death. And that was like 4000 years ago.
Rachel: So, pretty much around the same time that you started telling this story.

Chandler: Hey Joe whats up?
Joey: I had to get out of the apartment. Janine is like stretching all over the place. Yknow, everywhere I look shes like (He imitates her stretching)
Chandler: I can see why thats hard to resist.
Joey: I like her so much!
Monica: Aw, Im sorry sweetie that she doesnt feel the same way.
Joey: I know. And shes so sweet. I just wanna feed her grapes and brush her hair.
Chandler: You are aware that shes not a monkey, right?
Ross: I am so over Janine. I mean, yeah, at first I thought she was hot, but now shes like OLD NEWS!
(Janine enters)
Janine: Hey guys!
Ross: Hi Janine!
Janine: I just got a call to be a dancer on a television special for New Years Eve. Its called some sort of Dickn Rockn Dickie Eve.
Monica: Hold it!
Janine: Yeah, thats what I said.
Monica: Oh my God! We love that show! I mean Ross and I have been watching it since I can remember!
 (He kisses her on the cheek)
Janine: Well Im gonna be on it this year. Im gonna be one of the party people.
 Those guys rock the most!
Janine: Well they said I should bring someone. (To Joey) Do you wanna be my dance partner?
Joey: Totally! I would love to spend New Years with you.
Janine: Well actually theyre taping tomorrow. I dont really understand why.
Ross: Oh, well you see how it works is, the part with Dick Clark in Times Square is actually live, but they tape some of the party stuff ahead of time. Yeah, not a lot of people know that.
Janine: Yeah well, do you guys wanna come too?

Monica: We are there!
(Rachel laughs)
Chandler: What, what are you laughing at?
Rachel: Well, I used to date him, but youre still going out with her!
(Gunther brings Janine a coffee)
Janine: Thanks. (To Monica and Ross) Great so we can all go together! I gotta run. Catch you later!
(Janine leaves)
All: Bye!
Ross: Bye Janine!
Joey: Did she just ask me out on a date?
Chandler: I dont think so.
Monica: What are you talking about? She just invited him to the biggest party of the millennium!
Rachel: Yeah, but she also invited you and Ross. Yeah, honey, Im sorry, but I dont think that was a romantic thing.
Joey: Oh. Maybe. But hey I know how I can find out. Were going to a New Years Eve party, right? So at midnight, I can kiss her. And if she kisses me back, great! Yknow?  I can say It wasnt me, it was New Years!
Rachel: Well, thats a lot better than Ross trying to kiss me in High School, and saying that he did it because he needed chapstick.
Ross: It was a dry day.
Monica: We are going to Dick Clarks New Years Rocking Eve!
Ross: Oh my God!
Monica: Oh my God!
Chandler: (To Rachel) Oh my God!
[Scene: The Set, Joey, Janine, Ross and Monica are walking in.]
Joey: OK, listen Ive been on sets before, so let me give you a little advice, alright? Its a show, but were just dancing, OK? Its no big deal. The important thing to remember stay cool.
Ross: Got it!
(They get to the main stage)
Ross: Oh my God its just like I dreamed it!
Director: OK, everyone gather up.
(Monica and Ross push to the front)
Monica and Ross: Scuse us
Director: Heres whats gonna happen.  Any questions?
Ross: Yeah, I have a question. When is this gonna air?
(He and Monica laugh)
Director: Uh, yeah.
Joey: Ross! So when is it gonna air?
[Scene: Monica and Chandlers apartment, Chandler is there. Phoebe and Rachel enter.]

Chandler: I can save you time ladies, Im right here.
Phoebe: Yeah, Chandler why dont you take a walk? This doesnt concern you.
Rachel: We are looking for our Christmas presents from Monica.
Chandler: What? Thats terrible!
Phoebe: No-no, we do it every year!
Chandler: Oh well, that makes it not terrible.
Phoebe: No, yeah, we never find them! Shes always best at us that wily minx.
Rachel: Dont worry, were just gonna search here for an hour, them were gonna go over to Joeys and search, OK?
Chandler: No not okay, you cant look for Monicas presents!
Phoebe: But we have to!

Phoebe: Well then, you should look with us.
Chandler: Why?
Rachel: Chandler, arent you worried about what to get Monica for Christmas?
Chandler: No, I have a great idea for a present for her.
Phoebe: Oh, thats it? (Mimics Chandler) A great idea!
Rachel: Chandler, thats not enough.  And youve just gotten her one great present? I mean thats just gonna make her feel bad. Why would you do that to her Chandler? Why? Why?
Chandler: If I help, we can find em faster!
Rachel: Thats right!
(Phoebe looks under the couch)
Phoebe: Ooh ooh, we have a live one!
Rachel: Oh, its a Macys bag!
(Phoebe tips it upside down, and a shoe falls out)
Phoebe: Ooh, whos it for?
Rachel: (Reading) Dear losers, do you really think Id hide presents under the couch? P.S. Chandler, I knew theyd break you.
Phoebe: Uh-oh. She may be onto us.
Rachel: We are so gonna find them this year.
Chandler: Yknow when you guys said you were gonna go across the hall and look, you dont, you dont do that every year do you?
Rachel: Yeah.

Phoebe and Rachel: No, we never do that
(They turn away.)
Chandler: Because thats where Joey gave me some stuff to store that Ive never seen before in my life! Okay, that did not just happen! (He does a weird clicky motion with his fingers, that kinda hard to describe.)
[Scene: The Set, everyone is dancing.]
Monica: Okay, here comes another camera.
Ross: Right. No biggie. Stay loose.
(As the camera passes by, they start to dance really rigid, but the camera is facing the other way.)
Ross: Why do they keep doing that?
Monica: If we wanna get on camera, I think we have to get up on one of those platforms. Theyve been taping those people up there all day.
Ross: Right.
(They move towards a platform, dancing really strangely as they go)
Ross: Hey, whatd you guys do to get up on there?
Girl: We learned how to dance.
Monica: Oh yeah? Well when you learned how to dance did you forget how to put on underpants?
Ross: Yeah!
(Camera pans to Joey and Janine)
Janine: Hey! Youre a good dancer!
Joey: Really?
Janine: Yeah, well youd be better if you just loosened your hips a little.
Joey: What do you mean?
Janine: Like this.
(She pulls Joey towards her and dances really close to him.)
Janine: Thats it, feel the rhythm. Thats better.
Joey: Uh-huh.
Director: (To Joey) Okay, youre dancing with that girl over there.
Joey: No-no-no-no-no we came together!
Director: I dont see it. (To Janine) You are dancing with the tall guy over there. Tall guy, raise your hand! (He does. Janine goes over to him.)
Joey: No-no hey buddy, please let me dance with that girl, I really like her and I think I have a shot.
Director: Really, ythink so? I dont..
(He leaves, and this girl grabs Joey and starts dancing really wild.)
Commercial Break
[Scene: Monica and Chandler's apartment, Phoebe and Rachel are there and Chandler enters.]
Chandler: I couldn't find anything at Joey--Hey-hey, oh hey!
Rachel: Yeah, we found them. There were in the guest room closet behind some coats.
Phoebe: Yeah, and you have nothing to worry about 'cos they're all crap!
Chandler: Those are my gifts, I got them for you.
Phoebe: Ohhh. Thanks Chandler they're great!
Rachel: Well Chandler, what is this very weird, metal A Z thing?
Chandler: Those are book ends! That's a great gift!
Phoebe: Oh, okay, I'm sorry, thank you for my azzz.
Rachel: Ha!
Chandler: Make sure you put all that stuff back in the closet, okay?
Rachel: Yes, okay, oh, by the way, I just gotta say, I think it's really nice of you that even after you've moved, you still keep storing that stuff for Joey!
(Chandler does the weird clicky thing again.)
[Scene: The Set, the girl is still dancing with Joey.]
Joey: Hey-hey dancer girl! Can I go to the bathroom? I just.. (The girl starts dancing really close to him, so he picks her up, twirls her round, and puts her against a platform) Here we go. (He walks away to find Monica and Ross doing a really out of place dance) Looking good Gellers!
Ross: We know!
Monica: Hey, see that snippy guy over there? Hes the one who decides who gets up on the platform. We should go dance by him.
Ross: Okay.
(They dance over to him.)
Director: Okay, everybody hold!
(Ross and Monica high-five)
Director: Next on the platforms are (He points to the right of Ross and Monica, so they dance over to where hes pointing to. He points away from them) you two! And (He points the other way, and Ross and Monica follow his arm. Again he points away.) You two!
Monica: Excuse me, sir, would it help if I werent wearing underpants?
Ross: Monica! (Pause) Would it?
(The director shakes his head.)
[Scene: The Mens Bathroom, the tall guy is there as Joey enters.]
Joey: Hey! Tall guy! Hey, listen, I wanted to talk to you about that girl that youre dancing with.
Tall Guy: Shes nice, huh? To think I almost brought my wife to this!
Joey: Yeah, yeah, okay. Uh, look buddy, I came with that girl, and I had this plan to kiss her at the new years countdown Im trying to win her over, so I was wondering if..
Tall Guy: No I dont think so.
Joey: Oh come on man, you can dance with my partner, shes real, uh, mellow!
Tall Guy: Look, are you dating this girl you came with?
Joey: Well, I was hoping after tonight that maybe I could you know
Tall Guy: No, no. Shes fair game if you ask me, sorry buddy!
Joey: Alright, alright, hey yknow fair is fair, (he pretends to wash his hands) if youre right, youre right, what can I say, but hey oh no! (He throws water on the guys pants)
Tall Guy: God! What are you, in second grade?
 (He throws another handful on him and runs out)
[Scene: The Set, Monica and Ross are dancing.]

Ross: Hey, I know whatll get us up on a platform!
Monica: What?
Ross: The routine!
Monica: Ross, we havent done the routine since middle school.

Monica: Was it really that good?
Ross: We got honourable mention in the brother/sister dance category! Look, its almost fake midnight, do we really have any other choice?
Monica: Okay, lets do it. Mom and Dad are gonna be so faced!
(They move into a space, and Ross points to his eyes and then to hers)
Monica: 5 6 7 8!
(They start the routine. However hard I try, I really cannot describe it. You will have to watch it. Im sorry.)
(When they finish, they walk over to the director)
Ross: So, do we really have to ask whos going up on the platform next?
Director: Oh no! You get up there and do that again exactly like that!
Monica: Yes! (They run over to a platform)
Director: (To Cameraman) Make sure you get this, theyre gonna want it for the bloopers show. (To everyone) Alright cut! Listen up everyone, when we start again its gonna be the countdown to new years, so I wanna see everybodys excitement.
[Cut to Joey and Janine]
Tall Guy: Hey, pal, you have about three seconds to get away from my partner.
Director: Whats going on over here?
Joey: Uh, take a look at the guys pants!
Director: Whats the matter with you? Get out of here!
Joey: Yeah, take a hike wetpants!
(The director pushes the Tall Guy away)
[Cut to Ross and Monica, who are finally on a platform!]
Ross: Can you believe this? Were gonna be on the platform for the Millennium moment!
Monica: I know! Hey, you havent been practising the routine, have you?
Ross: No!
Monica: Me too!
Ross: Hey, when the music starts up again, I was thinking of maybe goind into the robot, yknow? (He mimics a robot)
Monica: Ross, I think we should stick to the routine, we dont wanna look stupid!
Director: Alright were back! Ten seconds left here we go! Ten! Nine! Eight! Seven! (He continues to count as we hear Joey think)
Joeys Head: Okay, it all comes down to this. Whatever happens, happens. Destiny.
All: Three, Two, One!
Director: Cut!
Joey: No! Year! Happy No Year!
Director: Okay, heres where we go to the live shot of Times Square, nice work everyone thats a wrap!
[Scene: Monica and Chandlers apartment, Chandler and Rachel are there, and Phoebe enters with the Chick and the Duck.]
Phoebe: Hey! Look who I found!
Chandler: Oh, hey guys!
Phoebe: Yknow, birds have a very good sense of direction, and I thought maybe they could help us find where the presents are hidden.
Chandler: Yes, if the presents are hidden south for the winter.
 No! Didnt think so! Okay, cmon guys, show us where the presents are!
Chandler: Oh, the duck seems to think that Monica got me garbage! Hmm, I wonder what I could get Monica thats as good as garbage?
Phoebe: Hmm, how about my azzz?
(Rachel sits on the window seat, and knocks against it)
Rachel: Hey, this is hollow.
Phoebe: What?
Rachel: This bench, its hollow! I cant believe I never knew that! (She pushes all the pillows off it and opens it up) Oh, the presents!!!
Phoebe: No, dont look directly at them!
Chandler: What?
Phoebe: Alright, no, we could look at them!
Rachel: Oh, this ones for me!
Phoebe: Oh, this ones for Chandler. Here.
Chandler: Oh great!
Phoebe: And the big ones for me!
Rachel: Ooh, lets open them!
Chandler: Okay! Okay! Okay!
Phoebe: Hee hee!
Chandler: Wait, we cant do this.
Phoebe and Rachel: Why?
Chandler: I dont wanna know what Monica got me. Yknow? I mean, look, Im sure she worked really hard at getting you a present, and wanting to surprise me, and you guys are gonna ruin that, and I, look we have to put these back, this is not what Christmas is about.
Rachel: Whatever Linus, Im opening mine.
Chandler: Nobody is opening anything ok?  So please, please, can we just, can we put them back?
Phoebe: Will you get us better gifts?
Chandler: Fine!
(Monica enters, and they throw the gifts behind them.)
Monica: Hey guys! You found the presents? Chandler, you let them find the presents? Great! Do you know how long it took me to find you that water purifier?
Chandler: Thats what you got me?
Phoebe: Oh yes, I see what you mean. That look is priceless.
(Rachel leans over to look at him.)
[Scene: Joey and Janines apartment, they both enter.]
Joey: Home sweet home, huh? Nice to, uh, get back to reality.  I guess theres no reason for all that Y2K panic, yknow? Anyway, gnight!
Janine: Joey.
Joey: Yeah?
Janine: (She takes his hands) 3, 2, 1. (She kisses him) Happy New Year.
Joey: Oh, yoii. What was that for?
Janine: Well, I dont know tonight when they yelled cut and we didnt get to kiss, I was really, really, disappointed, and I just, really wanted to kiss you
Joey: Really? In the moment, I really wanted to kiss you too. In the moment.
Janine: In the moment, yeah.
Joey: But only in the moment. So do ya wanna kiss again?
Janine: Sure, New Years Eve is only two weeks away. Can you wait?
Joey: No.
Janine: Me neither.
Joey: 3, 2,
Janine: Joey, you dont have to count down every time we kiss.
Joey: Uh, yeah, okay. Except I sorta felt like I needed a couple of seconds to get ready.
(They kiss to the music of Auld Lang Syne)
Ending Credits
[Scene: Monica and Chandler's apartment, everyone except Joey is there.]
Monica: We were on the platform, ready to dance the world into the new Millennium, and the guy yelled CUT!
Rachel: Uh, wait, so you guys are telling me you actually did the routine from eighth grade?
Monica: Yeah. But of course we had to update it a little bit. (To Ross) Hey, by the way, great thinking about catching me!

Monica: What? We could do it!
Ross: I dont know, I mean you were a lot bigger, I mean, stronger back then.
Monica: I can do it, okay? Come on, lets go. (She and Ross get up)
Monica and Ross: 1, 2, 3, 4, 5, 6, 7, 8 (Ross runs to be caught by Monica, but she moves out of the way)
Monica: I cant do it! (Ross falls into Monicas room)
Chandler: Now you do that, youre on TV.
End


Reports usages of sameElements
or corresponds
to compare collections of same kind (Seq, Set, or Map).
The quick-fix uses a equality instead.
Example:
seq sameElements list
hashSet sameElements treeSet
After the quick-fix is applied:
seq == list
hashSet == treeSet


Please check your location settings in your mobile or browser. Otherwise, a browser update could be necessary.
-
*Feel like


--- layout: post permalink: bikesomewherecom.html Tags: Array NameOfCoupon: Bike Some Where.com Cash Back Summary: See our Bike Some Where.com Coupon Code, Bike Some Where.com Rebate, Bike Some Where.com Promo Code, Bike Some Where.com Discount, Bike Some Where.com Coupon Cash Back Rebate here.  We have the best Bike Some Where.com Rebate anywhere. thesis_keywords: Bike Some Where.com, Bike Some Where.com Coupon Code, Bike Some Where.com Discount, Bike Some Where.com Rebate product_name: Bike Some Where.com hop_url: http://www.icouponblog.com/hop.php?id=1080 ---
Bike Some Where.com is an amazing place for all your biking needs. It is the ultimate bike store. If you are a biker looking for bicycle related items and lot more, Bike Some Where.com will pleasantly surprise you. They carry all hundreds of products relating to bicycles and cycling activities. You can get bike clothing and apparel, protective gears, helmets, heart rate monitors, lubes, cleaners, pumps, racks, stands and much more. Visit Bike Some Where.com for high quality products at great prices. Use our discount coupons to get fantastic deals on Bike Some Where.com today and everyday.
Bike Some Where.com has hundreds of biking apparels and clothing. You can get cycling shirts, shorts, knickers, bibs, vests, jackets, cycling team uniforms, cycling arms and legs warmers, cycling socks, gloves, ventilator caps. Bike Some Where.com also carries bicycle tubes, bicycle mounted baskets, CO2 inflating cartridges, saddle bags and lots of other products that you will satisfy your biking needs. Check out Bike Some Where.com now and save money by using our cash back rebate coupons now!
Bike Some Where.com has a great website. You can find loads of items for your bicycling needs from bike computers to apparel and accessories. For the best quality products in the most reasonable, affordable prices go to Bike Some Where.com now, it is a place where many professional cyclists shop at. Remember, Bike Some Where.com, the ultimate bike store!


Our gallant crew consisted of Ray, Curtis, Kevin, his wife Joanna and daughter Catherine, John, a guest, Mike and son Corey, John G., Paul, Jake and Dave V.
We found the beginning of the trail needed some work and thanks to the fact that tree branches had been cleared from the road our work was a bit easier. We utilized the tree branches by putting them into the ruts to stop the run off from tearing the road up even more. As we worked our way up we continued to fill in ruts and clear branches out of the road way.
At the obstacle we found the bypass has become quite difficult now though not as hard as the main thoroughfare. John had just a bit of trouble with a rock...seems it liked a bit of his vehicle and claimed it. John Gamby tried the bypass and was able to make it up with a little work...once he get a lift on that Renegade and some lockers there will be not stopping him. Kevin also had some fun with the rocks and dirt but made it up with no damage. Ray, Mike, Jake, Paul, Curtis, and Dave made it up with no problems.
After having lunch we continued up to our "favorite" spot...the lean. It was covered with snow and Ray came very close to "meeting" a tree. We worked getting the road passable by clearing snow, building up the lower side with more tree branches and some rocks, hoping that it will fill in and the danger of sliding off that way will lessen. We got Ray out of his bit of tousle and down the road which after all of our work was a "bit" easier for the other drivers. The bog didn't need any work and as we were discussing what we were going to do it began to rain and the decision to go home was made.
Thanks to all who showed up and for all your hard work...


--- title: About header-img: "img/about-bg.png" ---
Junior Web Developer passionate about all things code
A passionate Junior Web Developer and recent Flatiron School graduate residing in the New York City area. Having gone through multiple education paths and helping others along the way in my own learning journey, I have learned a lot about myself. Here are some quick facts about me
I am a fast learner. In less than a year I have completed over 300 small programs and 4 major projects. In addition to attending Flatiron School, I simultaneously pursued a Computer Science degree at a local community college and became the Vice President of the Computer Science Club. Due to my diligence, hard work and willingness to help others, I have acted as an ambassador to my fellow students in Flatiron School. This led me to being promoted as a Technical Coach, where I tutor other students in web development.
View on Github
View on Github
View on Github


About {{(listEmployee|filter:employeeSearchInput).length}} result (0.13 seconds)
About {{(listEmployee|filter:employeeSearch).length}} result (0.13 seconds)
Select an image from your gallery Submit Close
Email
Phone
Platform
Department
Role
Blood Group
Address


Terms & conditions
I would like to become a WWOOF INDEPENDENTS Host, and confirm that:
- my farm or property is organic and / or uses ecologically sound techniques
- I will provide hands-on experience of organic growing and other learning opportunities
- I will provide clean dry accommodation and adequate food for volunteers
- I will not charge volunteers money for their stay (WWOOF is a non-monetary exchange)
- I will reply to all reasonable volunteer enquiries ( even if only to say that I am unable to
accommodate volunteers at this time )
- I will ensure that WWOOFers are current members of a WWOOF organisation
- I understand that many volunteers are not skilled and should not be expected to take the
place of paid workers.
- I understand and agree that the responsibility of WWOOF is limited to providing a means
of contact between hosts and WWOOF members, and that the arrangements I make with volunteers is entirely my own responsibility.
- I have read, understood and agree with the mission statement and commit to respect
and support the philosophy of this movement.
“WWOOF is a worldwide movement linking volunteers with organic farmers and
growers to promote cultural and educational experiences based on trust and nonmonetary exchange, thereby helping to building a sustainable global community.”


{% extends "base.html" %} {% import 'bootstrap/wtf.html' as wtf %} {% block app_content %}
As a result of running this wizard, the information generated will be
Afterwards, following the instructions you will be able to use that repository to deploy the Buildfarm.


run
This page contains webassembly and javascript content, please enable javascript in your browser.