I enjoyed my time at Ericsson
I enjoyed my studies at the Royal Institute of Technology (KTH).
I enjoyed my time working for the IT department of Stockholm University.
I enjoyed my time at Nanoradio and my time at Samsung after they aquired us.
Now a new chapter dawns and I tought I would try something new.
So as of 2015 I am a freelance developer.
Lets have some fun...


NBA roundup: Leonard, Clippers hand Spurs 1st loss of season
Kawhi Leonard had 38 points and 12 rebounds to lead the Los Angeles Clippers to a 103-97 win against the visiting San Antonio Spurs on Thursday night.
The game marked the third matchup between Leonard and DeRozan since the Spurs traded Leonard to the Toronto Raptors in July 2018 in a deal that brought DeRozan to San Antonio.
Montrezl Harrell scored 24 points off the bench and Lou Williams added 12 points in a reserve role despite shooting just 5-for-19 for Los Angeles.
DeMar DeRozan scored 29 points, Derrick White had 20 points off the bench and Rudy Gay added nine points and 12 rebounds for the Spurs, who had won their first three games this season — leaving the Philadelphia 76ers as the NBA’s only remaining unbeaten team.
Heat 106, Hawks 97
Rookie Kendrick Nunn produced his third 20-point effort of the season, going for a career-high 28 points to lead Miami to a win at Atlanta.
Nunn shot 10-for-15 from the field and upped his season average to 22.4 points. Nunn has scored 112 points this season, an NBA record for an undrafted free agent in his first five career games.
Tyler Herro scored 17 and Meyers Leonard added 16 for Miami. Jimmy Butler led the Heat with 11 assists and nine rebounds but he scored just five points on 2-of-10 shooting in his second game with the Heat. Jabari Parker led the Hawks with 23 points and added eight rebounds.
Pelicans 122, Nuggets 107
Jahlil Okafor scored 26 points as host New Orleans got its first victory of the season, defeating Denver.
Okafor, making his second consecutive start with starting center Derrick Favors sidelined by knee soreness, made 8 of 13 shots to become the first Pelican other than Brandon Ingram to lead the team in scoring this season. Ingram finished with 25.
Frank Jackson came off the bench to add 21 points and Jrue Holiday, returning from a two-game absence due to a sprained knee, had 19 points, five rebounds and seven assists. Michael Porter Jr., in his first career game after a knee injury derailed his 2018-19 season, led Denver with 15 points.
—Field Level Media


Meggie
- Student ID: 117010086
- School: SSE
- College: Muse
- Hobbies:
- Music
- Sleep
Joslyn
- Student ID: 117010154
- School: SSE
- College: Muse
- Hobbies:
- Soduko
- Music
Tony
- Student ID: 117010047
- School: SSE
- College: Shaw
- Hobbies:
- Movie
- skating


REST URL shortening web service, which provides short aliases for redirection of long URLs.
Service functionality:


-
common disorder
-
organic
-
gradual onset
-
difficulty becomes progressively worse with time
-
early morning erections usually decreased or absent
-
-
pscyhogenic
-
suddenly
-
complete/immediate loss of seual function
-
vary with partner or situation
-
may be indistinguishable caused by organic
-
maintained theri early morning erections
-
-
likely combined
- not mutually exclusive
History
-
understand;
-
nature of complaint
-
imact on himself, partner and relationship
-
-
how man and partner have adapted to this condition
-
determine liekly cause
-
identify co-morbidities
-
other sexual difficulties
-
low sexual desire
-
rapid ejaculation
-
associated sexual difficulties for partner
-
Physiology of erection
-
sexual stimulation, physical mental
-
release NO from penile nerves
-
stimulates cyclic huanosine monophosphate (cGMP)
- within vasuclar smooth muscle of corpora cavernosae
-
-
-
cGMP induces smooth muscle relaxation
-
vascualr lakes fill with blood
-
penile veins passively compressed
-
restricts venous return
-
-
-
cGMP -> 5’GMP by action of PDE5
- sildenafil, tadalafil and vardenafil inhibit this enzyme
Exam
-
cardiovascular risk assessment
-
genital examination
-
occ. identify anatomical abnormalities
-
signs of hypogonadism
-
more importantly taking condition seriously
-
-
-
diabeties
-
DRE -> suspected prostate disease
Investigations
-
unexplained low libido or suspected hypogonadism
-
testosterone and prolactin @ 0800hrs
-
CVRA
-
associated medications:
-
Betablockers, CCB
-
Thiazides, spironolactones
-
SSRI, TCA, MAOi
-
Phenothiazines, carbamazepin, risperidone
-
Cyproterone, finasteride (5a-reductase
-
H2 antagonist
-
EtoH, meriguana, cocaine
Risk factors
-
metabolic syndrome
-
cardiovascular disease
-
PDE5i contraindicated until specialsit
-
unstable angina
-
uncontrolled tn
-
chf Class 3/4
-
very recent MI (\<2w)
-
high risk arryhtmia
-
obstructive hypertrophic cardiomyopathies
-
moderate- severe valvular disease
-
-
Treatment
-
Suitability for PDE5:
-
does exertion, stress, sexual activity cause any symptoms
-
what is most strenusous activity?
-
do you accept risk of taking this medicaiton
-
-
PDE5 first line
-
tadalafil has longer half life
-
no evidence of superiority of one vs other
-
require sexual stimuliation to have an efefct
-
take at least 40minutes to 1 hr before sexual activity
-
fattyfood/etoh may delay onset of action
-
contraindicated
-
nitrates
-
potentiate hypotensive effects of organic nitrates
-
safe time interval not dertmined
-
24hr sildenafil
-
48hrs tadalafil
-
-
-
-
adverse effects;
-
headahce
-
flushing
-
gastric upset
-
diarrhoea
-
nasal congestion
-
light headedness
-
Sildenafil and vardenafil have some cross-reactivity
-
-
-
Injection therapies
-
act directly by relaxing smooth msucle in corpora cavernosum
-
do not require sexual stimulation
-
firstdose administered under medical supervision
-
small risk of priaprism
-
Alprostadil (caverject)
-
phentolamine (invicorp)
-
-
Penile devices
-
prosthese
-
vacuum devices
-
-
Testosterone therapy not usually indicated for men with nroaml testosterone levels
-
appropriate whne man with ED has hypogonadism
-
Hynaecomastia, increased haematocit, changed lipid, htn, infertility = seide effects
-
increase risk of prostat cancer
-


Sharksicle is an underground T-Shirt and merchandise company based in Phoenix, Arizona. Some spoof off designs can be found on Amazon and through other sellers, but the real thing can only be found through Sharksicle dealers.
Different dealers have different one-of-a-kind designs, so you never know what you're going to get--but we can bet it's going to be awesome.
Putting on a Sharksicle shirt is the satisfying feeling of knowing something they don’t. Sharksicle stands for both loyalty and independence, compromise and rebellion, unity and individuality.
Sharksicle merch is coming soon, and we can hardly wait! In the meantime, you can visit the *very important* webpage below.
Click Here


- Roy Fielding
Documenting REST APIs
apihandyman.io
How RESTful are you?
How RESTful do you
want to be?
Interface Description Languages
Media Types
HAL
{
"_links": {
"self": {
"href": "http://otrosien:8081/pizzas"
}
},
"_embedded": {
"pizzas": [
{
"name": "Pizza Salami",
"description": "The classic"
}
]
}
}
Spring-Data-REST
Spring WebMVC Spring-Data Spring-HATEOAS
- Repositories as resources with CRUD operations
- Supports HAL + ALPS + JSON Schema
- Ties your REST API to your data model
olivergierke/spring-restbucks
Follow your nose API
- Single well-known entry point
- Resources discoverable via link relations
Documentation style
- Focus on problem domain
- Focus on relations
- Be consistent
- Focus on URIs
- Repeating the obvious
Demo
Learnings
- IDL standards are still evolving
- Tool-support (usually) still poor
- Be correct, complete and current


PERLCALL
Section: Perl Programmers Reference Guide (1)Updated: 2009-04-12
Index Return to Main Contents
NAME
perlcall - Perl calling conventions from CDESCRIPTION
The purpose of this document is to show you how to call Perl subroutines directly from C, i.e., how to write callbacks.Apart from discussing the C interface provided by Perl for writing callbacks the document uses a series of examples to show how the interface actually works in practice. In addition some techniques for coding callbacks are covered.
Examples where callbacks are necessary include
- *
-
An Error Handler
You have created an XSUB interface to an application's C API.
A fairly common feature in applications is to allow you to define a C function that will be called whenever something nasty occurs. What we would like is to be able to specify a Perl subroutine that will be called instead.
- *
-
An Event Driven Program
The classic example of where callbacks are used is when writing an event driven program like for an X windows application. In this case you register functions to be called whenever specific events occur, e.g., a mouse button is pressed, the cursor moves into a window or a menu item is selected.
Although the techniques described here are applicable when embedding Perl in a C program, this is not the primary goal of this document. There are other details that must be considered and are specific to embedding Perl. For details on embedding Perl in C refer to perlembed.
Before you launch yourself head first into the rest of this document, it would be a good idea to have read the following two documents - perlxs and perlguts.
THE CALL_ FUNCTIONS
Although this stuff is easier to explain using examples, you first need be aware of a few important definitions.Perl has a number of C functions that allow you to call Perl subroutines. They are
I32 call_sv(SV* sv, I32 flags); I32 call_pv(char *subname, I32 flags); I32 call_method(char *methname, I32 flags); I32 call_argv(char *subname, I32 flags, register char **argv);
The key function is call_sv. All the other functions are fairly simple wrappers which make it easier to call Perl subroutines in special cases. At the end of the day they will all call call_sv to invoke the Perl subroutine.
All the call_* functions have a "flags" parameter which is used to pass a bit mask of options to Perl. This bit mask operates identically for each of the functions. The settings available in the bit mask are discussed in ``FLAG VALUES''.
Each of the functions will now be discussed in turn.
- call_sv
- call_sv takes two parameters, the first, "sv", is an SV*. This allows you to specify the Perl subroutine to be called either as a C string (which has first been converted to an SV) or a reference to a subroutine. The section, Using call_sv, shows how you can make use of call_sv.
- call_pv
- The function, call_pv, is similar to call_sv except it expects its first parameter to be a C char* which identifies the Perl subroutine you want to call, e.g., "call_pv("fred", 0)". If the subroutine you want to call is in another package, just include the package name in the string, e.g., "pkg::fred".
- call_method
- The function call_method is used to call a method from a Perl class. The parameter "methname" corresponds to the name of the method to be called. Note that the class that the method belongs to is passed on the Perl stack rather than in the parameter list. This class can be either the name of the class (for a static method) or a reference to an object (for a virtual method). See perlobj for more information on static and virtual methods and ``Using call_method'' for an example of using call_method.
- call_argv
- call_argv calls the Perl subroutine specified by the C string stored in the "subname" parameter. It also takes the usual "flags" parameter. The final parameter, "argv", consists of a NULL terminated list of C strings to be passed as parameters to the Perl subroutine. See Using call_argv.
All the functions return an integer. This is a count of the number of items returned by the Perl subroutine. The actual items returned by the subroutine are stored on the Perl stack.
As a general rule you should always check the return value from these functions. Even if you are expecting only a particular number of values to be returned from the Perl subroutine, there is nothing to stop someone from doing something unexpected---don't say you haven't been warned.
FLAG VALUES
The "flags" parameter in all the call_* functions is a bit mask which can consist of any combination of the symbols defined below, OR'ed together.G_VOID
Calls the Perl subroutine in a void context.This flag has 2 effects:
- 1.
- It indicates to the subroutine being called that it is executing in a void context (if it executes wantarray the result will be the undefined value).
- 2.
- It ensures that nothing is actually returned from the subroutine.
The value returned by the call_* function indicates how many items have been returned by the Perl subroutine - in this case it will be 0.
G_SCALAR
Calls the Perl subroutine in a scalar context. This is the default context flag setting for all the call_* functions.This flag has 2 effects:
- 1.
- It indicates to the subroutine being called that it is executing in a scalar context (if it executes wantarray the result will be false).
- 2.
- It ensures that only a scalar is actually returned from the subroutine. The subroutine can, of course, ignore the wantarray and return a list anyway. If so, then only the last element of the list will be returned.
The value returned by the call_* function indicates how many items have been returned by the Perl subroutine - in this case it will be either 0 or 1.
If 0, then you have specified the G_DISCARD flag.
If 1, then the item actually returned by the Perl subroutine will be stored on the Perl stack - the section Returning a Scalar shows how to access this value on the stack. Remember that regardless of how many items the Perl subroutine returns, only the last one will be accessible from the stack - think of the case where only one value is returned as being a list with only one element. Any other items that were returned will not exist by the time control returns from the call_* function. The section Returning a list in a scalar context shows an example of this behavior.
G_ARRAY
Calls the Perl subroutine in a list context.As with G_SCALAR, this flag has 2 effects:
- 1.
- It indicates to the subroutine being called that it is executing in a list context (if it executes wantarray the result will be true).
- 2.
- It ensures that all items returned from the subroutine will be accessible when control returns from the call_* function.
The value returned by the call_* function indicates how many items have been returned by the Perl subroutine.
If 0, then you have specified the G_DISCARD flag.
If not 0, then it will be a count of the number of items returned by the subroutine. These items will be stored on the Perl stack. The section Returning a list of values gives an example of using the G_ARRAY flag and the mechanics of accessing the returned items from the Perl stack.
G_DISCARD
By default, the call_* functions place the items returned from by the Perl subroutine on the stack. If you are not interested in these items, then setting this flag will make Perl get rid of them automatically for you. Note that it is still possible to indicate a context to the Perl subroutine by using either G_SCALAR or G_ARRAY.If you do not set this flag then it is very important that you make sure that any temporaries (i.e., parameters passed to the Perl subroutine and values returned from the subroutine) are disposed of yourself. The section Returning a Scalar gives details of how to dispose of these temporaries explicitly and the section Using Perl to dispose of temporaries discusses the specific circumstances where you can ignore the problem and let Perl deal with it for you.
G_NOARGS
Whenever a Perl subroutine is called using one of the call_* functions, it is assumed by default that parameters are to be passed to the subroutine. If you are not passing any parameters to the Perl subroutine, you can save a bit of time by setting this flag. It has the effect of not creating the @_ array for the Perl subroutine.Although the functionality provided by this flag may seem straightforward, it should be used only if there is a good reason to do so. The reason for being cautious is that even if you have specified the G_NOARGS flag, it is still possible for the Perl subroutine that has been called to think that you have passed it parameters.
In fact, what can happen is that the Perl subroutine you have called can access the @_ array from a previous Perl subroutine. This will occur when the code that is executing the call_* function has itself been called from another Perl subroutine. The code below illustrates this
sub fred { print "@_\n" } sub joe { &fred } &joe(1,2,3);
This will print
1 2 3
What has happened is that "fred" accesses the @_ array which belongs to "joe".
G_EVAL
It is possible for the Perl subroutine you are calling to terminate abnormally, e.g., by calling die explicitly or by not actually existing. By default, when either of these events occurs, the process will terminate immediately. If you want to trap this type of event, specify the G_EVAL flag. It will put an eval { } around the subroutine call.Whenever control returns from the call_* function you need to check the $@ variable as you would in a normal Perl script.
The value returned from the call_* function is dependent on what other flags have been specified and whether an error has occurred. Here are all the different cases that can occur:
- *
- If the call_* function returns normally, then the value returned is as specified in the previous sections.
- *
- If G_DISCARD is specified, the return value will always be 0.
- *
- If G_ARRAY is specified and an error has occurred, the return value will always be 0.
- *
- If G_SCALAR is specified and an error has occurred, the return value will be 1 and the value on the top of the stack will be undef. This means that if you have already detected the error by checking $@ and you want the program to continue, you must remember to pop the undef from the stack.
See Using G_EVAL for details on using G_EVAL.
G_KEEPERR
You may have noticed that using the G_EVAL flag described above will always clear the $@ variable and set it to a string describing the error iff there was an error in the called code. This unqualified resetting of $@ can be problematic in the reliable identification of errors using the "eval {}" mechanism, because the possibility exists that perl will call other code (end of block processing code, for example) between the time the error causes $@ to be set within "eval {}", and the subsequent statement which checks for the value of $@ gets executed in the user's script.This scenario will mostly be applicable to code that is meant to be called from within destructors, asynchronous callbacks, signal handlers, "__DIE__" or "__WARN__" hooks, and "tie" functions. In such situations, you will not want to clear $@ at all, but simply to append any new errors to any existing value of<EMAIL_ADDRESS>The G_KEEPERR flag is meant to be used in conjunction with G_EVAL in call_* functions that are used to implement such code. This flag has no effect when G_EVAL is not used.
When G_KEEPERR is used, any errors in the called code will be prefixed with the string ``\t(in cleanup)'', and appended to the current value of<EMAIL_ADDRESS>an error will not be appended if that same error string is already at the end of<EMAIL_ADDRESS>In addition, a warning is generated using the appended string. This can be disabled using "no warnings 'misc'".
The G_KEEPERR flag was introduced in Perl version 5.002.
See Using G_KEEPERR for an example of a situation that warrants the use of this flag.
Determining the Context
As mentioned above, you can determine the context of the currently executing subroutine in Perl with wantarray. The equivalent test can be made in C by using the "GIMME_V" macro, which returns "G_ARRAY" if you have been called in a list context, "G_SCALAR" if in a scalar context, or "G_VOID" if in a void context (i.e. the return value will not be used). An older version of this macro is called "GIMME"; in a void context it returns "G_SCALAR" instead of "G_VOID". An example of using the "GIMME_V" macro is shown in section Using GIMME_V.EXAMPLES
Enough of the definition talk, let's have a few examples.Perl provides many macros to assist in accessing the Perl stack. Wherever possible, these macros should always be used when interfacing to Perl internals. We hope this should make the code less vulnerable to any changes made to Perl in the future.
Another point worth noting is that in the first series of examples I have made use of only the call_pv function. This has been done to keep the code simpler and ease you into the topic. Wherever possible, if the choice is between using call_pv and call_sv, you should always try to use call_sv. See Using call_sv for details.
No Parameters, Nothing returned
This first trivial example will call a Perl subroutine, PrintUID, to print out the UID of the process.
sub PrintUID { print "UID is $<\n"; }
and here is a C function to call it
static void call_PrintUID() { dSP; PUSHMARK(SP); call_pv("PrintUID", G_DISCARD|G_NOARGS); }
Simple, eh.
A few points to note about this example.
- 1.
- Ignore "dSP" and "PUSHMARK(SP)" for now. They will be discussed in the next example.
- 2.
- We aren't passing any parameters to PrintUID so G_NOARGS can be specified.
- 3.
- We aren't interested in anything returned from PrintUID, so G_DISCARD is specified. Even if PrintUID was changed to return some value(s), having specified G_DISCARD will mean that they will be wiped by the time control returns from call_pv.
- 4.
- As call_pv is being used, the Perl subroutine is specified as a C string. In this case the subroutine name has been 'hard-wired' into the code.
- 5.
- Because we specified G_DISCARD, it is not necessary to check the value returned from call_pv. It will always be 0.
Passing Parameters
Now let's make a slightly more complex example. This time we want to call a Perl subroutine, "LeftString", which will take 2 parameters---a string ($s) and an integer ($n). The subroutine will simply print the first $n characters of the string.So the Perl subroutine would look like this
sub LeftString { my($s, $n) = @_; print substr($s, 0, $n), "\n"; }
The C function required to call LeftString would look like this.
static void call_LeftString(a, b) char * a; int b; { dSP; ENTER; SAVETMPS; PUSHMARK(SP); XPUSHs(sv_2mortal(newSVpv(a, 0))); XPUSHs(sv_2mortal(newSViv(b))); PUTBACK; call_pv("LeftString", G_DISCARD); FREETMPS; LEAVE; }
Here are a few notes on the C function call_LeftString.
- 1.
- Parameters are passed to the Perl subroutine using the Perl stack. This is the purpose of the code beginning with the line "dSP" and ending with the line "PUTBACK". The "dSP" declares a local copy of the stack pointer. This local copy should always be accessed as "SP".
- 2.
-
If you are going to put something onto the Perl stack, you need to know
where to put it. This is the purpose of the macro "dSP"--it declares
and initializes a local copy of the Perl stack pointer.
All the other macros which will be used in this example require you to have used this macro.
The exception to this rule is if you are calling a Perl subroutine directly from an XSUB function. In this case it is not necessary to use the "dSP" macro explicitly---it will be declared for you automatically.
- 3.
-
Any parameters to be pushed onto the stack should be bracketed by the
"PUSHMARK" and "PUTBACK" macros. The purpose of these two macros, in
this context, is to count the number of parameters you are
pushing automatically. Then whenever Perl is creating the @_ array for the
subroutine, it knows how big to make it.
The "PUSHMARK" macro tells Perl to make a mental note of the current stack pointer. Even if you aren't passing any parameters (like the example shown in the section No Parameters, Nothing returned) you must still call the "PUSHMARK" macro before you can call any of the call_* functions---Perl still needs to know that there are no parameters.
The "PUTBACK" macro sets the global copy of the stack pointer to be the same as our local copy. If we didn't do this call_pv wouldn't know where the two parameters we pushed were---remember that up to now all the stack pointer manipulation we have done is with our local copy, not the global copy.
- 4.
-
Next, we come to XPUSHs. This is where the parameters actually get
pushed onto the stack. In this case we are pushing a string and an
integer.
See ``XSUBs and the Argument Stack'' in perlguts for details on how the XPUSH macros work.
- 5.
-
Because we created temporary values (by means of sv_2mortal() calls)
we will have to tidy up the Perl stack and dispose of mortal SVs.
This is the purpose of
ENTER; SAVETMPS;
at the start of the function, and
FREETMPS; LEAVE;
at the end. The "ENTER"/"SAVETMPS" pair creates a boundary for any temporaries we create. This means that the temporaries we get rid of will be limited to those which were created after these calls.
The "FREETMPS"/"LEAVE" pair will get rid of any values returned by the Perl subroutine (see next example), plus it will also dump the mortal SVs we have created. Having "ENTER"/"SAVETMPS" at the beginning of the code makes sure that no other mortals are destroyed.
Think of these macros as working a bit like using "{" and "}" in Perl to limit the scope of local variables.
See the section Using Perl to dispose of temporaries for details of an alternative to using these macros.
- 6.
- Finally, LeftString can now be called via the call_pv function. The only flag specified this time is G_DISCARD. Because we are passing 2 parameters to the Perl subroutine this time, we have not specified G_NOARGS.
Returning a Scalar
Now for an example of dealing with the items returned from a Perl subroutine.Here is a Perl subroutine, Adder, that takes 2 integer parameters and simply returns their sum.
sub Adder { my($a, $b) = @_; $a + $b; }
Because we are now concerned with the return value from Adder, the C function required to call it is now a bit more complex.
static void call_Adder(a, b) int a; int b; { dSP; int count; ENTER; SAVETMPS; PUSHMARK(SP); XPUSHs(sv_2mortal(newSViv(a))); XPUSHs(sv_2mortal(newSViv(b))); PUTBACK; count = call_pv("Adder", G_SCALAR); SPAGAIN; if (count != 1) croak("Big trouble\n"); printf ("The sum of %d and %d is %d\n", a, b, POPi); PUTBACK; FREETMPS; LEAVE; }
Points to note this time are
- 1.
- The only flag specified this time was G_SCALAR. That means the @_ array will be created and that the value returned by Adder will still exist after the call to call_pv.
- 2.
-
The purpose of the macro "SPAGAIN" is to refresh the local copy of the
stack pointer. This is necessary because it is possible that the memory
allocated to the Perl stack has been reallocated whilst in the
call_pv call.
If you are making use of the Perl stack pointer in your code you must always refresh the local copy using SPAGAIN whenever you make use of the call_* functions or any other Perl internal function.
- 3.
-
Although only a single value was expected to be returned from Adder,
it is still good practice to check the return code from call_pv
anyway.
Expecting a single value is not quite the same as knowing that there will be one. If someone modified Adder to return a list and we didn't check for that possibility and take appropriate action the Perl stack would end up in an inconsistent state. That is something you really don't want to happen ever.
- 4.
-
The "POPi" macro is used here to pop the return value from the stack.
In this case we wanted an integer, so "POPi" was used.
Here is the complete list of POP macros available, along with the types they return.
POPs SV POPp pointer POPn double POPi integer POPl long
- 5.
- The final "PUTBACK" is used to leave the Perl stack in a consistent state before exiting the function. This is necessary because when we popped the return value from the stack with "POPi" it updated only our local copy of the stack pointer. Remember, "PUTBACK" sets the global stack pointer to be the same as our local copy.
Returning a list of values
Now, let's extend the previous example to return both the sum of the parameters and the difference.Here is the Perl subroutine
sub AddSubtract { my($a, $b) = @_; ($a+$b, $a-$b); }
and this is the C function
static void call_AddSubtract(a, b) int a; int b; { dSP; int count; ENTER; SAVETMPS; PUSHMARK(SP); XPUSHs(sv_2mortal(newSViv(a))); XPUSHs(sv_2mortal(newSViv(b))); PUTBACK; count = call_pv("AddSubtract", G_ARRAY); SPAGAIN; if (count != 2) croak("Big trouble\n"); printf ("%d - %d = %d\n", a, b, POPi); printf ("%d + %d = %d\n", a, b, POPi); PUTBACK; FREETMPS; LEAVE; }
If call_AddSubtract is called like this
call_AddSubtract(7, 4);
then here is the output
7 - 4 = 3 7 + 4 = 11
Notes
- 1.
- We wanted list context, so G_ARRAY was used.
- 2.
- Not surprisingly "POPi" is used twice this time because we were retrieving 2 values from the stack. The important thing to note is that when using the "POP*" macros they come off the stack in reverse order.
Returning a list in a scalar context
Say the Perl subroutine in the previous section was called in a scalar context, like this
static void call_AddSubScalar(a, b) int a; int b; { dSP; int count; int i; ENTER; SAVETMPS; PUSHMARK(SP); XPUSHs(sv_2mortal(newSViv(a))); XPUSHs(sv_2mortal(newSViv(b))); PUTBACK; count = call_pv("AddSubtract", G_SCALAR); SPAGAIN; printf ("Items Returned = %d\n", count); for (i = 1; i <= count; ++i) printf ("Value %d = %d\n", i, POPi); PUTBACK; FREETMPS; LEAVE; }
The other modification made is that call_AddSubScalar will print the number of items returned from the Perl subroutine and their value (for simplicity it assumes that they are integer). So if call_AddSubScalar is called
call_AddSubScalar(7, 4);
then the output will be
Items Returned = 1 Value 1 = 3
In this case the main point to note is that only the last item in the list is returned from the subroutine, AddSubtract actually made it back to call_AddSubScalar.
Returning Data from Perl via the parameter list
It is also possible to return values directly via the parameter list - whether it is actually desirable to do it is another matter entirely.The Perl subroutine, Inc, below takes 2 parameters and increments each directly.
sub Inc { ++ $_[0]; ++ $_[1]; }
and here is a C function to call it.
static void call_Inc(a, b) int a; int b; { dSP; int count; SV * sva; SV * svb; ENTER; SAVETMPS; sva = sv_2mortal(newSViv(a)); svb = sv_2mortal(newSViv(b)); PUSHMARK(SP); XPUSHs(sva); XPUSHs(svb); PUTBACK; count = call_pv("Inc", G_DISCARD); if (count != 0) croak ("call_Inc: expected 0 values from 'Inc', got %d\n", count); printf ("%d + 1 = %d\n", a, SvIV(sva)); printf ("%d + 1 = %d\n", b, SvIV(svb)); FREETMPS; LEAVE; }
To be able to access the two parameters that were pushed onto the stack after they return from call_pv it is necessary to make a note of their addresses---thus the two variables "sva" and "svb".
The reason this is necessary is that the area of the Perl stack which held them will very likely have been overwritten by something else by the time control returns from call_pv.
Using G_EVAL
Now an example using G_EVAL. Below is a Perl subroutine which computes the difference of its 2 parameters. If this would result in a negative result, the subroutine calls die.
sub Subtract { my ($a, $b) = @_; die "death can be fatal\n" if $a < $b; $a - $b; }
and some C to call it
static void call_Subtract(a, b) int a; int b; { dSP; int count; ENTER; SAVETMPS; PUSHMARK(SP); XPUSHs(sv_2mortal(newSViv(a))); XPUSHs(sv_2mortal(newSViv(b))); PUTBACK; count = call_pv("Subtract", G_EVAL|G_SCALAR); SPAGAIN; /* Check the eval first */ if (SvTRUE(ERRSV)) { printf ("Uh oh - %s\n", SvPV_nolen(ERRSV)); POPs; } else { if (count != 1) croak("call_Subtract: wanted 1 value from 'Subtract', got %d\n", count); printf ("%d - %d = %d\n", a, b, POPi); } PUTBACK; FREETMPS; LEAVE; }
If call_Subtract is called thus
call_Subtract(4, 5)
the following will be printed
Uh oh - death can be fatal
Notes
- 1.
- We want to be able to catch the die so we have used the G_EVAL flag. Not specifying this flag would mean that the program would terminate immediately at the die statement in the subroutine Subtract.
- 2.
-
The code
if (SvTRUE(ERRSV)) { printf ("Uh oh - %s\n", SvPV_nolen(ERRSV)); POPs; }
is the direct equivalent of this bit of Perl
print "Uh oh - $@\n" if $@;
"PL_errgv" is a perl global of type "GV *" that points to the symbol table entry containing the error. "ERRSV" therefore refers to the C equivalent of<EMAIL_ADDRESS>- 3.
- Note that the stack is popped using "POPs" in the block where "SvTRUE(ERRSV)" is true. This is necessary because whenever a call_* function invoked with G_EVAL|G_SCALAR returns an error, the top of the stack holds the value undef. Because we want the program to continue after detecting this error, it is essential that the stack is tidied up by removing the undef.
Using G_KEEPERR
Consider this rather facetious example, where we have used an XS version of the call_Subtract example above inside a destructor:
package Foo; sub new { bless {}, $_[0] } sub Subtract { my($a,$b) = @_; die "death can be fatal" if $a < $b; $a - $b; } sub DESTROY { call_Subtract(5, 4); } sub foo { die "foo dies"; } package main; eval { Foo->new->foo }; print "Saw: $@" if $@; # should be, but isn't
This example will fail to recognize that an error occurred inside the "eval {}". Here's why: the call_Subtract code got executed while perl was cleaning up temporaries when exiting the eval block, and because call_Subtract is implemented with call_pv using the G_EVAL flag, it promptly reset<EMAIL_ADDRESS>This results in the failure of the outermost test for $@, and thereby the failure of the error trap.
Appending the G_KEEPERR flag, so that the call_pv call in call_Subtract reads:
count = call_pv("Subtract", G_EVAL|G_SCALAR|G_KEEPERR);
will preserve the error and restore reliable error handling.
Using call_sv
In all the previous examples I have 'hard-wired' the name of the Perl subroutine to be called from C. Most of the time though, it is more convenient to be able to specify the name of the Perl subroutine from within the Perl script.Consider the Perl code below
sub fred { print "Hello there\n"; } CallSubPV("fred");
Here is a snippet of XSUB which defines CallSubPV.
void CallSubPV(name) char * name CODE: PUSHMARK(SP); call_pv(name, G_DISCARD|G_NOARGS);
That is fine as far as it goes. The thing is, the Perl subroutine can be specified as only a string. For Perl 4 this was adequate, but Perl 5 allows references to subroutines and anonymous subroutines. This is where call_sv is useful.
The code below for CallSubSV is identical to CallSubPV except that the "name" parameter is now defined as an SV* and we use call_sv instead of call_pv.
void CallSubSV(name) SV * name CODE: PUSHMARK(SP); call_sv(name, G_DISCARD|G_NOARGS);
Because we are using an SV to call fred the following can all be used
CallSubSV("fred"); CallSubSV(\&fred); $ref = \&fred; CallSubSV($ref); CallSubSV( sub { print "Hello there\n" } );
As you can see, call_sv gives you much greater flexibility in how you can specify the Perl subroutine.
You should note that if it is necessary to store the SV ("name" in the example above) which corresponds to the Perl subroutine so that it can be used later in the program, it not enough just to store a copy of the pointer to the SV. Say the code above had been like this
static SV * rememberSub; void SaveSub1(name) SV * name CODE: rememberSub = name; void CallSavedSub1() CODE: PUSHMARK(SP); call_sv(rememberSub, G_DISCARD|G_NOARGS);
The reason this is wrong is that by the time you come to use the pointer "rememberSub" in "CallSavedSub1", it may or may not still refer to the Perl subroutine that was recorded in "SaveSub1". This is particularly true for these cases
SaveSub1(\&fred); CallSavedSub1(); SaveSub1( sub { print "Hello there\n" } ); CallSavedSub1();
By the time each of the "SaveSub1" statements above have been executed, the SV*s which corresponded to the parameters will no longer exist. Expect an error message from Perl of the form
Can't use an undefined value as a subroutine reference at ...
for each of the "CallSavedSub1" lines.
Similarly, with this code
$ref = \&fred; SaveSub1($ref); $ref = 47; CallSavedSub1();
you can expect one of these messages (which you actually get is dependent on the version of Perl you are using)
Not a CODE reference at ... Undefined subroutine &main::47 called ...
The variable $ref may have referred to the subroutine "fred" whenever the call to "SaveSub1" was made but by the time "CallSavedSub1" gets called it now holds the number 47. Because we saved only a pointer to the original SV in "SaveSub1", any changes to $ref will be tracked by the pointer "rememberSub". This means that whenever "CallSavedSub1" gets called, it will attempt to execute the code which is referenced by the SV* "rememberSub". In this case though, it now refers to the integer 47, so expect Perl to complain loudly.
A similar but more subtle problem is illustrated with this code
$ref = \&fred; SaveSub1($ref); $ref = \&joe; CallSavedSub1();
This time whenever "CallSavedSub1" get called it will execute the Perl subroutine "joe" (assuming it exists) rather than "fred" as was originally requested in the call to "SaveSub1".
To get around these problems it is necessary to take a full copy of the SV. The code below shows "SaveSub2" modified to do that
static SV * keepSub = (SV*)NULL; void SaveSub2(name) SV * name CODE: /* Take a copy of the callback */ if (keepSub == (SV*)NULL) /* First time, so create a new SV */ keepSub = newSVsv(name); else /* Been here before, so overwrite */ SvSetSV(keepSub, name); void CallSavedSub2() CODE: PUSHMARK(SP); call_sv(keepSub, G_DISCARD|G_NOARGS);
To avoid creating a new SV every time "SaveSub2" is called, the function first checks to see if it has been called before. If not, then space for a new SV is allocated and the reference to the Perl subroutine, "name" is copied to the variable "keepSub" in one operation using "newSVsv". Thereafter, whenever "SaveSub2" is called the existing SV, "keepSub", is overwritten with the new value using "SvSetSV".
Using call_argv
Here is a Perl subroutine which prints whatever parameters are passed to it.
sub PrintList { my(@list) = @_; foreach (@list) { print "$_\n" } }
and here is an example of call_argv which will call PrintList.
static char * words[] = {"alpha", "beta", "gamma", "delta", NULL}; static void call_PrintList() { dSP; call_argv("PrintList", G_DISCARD, words); }
Note that it is not necessary to call "PUSHMARK" in this instance. This is because call_argv will do it for you.
Using call_method
Consider the following Perl code
{ package Mine; sub new { my($type) = shift; bless [@_] } sub Display { my ($self, $index) = @_; print "$index: $$self[$index]\n"; } sub PrintID { my($class) = @_; print "This is Class $class version 1.0\n"; } }
It implements just a very simple class to manage an array. Apart from the constructor, "new", it declares methods, one static and one virtual. The static method, "PrintID", prints out simply the class name and a version number. The virtual method, "Display", prints out a single element of the array. Here is an all Perl example of using it.
$a = Mine->new('red', 'green', 'blue'); $a->Display(1); Mine->PrintID;
will print
1: green This is Class Mine version 1.0
Calling a Perl method from C is fairly straightforward. The following things are required
- *
- a reference to the object for a virtual method or the name of the class for a static method.
- *
- the name of the method.
- *
- any other parameters specific to the method.
Here is a simple XSUB which illustrates the mechanics of calling both the "PrintID" and "Display" methods from C.
void call_Method(ref, method, index) SV * ref char * method int index CODE: PUSHMARK(SP); XPUSHs(ref); XPUSHs(sv_2mortal(newSViv(index))); PUTBACK; call_method(method, G_DISCARD); void call_PrintID(class, method) char * class char * method CODE: PUSHMARK(SP); XPUSHs(sv_2mortal(newSVpv(class, 0))); PUTBACK; call_method(method, G_DISCARD);
So the methods "PrintID" and "Display" can be invoked like this
$a = Mine->new('red', 'green', 'blue'); call_Method($a, 'Display', 1); call_PrintID('Mine', 'PrintID');
The only thing to note is that in both the static and virtual methods, the method name is not passed via the stack---it is used as the first parameter to call_method.
Using GIMME_V
Here is a trivial XSUB which prints the context in which it is currently executing.
void PrintContext() CODE: I32 gimme = GIMME_V; if (gimme == G_VOID) printf ("Context is Void\n"); else if (gimme == G_SCALAR) printf ("Context is Scalar\n"); else printf ("Context is Array\n");
and here is some Perl to test it
PrintContext; $a = PrintContext; @a = PrintContext;
The output from that will be
Context is Void Context is Scalar Context is Array
Using Perl to dispose of temporaries
In the examples given to date, any temporaries created in the callback (i.e., parameters passed on the stack to the call_* function or values returned via the stack) have been freed by one of these methods- *
- specifying the G_DISCARD flag with call_*.
- *
- explicitly disposed of using the "ENTER"/"SAVETMPS" - "FREETMPS"/"LEAVE" pairing.
There is another method which can be used, namely letting Perl do it for you automatically whenever it regains control after the callback has terminated. This is done by simply not using the
ENTER; SAVETMPS; ... FREETMPS; LEAVE;
sequence in the callback (and not, of course, specifying the G_DISCARD flag).
If you are going to use this method you have to be aware of a possible memory leak which can arise under very specific circumstances. To explain these circumstances you need to know a bit about the flow of control between Perl and the callback routine.
The examples given at the start of the document (an error handler and an event driven program) are typical of the two main sorts of flow control that you are likely to encounter with callbacks. There is a very important distinction between them, so pay attention.
In the first example, an error handler, the flow of control could be as follows. You have created an interface to an external library. Control can reach the external library like this
perl --> XSUB --> external library
Whilst control is in the library, an error condition occurs. You have previously set up a Perl callback to handle this situation, so it will get executed. Once the callback has finished, control will drop back to Perl again. Here is what the flow of control will be like in that situation
perl --> XSUB --> external library ... error occurs ... external library --> call_* --> perl | perl <-- XSUB <-- external library <-- call_* <----+
After processing of the error using call_* is completed, control reverts back to Perl more or less immediately.
In the diagram, the further right you go the more deeply nested the scope is. It is only when control is back with perl on the extreme left of the diagram that you will have dropped back to the enclosing scope and any temporaries you have left hanging around will be freed.
In the second example, an event driven program, the flow of control will be more like this
perl --> XSUB --> event handler ... event handler --> call_* --> perl | event handler <-- call_* <----+ ... event handler --> call_* --> perl | event handler <-- call_* <----+ ... event handler --> call_* --> perl | event handler <-- call_* <----+
In this case the flow of control can consist of only the repeated sequence
event handler --> call_* --> perl
for practically the complete duration of the program. This means that control may never drop back to the surrounding scope in Perl at the extreme left.
So what is the big problem? Well, if you are expecting Perl to tidy up those temporaries for you, you might be in for a long wait. For Perl to dispose of your temporaries, control must drop back to the enclosing scope at some stage. In the event driven scenario that may never happen. This means that as time goes on, your program will create more and more temporaries, none of which will ever be freed. As each of these temporaries consumes some memory your program will eventually consume all the available memory in your system---kapow!
So here is the bottom line---if you are sure that control will revert back to the enclosing Perl scope fairly quickly after the end of your callback, then it isn't absolutely necessary to dispose explicitly of any temporaries you may have created. Mind you, if you are at all uncertain about what to do, it doesn't do any harm to tidy up anyway.
Strategies for storing Callback Context Information
Potentially one of the trickiest problems to overcome when designing a callback interface can be figuring out how to store the mapping between the C callback function and the Perl equivalent.To help understand why this can be a real problem first consider how a callback is set up in an all C environment. Typically a C API will provide a function to register a callback. This will expect a pointer to a function as one of its parameters. Below is a call to a hypothetical function "register_fatal" which registers the C function to get called when a fatal error occurs.
register_fatal(cb1);
The single parameter "cb1" is a pointer to a function, so you must have defined "cb1" in your code, say something like this
static void cb1() { printf ("Fatal Error\n"); exit(1); }
Now change that to call a Perl subroutine instead
static SV * callback = (SV*)NULL; static void cb1() { dSP; PUSHMARK(SP); /* Call the Perl sub to process the callback */ call_sv(callback, G_DISCARD); } void register_fatal(fn) SV * fn CODE: /* Remember the Perl sub */ if (callback == (SV*)NULL) callback = newSVsv(fn); else SvSetSV(callback, fn); /* register the callback with the external library */ register_fatal(cb1);
where the Perl equivalent of "register_fatal" and the callback it registers, "pcb1", might look like this
# Register the sub pcb1 register_fatal(\&pcb1); sub pcb1 { die "I'm dying...\n"; }
The mapping between the C callback and the Perl equivalent is stored in the global variable "callback".
This will be adequate if you ever need to have only one callback registered at any time. An example could be an error handler like the code sketched out above. Remember though, repeated calls to "register_fatal" will replace the previously registered callback function with the new one.
Say for example you want to interface to a library which allows asynchronous file i/o. In this case you may be able to register a callback whenever a read operation has completed. To be of any use we want to be able to call separate Perl subroutines for each file that is opened. As it stands, the error handler example above would not be adequate as it allows only a single callback to be defined at any time. What we require is a means of storing the mapping between the opened file and the Perl subroutine we want to be called for that file.
Say the i/o library has a function "asynch_read" which associates a C function "ProcessRead" with a file handle "fh"--this assumes that it has also provided some routine to open the file and so obtain the file handle.
asynch_read(fh, ProcessRead)
This may expect the C ProcessRead function of this form
void ProcessRead(fh, buffer) int fh; char * buffer; { ... }
To provide a Perl interface to this library we need to be able to map between the "fh" parameter and the Perl subroutine we want called. A hash is a convenient mechanism for storing this mapping. The code below shows a possible implementation
static HV * Mapping = (HV*)NULL; void asynch_read(fh, callback) int fh SV * callback CODE: /* If the hash doesn't already exist, create it */ if (Mapping == (HV*)NULL) Mapping = newHV(); /* Save the fh -> callback mapping */ hv_store(Mapping, (char*)&fh, sizeof(fh), newSVsv(callback), 0); /* Register with the C Library */ asynch_read(fh, asynch_read_if);
and "asynch_read_if" could look like this
static void asynch_read_if(fh, buffer) int fh; char * buffer; { dSP; SV ** sv; /* Get the callback associated with fh */ sv = hv_fetch(Mapping, (char*)&fh , sizeof(fh), FALSE); if (sv == (SV**)NULL) croak("Internal error...\n"); PUSHMARK(SP); XPUSHs(sv_2mortal(newSViv(fh))); XPUSHs(sv_2mortal(newSVpv(buffer, 0))); PUTBACK; /* Call the Perl sub */ call_sv(*sv, G_DISCARD); }
For completeness, here is "asynch_close". This shows how to remove the entry from the hash "Mapping".
void asynch_close(fh) int fh CODE: /* Remove the entry from the hash */ (void) hv_delete(Mapping, (char*)&fh, sizeof(fh), G_DISCARD); /* Now call the real asynch_close */ asynch_close(fh);
So the Perl interface would look like this
sub callback1 { my($handle, $buffer) = @_; } # Register the Perl callback asynch_read($fh, \&callback1); asynch_close($fh);
The mapping between the C callback and Perl is stored in the global hash "Mapping" this time. Using a hash has the distinct advantage that it allows an unlimited number of callbacks to be registered.
What if the interface provided by the C callback doesn't contain a parameter which allows the file handle to Perl subroutine mapping? Say in the asynchronous i/o package, the callback function gets passed only the "buffer" parameter like this
void ProcessRead(buffer) char * buffer; { ... }
Without the file handle there is no straightforward way to map from the C callback to the Perl subroutine.
In this case a possible way around this problem is to predefine a series of C functions to act as the interface to Perl, thus
#define MAX_CB 3 #define NULL_HANDLE -1 typedef void (*FnMap)(); struct MapStruct { FnMap Function; SV * PerlSub; int Handle; }; static void fn1(); static void fn2(); static void fn3(); static struct MapStruct Map [MAX_CB] = { { fn1, NULL, NULL_HANDLE }, { fn2, NULL, NULL_HANDLE }, { fn3, NULL, NULL_HANDLE } }; static void Pcb(index, buffer) int index; char * buffer; { dSP; PUSHMARK(SP); XPUSHs(sv_2mortal(newSVpv(buffer, 0))); PUTBACK; /* Call the Perl sub */ call_sv(Map[index].PerlSub, G_DISCARD); } static void fn1(buffer) char * buffer; { Pcb(0, buffer); } static void fn2(buffer) char * buffer; { Pcb(1, buffer); } static void fn3(buffer) char * buffer; { Pcb(2, buffer); } void array_asynch_read(fh, callback) int fh SV * callback CODE: int index; int null_index = MAX_CB; /* Find the same handle or an empty entry */ for (index = 0; index < MAX_CB; ++index) { if (Map[index].Handle == fh) break; if (Map[index].Handle == NULL_HANDLE) null_index = index; } if (index == MAX_CB && null_index == MAX_CB) croak ("Too many callback functions registered\n"); if (index == MAX_CB) index = null_index; /* Save the file handle */ Map[index].Handle = fh; /* Remember the Perl sub */ if (Map[index].PerlSub == (SV*)NULL) Map[index].PerlSub = newSVsv(callback); else SvSetSV(Map[index].PerlSub, callback); asynch_read(fh, Map[index].Function); void array_asynch_close(fh) int fh CODE: int index; /* Find the file handle */ for (index = 0; index < MAX_CB; ++ index) if (Map[index].Handle == fh) break; if (index == MAX_CB) croak ("could not close fh %d\n", fh); Map[index].Handle = NULL_HANDLE; SvREFCNT_dec(Map[index].PerlSub); Map[index].PerlSub = (SV*)NULL; asynch_close(fh);
In this case the functions "fn1", "fn2", and "fn3" are used to remember the Perl subroutine to be called. Each of the functions holds a separate hard-wired index which is used in the function "Pcb" to access the "Map" array and actually call the Perl subroutine.
There are some obvious disadvantages with this technique.
Firstly, the code is considerably more complex than with the previous example.
Secondly, there is a hard-wired limit (in this case 3) to the number of callbacks that can exist simultaneously. The only way to increase the limit is by modifying the code to add more functions and then recompiling. None the less, as long as the number of functions is chosen with some care, it is still a workable solution and in some cases is the only one available.
To summarize, here are a number of possible methods for you to consider for storing the mapping between C and the Perl callback
- 1. Ignore the problem - Allow only 1 callback
- For a lot of situations, like interfacing to an error handler, this may be a perfectly adequate solution.
- 2. Create a sequence of callbacks - hard wired limit
- If it is impossible to tell from the parameters passed back from the C callback what the context is, then you may need to create a sequence of C callback interface functions, and store pointers to each in an array.
- 3. Use a parameter to map to the Perl callback
- A hash is an ideal mechanism to store the mapping between C and Perl.
Alternate Stack Manipulation
Although I have made use of only the "POP*" macros to access values returned from Perl subroutines, it is also possible to bypass these macros and read the stack using the "ST" macro (See perlxs for a full description of the "ST" macro).Most of the time the "POP*" macros should be adequate, the main problem with them is that they force you to process the returned values in sequence. This may not be the most suitable way to process the values in some cases. What we want is to be able to access the stack in a random order. The "ST" macro as used when coding an XSUB is ideal for this purpose.
The code below is the example given in the section Returning a list of values recoded to use "ST" instead of "POP*".
static void call_AddSubtract2(a, b) int a; int b; { dSP; I32 ax; int count; ENTER; SAVETMPS; PUSHMARK(SP); XPUSHs(sv_2mortal(newSViv(a))); XPUSHs(sv_2mortal(newSViv(b))); PUTBACK; count = call_pv("AddSubtract", G_ARRAY); SPAGAIN; SP -= count; ax = (SP - PL_stack_base) + 1; if (count != 2) croak("Big trouble\n"); printf ("%d + %d = %d\n", a, b, SvIV(ST(0))); printf ("%d - %d = %d\n", a, b, SvIV(ST(1))); PUTBACK; FREETMPS; LEAVE; }
Notes
- 1.
- Notice that it was necessary to define the variable "ax". This is because the "ST" macro expects it to exist. If we were in an XSUB it would not be necessary to define "ax" as it is already defined for you.
- 2.
-
The code
SPAGAIN; SP -= count; ax = (SP - PL_stack_base) + 1;
sets the stack up so that we can use the "ST" macro.
- 3.
- Unlike the original coding of this example, the returned values are not accessed in reverse order. So ST(0) refers to the first value returned by the Perl subroutine and "ST(count-1)" refers to the last.
Creating and calling an anonymous subroutine in C
As we've already shown, "call_sv" can be used to invoke an anonymous subroutine. However, our example showed a Perl script invoking an XSUB to perform this operation. Let's see how it can be done inside our C code:
... SV *cvrv = eval_pv("sub { print 'You will not find me cluttering any namespace!' }", TRUE); ... call_sv(cvrv, G_VOID|G_NOARGS);
"eval_pv" is used to compile the anonymous subroutine, which will be the return value as well (read more about "eval_pv" in ``eval_pv'' in perlapi). Once this code reference is in hand, it can be mixed in with all the previous examples we've shown.
LIGHTWEIGHT CALLBACKS
Sometimes you need to invoke the same subroutine repeatedly. This usually happens with a function that acts on a list of values, such as Perl's built-in sort(). You can pass a comparison function to sort(), which will then be invoked for every pair of values that needs to be compared. The first() and reduce() functions from List::Util follow a similar pattern.In this case it is possible to speed up the routine (often quite substantially) by using the lightweight callback API. The idea is that the calling context only needs to be created and destroyed once, and the sub can be called arbitrarily many times in between.
It is usual to pass parameters using global variables --- typically $_ for one parameter, or $a and $b for two parameters --- rather than via @_. (It is possible to use the @_ mechanism if you know what you're doing, though there is as yet no supported API for it. It's also inherently slower.)
The pattern of macro calls is like this:
dMULTICALL; /* Declare local variables */ I32 gimme = G_SCALAR; /* context of the call: G_SCALAR, * G_LIST, or G_VOID */ PUSH_MULTICALL(cv); /* Set up the context for calling cv, and set local vars appropriately */ /* loop */ { /* set the value(s) af your parameter variables */ MULTICALL; /* Make the actual call */ } /* end of loop */ POP_MULTICALL; /* Tear down the calling context */
For some concrete examples, see the implementation of the first() and reduce() functions of List::Util 1.18. There you will also find a header file that emulates the multicall API on older versions of perl.
SEE ALSO
perlxs, perlguts, perlembedAUTHOR
Paul MarquessSpecial thanks to the following people who assisted in the creation of the document.
Jeff Okamoto, Tim Bunce, Nick Gianniotis, Steve Kelem, Gurusamy Sarathy and Larry Wall.
DATE
Version 1.3, 14th Apr 1997
Index
- NAME
- DESCRIPTION
- THE CALL_ FUNCTIONS
- FLAG VALUES
- EXAMPLES
-
- No Parameters, Nothing returned
- Passing Parameters
- Returning a Scalar
- Returning a list of values
- Returning a list in a scalar context
- Returning Data from Perl via the parameter list
- Using G_EVAL
- Using G_KEEPERR
- Using call_sv
- Using call_argv
- Using call_method
- Using GIMME_V
- Using Perl to dispose of temporaries
- Strategies for storing Callback Context Information
- Alternate Stack Manipulation
- Creating and calling an anonymous subroutine in C
- LIGHTWEIGHT CALLBACKS
- SEE ALSO
- AUTHOR
- DATE
This document was created by man2html, using the manual pages.
Time: 05:29:07 GMT, December 24, 2015


If you need assistance with your travel arrangements, please give us a call at<PHONE_NUMBER>. We will have one of our travel specialists work with you to plan your trip.
Your satisfaction is our goal, so we only hire the best travel agents to work with our resort. Our specialists will find out what you are interested in experiencing on your vacation, and then they will work hard to make sure that your expectations are realized.
Come and visit us at Private Island Resort soon!
Back To Home


Time to clear that Rat Nest of yours and make some $$$!


Not a port of entry. Make sure you check in/out from one of the 4 ports of entry in Vanuatu on Efate, Santo, Banks and Tanna Islands.
Asanvari Bay is the calmest anchorage on Maewo. The anchorage is well protected from tradewinds (open to NW to SW winds). Anchor over rock and coral in 30 to 60 feet. You can land your dinghy ashore in front of the yacht club. A small dinghy channel is marked by 2 range posts ashore and a green LED light at night.
Chief Nelson and son Nixon welcomed yachts here for many years. Earlier cruisers helped them get foreign aid to build a proper Yacht Club and to install a small hydro-electric generator near the Bay's waterfall. However sadly the Chief and yacht club are no more. There are plans to rebuild it.
Last updated May 2016.


Please fill in the required information to create an account.
Name cannot be empty
Date of Birth cannot be empty
Invalid date of Birth
Please select gender
Telephone cannot be empty
Invalid telephone number
please select designation
email address cannot be empty
password cannot be empty
Password cannot be empty
Password do not match
Already have an account?Sign in


|
| template<typename TNumeric > |
| constexpr TNumeric | IntegerPower (TNumeric base, std::size_t exponent) noexcept |
| | Raise any base to an integer power. More...
|
| |
| constexpr double | ComputeGeometricSum (double coefficient, double base, std::size_t max_terms) noexcept |
| | Compute the sum of the first n terms of a geometric series. More...
|
| |
Compile-time Application
Utilities for performing calculations and logic at compile time to help with template programming.
◆ ComputeGeometricSum()
| constexpr double Kratos::ComputeGeometricSum |
( |
double |
coefficient, |
|
|
double |
base, |
|
|
std::size_t |
max_terms |
|
) |
| |
|
constexprnoexcept |
Compute the sum of the first n terms of a geometric series.
Compute the following expression:
\[ c \cdot \sum_{k=0}^n q^k \]
- Parameters
-
| coefficient | (c) coefficient multiplying each term of the series. |
| base | (q) base of the geometric series. |
| max_terms | (n) number of terms to sum up. |
- Note
- the classic reduced formula is used to compute the sum, unless
base
is 1
. Power calculation is deferred to IntegerPower<double> which is less efficient than std::pow
but can be invoked at compile time and does not throw exceptions.
- Warning
- be wary of floating point overflows.
◆ IntegerPower()
| constexpr TNumeric Kratos::IntegerPower |
( |
TNumeric |
base, |
|
|
std::size_t |
exponent |
|
) |
| |
|
constexprnoexcept |
Raise any base to an integer power.
Compute \(a^n\).
- Template Parameters
-
| TNumeric | base type; can be any integer or floating point type (example: int or double ). |
- Parameters
-
| base | base to be raised to a power. |
| exponent | multiply base by itself this many times |
- Note
- this function can be invoked at compile time, and is guaranteed no to throw an exception.


Plan
The plan is too costly and I am frustrated. Even operators like T-Mobile are offering better plans
Change Plan
Bill Details


|
WiseLoop JavaScript Premium Weather Widget 2.1.1
Weather Condition & Forecast Script
|
Copy the entire /javascript-premium-weather-widget directory on your web server. The directory is included in the downloaded archive.
Include the /javascript-premium-weather-widget/bins/wl-ng-weather.js in your page.
The script has AngularJS, bootstrap.css, skycons and google maps API as dependencies, so they should be included also.
The paths are relative to your current HTML page, so please pay attention to that.
<link href="/javascript-premium-weather-widget/bins/lib/bootstrap/css/bootstrap.min.css" rel="stylesheet"/>
The weather widget is shown by adding a div as below:

In order to configure the script properly, please visit https://developer.forecast.io to get a forecast.io API key. Registration is free, very easy and you get 1000 free API calls per day. After getting the key, just replace the your-developer.forecast.io-key string with your actual key.
Also, the module needs to know where its files are located. Add the following code at the end of your HTML page but replace the path to your actual path relative to the HTML page:

For instance, if you have a file structure like:
Then, index.html should look like:
  <link rel="stylesheet" href="../bins/lib/bootstrap/css/bootstrap.min.css"/>


protein viral host RNA virus human proteins cells segment influenza avian infection strain Pan splicing using splice Mal synthesis (Fig. mRNA IAV site strains differences structure data region secondary SILAC sequences {border-style infection. used expression infected observed production pulse px;} #ffffff;} Fig. different gene conserved human-adapted produced sequence viruses based bird-adapted level time Thus, levels performed reporter samples wild-type Data following labeling non-permissive mM Supplementary assess avian-adapted biological impaired important mammalian medium range similar AG, GA, analysis cis-regulatory containing indicated permissive replicates subjected analyzed cell cells. changes corresponding experiments factors global junction nuclear polymerase proteins. ratios reduced shutoff Cells high individual newly n = profiles proteomic quantification quantified relative strains. synthesized AHA However, LINK comparing constructs dynamic enrichment evolutionary export increased input nucleotides overall pSILAC predicted proteome px; role species spliced splicing. structures supplemented values {font-family Also, DNA [], according amino average buffer cellular channel depicted. described element font-size iBAQ identify infection, known matrix normalized peptides replication scans seasonal specific total transfected translation min (Supplementary (i.e., (nucleotides Importantly, Moreover, Pan-Av Pan/Mal RNA-Decoder RNA-seq activity b). binding c). chimeric coding computational conclude consistent contrast, directly double; elements end, evolutionarily factor generated grown identified information isoforms kinetics later mRNAs manufacturer’s markedly model pAHA-SILAC pHW-Mal pandemic post reads reads. relevant strain-specific target virus, vitro – h (HN) (clone (lane HEKT Hence, IAVs. Influenza Interestingly, Research Then, absolute adaptation agarose alignments antibody border-color border-width bovine common construct control data. database determinant. difference dynamics early encoded example, exclude features findings genome investigate investigated ion labeled maximum mechanisms novel novo primary quantify quantitative recent replicate required results segments sequencing showed solid; stages strain. transcript transcription type value vs. {font-style {font-weight (ATCC (GenBank (Pan) (Thermo (e.g., (see . M Acids B.B. Cell. Commons Creative Fisher) IAVs MS/MS PB, Peptides Protein Proteins Proteome Q-Exactive RNA-sequencing RdRP accession: acids adaptation. alternative analyses attB available base bold calculated causes chicken cloned compared complete consensus controls courier; d). data-dependent date decreased denaturing depend does efficiencies efficiency em; encoding essential experimental extracted fetal files fused higher human- included incubated inefficiently infections injection interferon late lysis material mode. molecular multiple mutated mutations number observe particularly pattern peptide period pies play point points provides pt;} ratio replicates. replication. respective reverse run selected set shared shutoff. signals significance software source specificity stained strains, striking supervised temporal view virus. washed °C °C.


Google Doodle honors Will Rogers on his 140th birthday
by Kyle BradshawIn honor of Native American Indian Heritage Month, Google is displaying a homepage Doodle featuring Cherokee actor Will Rogers.
Born on this day in 1879, Will Rogers was, among many other things, an actor, columnist, and the spitting image of what most picture a cowboy to look like. His horse-riding and rope lassoing tricks combined with his intelligent writing and ever-kind heart cemented Rogers as an American icon.
To truly understand who Will Rogers was and the full impact he had on our culture — and especially that of the Cherokee Nation — be sure to check out a recent Google Arts & Culture gallery created in his honor.
This morning’s animated homepage Doodle is a perfect homage to Will Rogers’ fame as a multi-talented multi-tasker, as it features him writing while lassoing and laying on a galloping horse. While this combination of tasks may seem absurd, Google shared some photos from the Rogers’ estate, including a stunning image of Will spinning a lasso while penning something.
The Doodle was created by San Francisco artist Kevin Laughlin in partnership with the Will Rogers Memorial. When asked what inspires him about Rogers’ life, Laughlin shared his favorite quote, which speaks to the core of who Rogers was.
I deeply admire people who are able to maintain a positive view of others around them in a time of adversity. To be able to see an inherent good in everyone, enough at least to have uttered the phrase, “I never met a man I didn’t like,” Will left behind a philosophy worth aspiring to, indeed.
Laughlin shared two early drafts of today’s Doodle, which appear to have been combined to form the final image seen on the homepage.
Elsewhere in the world today, residents of Colombia are treated to a Doodle honoring anthropologist Virginia Gutíerrez de Pineda’s 98th birthday. Pineda’s efforts and research played a major role in positively reshaping the family structures of Colombia.
FTC: We use income earning auto affiliate links. More.


Filerobot Uploader
Share Your Images in Seconds!
The Filerobot Uploader is a multi-function Uploader that will make uploads super easy on your web and mobile applications. With few lines of code, you will get a state of the art Uploader and enable your users to upload media, files and any assets via Filerobot's reverse CDN. Files are stored into scalable and flexible Cloud storage, optimized and delivered over CDN to your end users rocket fast. Features include inline image editing, auto-tagging, auto-cropping and many more.
- File name: placeholder
- Public link: https://cdn.scaleflex.it/filerobot/assets/no-image-icon.png
- Size: 28.8 KB
- First Uploaded: Monday, Jan 28, 2019, 7:53 PM
- Last Modified: Monday, Jan 28, 2019, 7:53 PM
- Description: Placeholder icon
- Tags: placeholder, icon, image icon
Ready to get started?
To use the plugin, you will need a Filerobot token. Don't worry, it only takes seconds to get one by registering here. Once your token is created, you can configure it as described below. This token allows you to use 25GB of image cache and 25GB of worldwide CDN traffic per month for free.
Include the following script into your project
Initialize Filerobot Uploader
Get your Filerobot tokens here.
Open Filerobot Uploader
…and you're done! Visit the full documentation here.
Any questions?
Contact us at<EMAIL_ADDRESS>our experts will be happy to help!


Hello
one paragraph
label
te
xt
x
2
<0
α >30°
Lists
Forms
Image 1 & image 2
Image 1
Image 2
link to label
download http
-
download ftp
Contact


torchvision.io¶
The torchvision.io
package provides functions for performing IO
operations. They are currently specific to reading and writing video and
images.
Video¶
-
torchvision.io.
read_video
(filename: str, start_pts: int = 0, end_pts: Optional[float] = None, pts_unit: str = 'pts') → Tuple[torch.Tensor, torch.Tensor, Dict[str, Any]][source]¶ Reads a video from a file, returning both the video frames as well as the audio frames
- Parameters
filename (str) – path to the video file
start_pts (int if pts_unit = 'pts', optional) – float / Fraction if pts_unit = ‘sec’, optional the start presentation time of the video
end_pts (int if pts_unit = 'pts', optional) – float / Fraction if pts_unit = ‘sec’, optional the end presentation time
pts_unit (str, optional) – unit in which start_pts and end_pts values will be interpreted, either ‘pts’ or ‘sec’. Defaults to ‘pts’.
- Returns
vframes (Tensor[T, H, W, C]) – the T video frames
aframes (Tensor[K, L]) – the audio frames, where K is the number of channels and L is the number of points
info (Dict) – metadata for the video and audio. Can contain the fields video_fps (float) and audio_fps (int)
-
torchvision.io.
read_video_timestamps
(filename: str, pts_unit: str = 'pts') → Tuple[List[int], Optional[float]][source]¶ List the video frames timestamps.
Note that the function decodes the whole video frame-by-frame.
- Parameters
- Returns
pts (List[int] if pts_unit = ‘pts’) – List[Fraction] if pts_unit = ‘sec’ presentation timestamps for each one of the frames in the video.
video_fps (float, optional) – the frame rate for the video
Fine-grained video API¶
In addition to the read_video
function, we provide a high-performance
lower-level API for more fine-grained control compared to the read_video
function.
It does all this whilst fully supporting torchscript.
-
class
torchvision.io.
VideoReader
(path, stream='video')[source]¶ Fine-grained video-reading API. Supports frame-by-frame reading of various streams from a single video container.
Example
The following examples creates a
VideoReader
object, seeks into 2s point, and returns a single frame:import torchvision video_path = "path_to_a_test_video" reader = torchvision.io.VideoReader(video_path, "video") reader.seek(2.0) frame = next(reader)
VideoReader
implements the iterable API, which makes it suitable to using it in conjunction withitertools
for more advanced reading. As such, we can use aVideoReader
instance inside for loops:reader.seek(2) for frame in reader: frames.append(frame['data']) # additionally, `seek` implements a fluent API, so we can do for frame in reader.seek(2): frames.append(frame['data'])
With
itertools
, we can read all frames between 2 and 5 seconds with the following code:for frame in itertools.takewhile(lambda x: x['pts'] <= 5, reader.seek(2)): frames.append(frame['data'])
and similarly, reading 10 frames after the 2s timestamp can be achieved as follows:
for frame in itertools.islice(reader.seek(2), 10): frames.append(frame['data'])
Note
Each stream descriptor consists of two parts: stream type (e.g. ‘video’) and a unique stream id (which are determined by the video encoding). In this way, if the video contaner contains multiple streams of the same type, users can acces the one they want. If only stream type is passed, the decoder auto-detects first stream of that type.
- Parameters
path (string) – Path to the video file in supported format
stream (string, optional) – descriptor of the required stream, followed by the stream id, in the format
{stream_type}:{stream_id}
. Defaults to"video:0"
. Currently available options include['video', 'audio']
-
__next__
()[source]¶ Decodes and returns the next frame of the current stream
- Returns
a dictionary with fields
data
andpts
containing decoded frame and corresponding timestamp- Return type
(dict)
-
get_metadata
()[source]¶ Returns video metadata
- Returns
dictionary containing duration and frame rate for every stream
- Return type
(dict)
-
seek
(time_s: float)[source]¶ Seek within current stream.
- Parameters
time_s (float) – seek time in seconds
Note
Current implementation is the so-called precise seek. This means following seek, call to
next()
will return the frame with the exact timestamp if it exists or the first frame with timestamp larger thantime_s
.
-
set_current_stream
(stream: str)[source]¶ Set current stream. Explicitly define the stream we are operating on.
- Parameters
stream (string) – descriptor of the required stream. Defaults to
"video:0"
Currently available stream types include['video', 'audio']
. Each descriptor consists of two parts: stream type (e.g. ‘video’) and a unique stream id (which are determined by video encoding). In this way, if the video contaner contains multiple streams of the same type, users can acces the one they want. If only stream type is passed, the decoder auto-detects first stream of that type and returns it.- Returns
True on succes, False otherwise
- Return type
(bool)
Example of inspecting a video:
import torchvision
video_path = "path to a test video"
# Constructor allocates memory and a threaded decoder
# instance per video. At the momet it takes two arguments:
# path to the video file, and a wanted stream.
reader = torchvision.io.VideoReader(video_path, "video")
# The information about the video can be retrieved using the
# `get_metadata()` method. It returns a dictionary for every stream, with
# duration and other relevant metadata (often frame rate)
reader_md = reader.get_metadata()
# metadata is structured as a dict of dicts with following structure
# {"stream_type": {"attribute": [attribute per stream]}}
#
# following would print out the list of frame rates for every present video stream
print(reader_md["video"]["fps"])
# we explicitly select the stream we would like to operate on. In
# the constructor we select a default video stream, but
# in practice, we can set whichever stream we would like
video.set_current_stream("video:0")
Image¶
-
torchvision.io.
read_image
(path: str) → torch.Tensor[source]¶ Reads a JPEG or PNG image into a 3 dimensional RGB Tensor. The values of the output tensor are uint8 between 0 and 255.
-
torchvision.io.
decode_image
(input: torch.Tensor) → torch.Tensor[source]¶ Detects whether an image is a JPEG or PNG and performs the appropriate operation to decode the image into a 3 dimensional RGB Tensor.
The values of the output tensor are uint8 between 0 and 255.
-
torchvision.io.
encode_jpeg
(input: torch.Tensor, quality: int = 75) → torch.Tensor[source]¶ Takes an input tensor in CHW layout and returns a buffer with the contents of its corresponding JPEG file.
- Parameters
- Returns
output – A one dimensional int8 tensor that contains the raw bytes of the JPEG file.
- Return type
Tensor[1]
-
torchvision.io.
write_jpeg
(input: torch.Tensor, filename: str, quality: int = 75)[source]¶ Takes an input tensor in CHW layout and saves it in a JPEG file.
-
torchvision.io.
encode_png
(input: torch.Tensor, compression_level: int = 6) → torch.Tensor[source]¶ Takes an input tensor in CHW layout and returns a buffer with the contents of its corresponding PNG file.
- Parameters
- Returns
output – A one dimensional int8 tensor that contains the raw bytes of the PNG file.
- Return type
Tensor[1]


DeviceModelable
Undocumented
-
Undocumented
-
presentation
Default implementationUndocumented
Default Implementation
Undocumented
-
Undocumented
-
Undocumented
-
Undocumented
-
writeState
Default implementationUndocumented
Default Implementation
Undocumented
-
Undocumented
-
Undocumented
-
Undocumented
-
Undocumented
-
Undocumented
-
otaProgress
Default implementationUndocumented
Default Implementation
Undocumented
-
Undocumented
-
notifyViewing(_:)
Default implementationUndocumented
Default Implementation
Undocumented
-
valueForSystemAttribute(_:)
Extension methodUndocumented
-
hachiState
Extension methodUndocumented
-
actions
Extension methodRepresentation of the device’s current attribute as a
DeviceRuleAction
object. On implementors that support it, this may instigate signal emission. For example, settingaction
on aDeviceModel
instance will result in anDeviceEvent.AttributeUpdate(DeviceState)
event being sent.Setting this value will cause the existing attribute state to be completely replaced by an attribute state derived from all
DeviceActions
whosedeviceId
matches our own, applied in array index order.Declaration
Swift
var actions: [DeviceRuleAction]
-
setOperation(_:forAttributeId:)
Extension methodUndocumented
-
operationForAttributeId(_:)
Extension methodUndocumented
-
update(_:accumulative:)
Extension methodIf
filterCriterion.deviceId
==self.id
, set (or optionally overlay) this modelable’s state to that indicated by the givenDeviceFilterCriterion
. IffilterCriterion.deviceId
≠self.id
, then do nothing.Important
By default, this does NOT overlay the current state
Declaration
Swift
public func update(_ filterCriterion: DeviceFilterCriterion, accumulative: Bool = false)
Parameters
filterCriterion
The filterCriterion from which to pull attribute state
accumulative
Whether or not to overlay the current device state. Defaults to false.
-
filterCriteria
Extension methodThis device’s state as an array of filterCriteria, with
trigger
andoperation
values set to their defaults forDeviceFilterCriterion
.Important
Note thattrigger
andoperation
values are replaced with their respective defaults when round-tripping, so this is not full-fidelity storage for filter criteria.Important
Setting this will not overlay the current state, but rather will successively replace it.Declaration
Swift
public var filterCriteria: [DeviceFilterCriterion]
-
TAG
Extension methodUndocumented
-
displayName
Extension methodUndocumented
-
readableAttributes
Extension methodUndocumented
-
readableAttributeIds
Extension methodUndocumented
-
hasReadableAttributes
Extension methodUndocumented
-
hasPresentableReadableAttributes
Extension methodUndocumented
-
writableAttributes
Extension methodUndocumented
-
writableAttributeIds
Extension methodUndocumented
-
hasWritableAttributes
Extension methodUndocumented
-
hasPresentableWritableAttributes
Extension methodUndocumented
-
groupIndicesForOperation(_:)
Extension methodUndocumented
-
groupsForOperation(_:)
Extension methodUndocumented
-
groupsWithWritableAttributes
Extension methodUndocumented
-
groupsWithReadableAttributes
Extension methodUndocumented
-
controlIds(_:)
Extension methodReturn all the controlIds for this device, optionally filtered per the given groupIndex.
Declaration
Swift
public func controlIds(_ groupIndex: Int? = nil) -> [Int]
-
valueForAttributeId(_:)
Extension methodFetch an attribute by id
Declaration
Swift
public func valueForAttributeId(_ attributeId: Int) -> AttributeValue?
Parameters
attributeId
The id of the attribute to fetch
-
set(value:forAttributeId:)
Extension methodUndocumented
-
set(value:forAttributeId:localOnly:)
Extension methodSet an attributeValue by id
Declaration
Swift
public func set(value: AttributeValue, forAttributeId attributeId: Int, localOnly: Bool) -> Promise<DeviceBatchAction.Results>
Parameters
value
The
AttributeValue
to setforAttributeId
The attributeId which associated with the value
localOnly
If true, the value is only written locally to the device state, and is not propogated through the service.and
Return Value
A
Promise<DeviceBatchAction.Results>
containing all request and response info. -
set(attributes:)
Extension methodUndocumented
-
set(attributes:)
Extension methodUndocumented
-
set(attributes:localOnly:)
Extension methodGiven a sequence of
(Int, AttributeValue)
pairs, apply apply them to the device.apply IflocalOnly
, then the changes are only applied locally, and may be overwritten by future incoming device updates.Declaration
Swift
public func set(attributes: [(Int, AttributeValue)], localOnly: Bool) -> Promise<DeviceBatchAction.Results>
Parameters
attributes
A sequences of
(attributeId, attributeValue)
pairs to write, in order.localOnly
If true, the value is only written locally to the device state, and is not propogated through the service.and
Return Value
A
Promise<DeviceBatchAction.Results>
containing all request and response info. -
attributeConfig(forAttributeId:)
Extension methodUndocumented
-
descriptorForAttributeId(_:)
Extension methodUndocumented
-
attributeOptionForAttributeId(_:)
Extension methodUndocumented
-
defaultValueForAttributeId(_:)
Extension methodUndocumented
-
CoderKeyId
Extension methodUndocumented
-
CoderKeyData
Extension methodUndocumented
-
CoderKeyValue
Extension methodUndocumented
-
CoderKeyAttributeId
Extension methodUndocumented
-
CoderKeyAttributes
Extension methodUndocumented
-
CoderKeyValues
Extension methodUndocumented
-
CoderKeyProfileId
Extension methodUndocumented
-
CoderKeyAvailable
Extension methodUndocumented
-
CoderKeyFriendlyName
Extension methodUndocumented
-
update(with:attrsOnly:)
Extension methodUndocumented
-
update(with:)
Extension methodUndocumented
-
update(with:)
Extension methodUndocumented
-
update(with:)
Extension methodUndocumented
-
update(_:attrsOnly:)
Extension methodUpdate the modelable’s state with the given data as provided in a
Conclave
payload.Declaration
Swift
public func update(_ deviceData: [String: Any], attrsOnly: Bool = true)
-
update(_:accumulative:)
Extension methodUpdate the current state by successively applying the given attributeInstances. If
accumulative
istrue
, then the current state will be modified. Ifaccumulative
isfalse
, then the modelable’s state will be replaced with new attributes.Declaration
Swift
public func update(_ attributeInstances: [AttributeInstance], accumulative: Bool = true)
Parameters
attributes
The array of
AttributeInstance
s to applyaccumulative
Whether or not to overlay the current device state. Defaults to true.
-
update(_:accumulative:)
Extension methodIdentical to calling
update(_: [AttributeInstance], accumulative: Bool)
with a single-element array of instances.Declaration
Swift
public func update(_ attributeInstance: AttributeInstance, accumulative: Bool = true)
-
update(_:accumulative:)
Extension methodUpdate (or optionally set) this modelable with the given attributes. If
accumulative
istrue
, then the current state will be modified. Ifaccumulative
isfalse
, then the modelable’s state will be replaced with new attributes.Declaration
Swift
public func update(_ attributes: [Int: String], accumulative: Bool = true)
Parameters
attributes
A set of attributes from which to draw device state.
accumulative
Whether or not to overlay the current device state. Defaults to true.
-
update(_:accumulative:)
Extension methodOverlay (or optoinally set) this modelable’s state to that indicated by the given
DeviceRuleAction
.Declaration
Swift
public func update(_ action: DeviceRuleAction, accumulative: Bool = true)
Parameters
filterCriterion
The filterCriterion from which to pull attribute state
accumulative
Whether or not to overlay the current device state. Defaults to true.
-
handleCommand(_:)
Extension methodUndocumented
-
write(_:completion:)
Extension methodSuccessively send write commands for members of
attributes
to the commandSink (which in turn will invokecompletion
as per.AttributeWrite
docs above.Declaration
Swift
public func write(_ attributes: [AttributeInstance?], completion: @escaping WriteAttributeOnDone = { _, _ in })
-
write(_:completion:)
Extension methodSend a write command for a single optional
AttributeInstance
Declaration
Swift
public func write(_ attribute: AttributeInstance?, completion: @escaping WriteAttributeOnDone = { _, _ in })
-
write(_:attributeValue:completion:)
Extension methodSend a write command for the given
attributeId
andattributeValue
.Declaration
Swift
public func write(_ attributeId: Int, attributeValue: AttributeValue, completion: @escaping WriteAttributeOnDone = { _, _ in })
-
write(_:value:completion:)
Extension methodSend a write command for a
Bool
value to the givenattributeId
. Note that no profile type checks are currently being done, so it’s the responsiblity of the invoker to ensure thatBool
is an appropriate type for the givenattributeId
.Declaration
Swift
public func write(_ attributeId: Int, value: Bool, completion: @escaping WriteAttributeOnDone = { _, _ in })
-
primaryOperationAttributeDescriptor
Extension methodUndocumented
-
primaryOperationValue
Extension methodUndocumented
-
primaryOperationAttributeOptions
Extension methodUndocumented
-
togglePrimaryOperation(_:)
Extension methodUndocumented
-
supportsOfflineSchedules
Extension methodUndocumented
-
types
Extension methodUndocumented
-
offlineScheduleFlags
Extension methodUndocumented
-
setOfflineScheduleFlags(_:)
Extension methodUndocumented


MoonSharp Debugger
Select which script you want to open the debugger for.
Script Name
State
Connected debuggers
Port
{0}


What is caffeine?
Caffeine is a bitter substance that occurs naturally in more than 60 plants including: Coffee beans, Tea leaves,Kola nuts: which are used to flavor soft drink colas and Cacao pods: which are used to make chocolate products.
Caffeine Health Benefits
Caffeine may have some health benefits:
Harmful Effects of Caffeine
Here are a few of the studies that concluded that caffeine could be potentially dangerous to one’s health.
Exciting Caffeine Facts


-1
-0.1
-0.01
Rotation
+0.01
+0.1
+1
-0.001
-0.01
-0.1
DPL
+0.1
+0.01
+0.001
-1
-0.1
-0.01
Offset
+0.01
+0.1
+1
Image
Save
JSON
DPL
Angle
Offset
View


My name is Cameron Ythan King. I attend school at Little Red Schoolhouse and Elisabeth Irwin High School (LREI) , located in SoHo, New York. I am a Prep for Prep and All Star Code alumn. I live in Brooklyn, New York. I consider myself an athelte, a musician, a comedian, an artist, a designer and I am an aspiring Computer Engineer.
I recently represented LREI at the White Privilege Conference in Louisville, Kentucky and help led a Black Lives Matter protest with my school. This summer, I participated in New York City's "Ladders for Leaders" program. I am an intern at Bleu Magazine, a men's fashion magazine.
Click the link to download my Resume. Here you'll find my activities, experience, education and skills all in one concise doument. Being that I'm a highschool student, I'm always learning more and opportunities keep coming my way so it's ever-changing.
Click Me!


They get enough light. So why aren't your plants as healthy or as big as you think they should be? It could be the soil. Did you know approximately 90% of plant problems are soil related? Soil is where it all begins and this course is where you begin learning about it. We will cover the physical, biological, and chemical properties of soils as well as basic plant nutrition and fertilization that will help you achieve an optimum planting and growing environment. Discussion will include soil, soil structure, how to work with different types of soils, and how to improve it. Understanding what is going on underground is your first step in creating a healthy and beautiful garden. Co-sponsored with Lifelong Learning. Members pay $44 + sp fee, register for section 002.


Press start to begin quiz
start
seconds remaining
correct:
0
wrong:
0
Reset Score
End of quiz
please enter your intials
save


Installing Drivers via the Print Server (Client Settings)
You can use the print server to install printer drivers for a shared printer on other computers (clients) on the same network. Because the printer drivers are installed via the print server, users of the other computers do not need to use the printer's CD-ROM/DVD-ROM.
1
Log on to the computer with an administrator account.
2
Open [Windows Explorer] or [File Explorer].
Windows XP/Vista/7/Server 2003/Server 2008
[Start]
select [All Programs] or [Programs]
[Accessories]
[Windows Explorer].
Windows 8/Server 2012
Right-click the lower-left corner of the screen
select [File Explorer].
3
Select the print server from [Network] or [My Network Places].
To display a computer on the network, you may need to enable [Network discovery] (
Enabling [Network discovery]) or search for the computer on the network.
If the print server is not discovered
Problems via the Print Server
4
Double-click the shared printer.
5
Follow the instructions on the screen to install the printer drivers.
It may not be possible to install printer drivers via the print server if the client computers and the print server use different processor versions (32-bit or 64-bit) of the operating system. In this case, install additional drivers on the print server.
Configuring Settings on the Print Server Computer


President: Emma Moore
Vice President, Admin: Cory Liu
Vice President, Travel: M. Devon Moore
Vice President, Finance: Thomas Chapman
AMTA - The American Mock Trial Association
Perjuries - Forums for the latest news, ideas, discussion.


Learning Japanese characters, or kanji, is a daunting experience for any non-native speaker of the language. Japanese kanji can sometimes be very complex structures, and there are different ways in which that complexity may be measured. One measure is simply stroke count, with more complex characters featuring higher numbers of strokes. Another related measure, though less commonly considered, is the number of parts that constitute a single kanji character. These subparts, known as radicals, lend both structural and semantic meaning and value to a character. In this project, kanji characters are mapped against one another by virtue of their structural components. Doing so reveals how certain common radicals and parts dominate the structure of different kanji characters.
In this visualization, each line represents a single character in the total set of
jouyou kanji (常用漢字). Lines are colored according to the grade in which they are introduced in the Japanese school system, from Grade 1 to secondary school. When you
hover over a single line, all of that kanji character's composite parts (including its radical) are displayed. Each step in the line along the horizontal axis represents an additional part (component) of the character; vertical position, meanwhile, corresponds to the stroke complexity of the respective kanji component (radicals with only one stroke are closer to the top of the visualization, while those with more strokes progress downward). The represented kanji character for each line is displayed at the end of the line.
To see all the kanji for a given grade, click the colored circle next to that grade or its respective label.
In addition to the lines representing each kanji character, the circles indicate radicals and kanji parts represented across all kanji displayed. These gray circles vary in size according to the relative number of kanji that contain them: larger dark gray circles indicate radicals or parts that are more commonly found in the kanji displayed. As you read the visualization, it is worth noting those kanji that extend far to the right and down the chart, as these indicate complex kanji characters with many individual subparts with many strokes.
This visualization was built in
D3.js by
Steven Braun. The data are taken from
Jim Breen's KRADFILE, a concordance of all kanji and their composite radicals. The code for this project is freely available on
GitHub.


About us
We are a young group of enthusiastic barbers and tattooers. Our passion burns within creating pieces of art in form of haircuts and tattoos.
Where you can find us?
AE Barbershop
Little Hanoi, Sapa
Praha 4, 14200
How can you contact us?
Monday - Sunday
9:30 - 19:00