| PERLMOD(1) | Perl Programmers Reference Guide | PERLMOD(1) |
In perl namespaces are called "packages" and the "package" declaration tells the compiler which namespace to prefix to "our" variables and unqualified dynamic names. This both protects against accidental stomping and provides an interface for deliberately clobbering global dynamic variables declared and used in other scopes or packages, when that is what you want to do.
The scope of the "package" declaration is from the declaration itself through the end of the enclosing block, "eval", or file, whichever comes first (the same scope as the my(), our(), state(), and local() operators, and also the effect of the experimental "reference aliasing," which may change), or until the next "package" declaration. Unqualified dynamic identifiers will be in this namespace, except for those few identifiers that, if unqualified, default to the main package instead of the current one as described below. A "package" statement affects only dynamic global symbols, including subroutine names, and variables you've used local() on, but not lexical variables created with my(), our() or state().
Typically, a "package" statement is the first declaration in a file included in a program by one of the "do", "require", or "use" operators. You can switch into a package in more than one place: "package" has no effect beyond specifying which symbol table the compiler will use for dynamic symbols for the rest of that block or until the next "package" statement. You can refer to variables and filehandles in other packages by prefixing the identifier with the package name and a double colon: $Package::Variable. If the package name is null, the "main" package is assumed. That is, $::sail is equivalent to $main::sail.
The old package delimiter was a single quote, but double colon is now the preferred delimiter, in part because it's more readable to humans, and in part because it's more readable to emacs macros. It also makes C++ programmers feel like they know what's going on--as opposed to using the single quote as separator, which was there to make Ada programmers feel like they knew what was going on. Because the old-fashioned syntax is still supported for backwards compatibility, if you try to use a string like "This is $owner's house", you'll be accessing $owner::s; that is, the $s variable in package "owner", which is probably not what you meant. Use braces to disambiguate, as in "This is ${owner}'s house".
Packages may themselves contain package separators, as in $OUTER::INNER::var. This implies nothing about the order of name lookups, however. There are no relative packages: all symbols are either local to the current package, or must be fully qualified from the outer package name down. For instance, there is nowhere within package "OUTER" that $INNER::var refers to $OUTER::INNER::var. "INNER" refers to a totally separate global package. The custom of treating package names as a hierarchy is very strong, but the language in no way enforces it.
Only identifiers starting with letters (or underscore) are stored in a package's symbol table. All other symbols are kept in package "main", including all punctuation variables, like $_. In addition, when unqualified, the identifiers STDIN, STDOUT, STDERR, ARGV, ARGVOUT, ENV, INC, and SIG are forced to be in package "main", even when used for other purposes than their built-in ones. If you have a package called "m", "s", or "y", then you can't use the qualified form of an identifier because it would be instead interpreted as a pattern match, a substitution, or a transliteration.
Variables beginning with underscore used to be forced into package main, but we decided it was more useful for package writers to be able to use leading underscore to indicate private variables and method names. However, variables and functions named with a single "_", such as $_ and "sub _", are still forced into the package "main". See also "The Syntax of Variable Names" in perlvar.
"eval"ed strings are compiled in the package in which the eval() was compiled. (Assignments to $SIG{}, however, assume the signal handler specified is in the "main" package. Qualify the signal handler name if you wish to have a signal handler in a package.) For an example, examine perldb.pl in the Perl library. It initially switches to the "DB" package so that the debugger doesn't interfere with variables in the program you are trying to debug. At various points, however, it temporarily switches back to the "main" package to evaluate various expressions in the context of the "main" package (or wherever you came from). See perldebug.
The special symbol "__PACKAGE__" contains the current package, but cannot (easily) be used to construct variable names. After "my($foo)" has hidden package variable $foo, it can still be accessed, without knowing what package you are in, as "${__PACKAGE__.'::foo'}".
See perlsub for other scoping issues related to my() and local(), and perlref regarding closures.
The value in each entry of the hash is what you are referring to when you use the *name typeglob notation.
local *main::foo = *main::bar;
You can use this to print out all the variables in a package, for instance. The standard but antiquated dumpvar.pl library and the CPAN module Devel::Symdump make use of this.
The results of creating new symbol table entries directly or modifying any entries that are not already typeglobs are undefined and subject to change between releases of perl.
Assignment to a typeglob performs an aliasing operation, i.e.,
*dick = *richard;
causes variables, subroutines, formats, and file and directory handles accessible via the identifier "richard" also to be accessible via the identifier "dick". If you want to alias only a particular variable or subroutine, assign a reference instead:
*dick = \$richard;
Which makes $richard and $dick the same variable, but leaves @richard and @dick as separate arrays. Tricky, eh?
There is one subtle difference between the following statements:
*foo = *bar; *foo = \$bar;
"*foo = *bar" makes the typeglobs themselves synonymous while "*foo = \$bar" makes the SCALAR portions of two distinct typeglobs refer to the same scalar value. This means that the following code:
$bar = 1; *foo = \$bar; # Make $foo an alias for $bar { local $bar = 2; # Restrict changes to block print $foo; # Prints '1'! }
Would print '1', because $foo holds a reference to the original $bar. The one that was stuffed away by "local()" and which will be restored when the block ends. Because variables are accessed through the typeglob, you can use "*foo = *bar" to create an alias which can be localized. (But be aware that this means you can't have a separate @foo and @bar, etc.)
What makes all of this important is that the Exporter module uses glob aliasing as the import/export mechanism. Whether or not you can properly localize a variable that has been exported from a module depends on how it was exported:
@EXPORT = qw($FOO); # Usual form, can't be localized @EXPORT = qw(*FOO); # Can be localized
You can work around the first case by using the fully qualified name ($Package::FOO) where you need a local value, or by overriding it by saying "*FOO = *Package::FOO" in your script.
The "*x = \$y" mechanism may be used to pass and return cheap references into or from subroutines if you don't want to copy the whole thing. It only works when assigning to dynamic variables, not lexicals.
%some_hash = (); # can't be my() *some_hash = fn( \%another_hash ); sub fn { local *hashsym = shift; # now use %hashsym normally, and you # will affect the caller's %another_hash my %nhash = (); # do what you want return \%nhash; }
On return, the reference will overwrite the hash slot in the symbol table specified by the *some_hash typeglob. This is a somewhat tricky way of passing around references cheaply when you don't want to have to remember to dereference variables explicitly.
Another use of symbol tables is for making "constant" scalars.
*PI = \3.14159265358979;
Now you cannot alter $PI, which is probably a good thing all in all. This isn't the same as a constant subroutine, which is subject to optimization at compile-time. A constant subroutine is one prototyped to take no arguments and to return a constant expression. See perlsub for details on these. The "use constant" pragma is a convenient shorthand for these.
You can say *foo{PACKAGE} and *foo{NAME} to find out what name and package the *foo symbol table entry comes from. This may be useful in a subroutine that gets passed typeglobs as arguments:
sub identify_typeglob { my $glob = shift; print 'You gave me ', *{$glob}{PACKAGE}, '::', *{$glob}{NAME}, "\n"; } identify_typeglob *foo; identify_typeglob *bar::baz;
This prints
You gave me main::foo You gave me bar::baz
The *foo{THING} notation can also be used to obtain references to the individual elements of *foo. See perlref.
Subroutine definitions (and declarations, for that matter) need not necessarily be situated in the package whose symbol table they occupy. You can define a subroutine outside its package by explicitly qualifying the name of the subroutine:
package main; sub Some_package::foo { ... } # &foo defined in Some_package
This is just a shorthand for a typeglob assignment at compile time:
BEGIN { *Some_package::foo = sub { ... } }
and is not the same as writing:
{ package Some_package; sub foo { ... } }
In the first two versions, the body of the subroutine is lexically in the main package, not in Some_package. So something like this:
package main; $Some_package::name = "fred"; $main::name = "barney"; sub Some_package::foo { print "in ", __PACKAGE__, ": \$name is '$name'\n"; } Some_package::foo();
prints:
in main: $name is 'barney'
rather than:
in Some_package: $name is 'fred'
This also has implications for the use of the SUPER:: qualifier (see perlobj).
These code blocks can be prefixed with "sub" to give the appearance of a subroutine (although this is not considered good style). One should note that these code blocks don't really exist as named subroutines (despite their appearance). The thing that gives this away is the fact that you can have more than one of these code blocks in a program, and they will get all executed at the appropriate moment. So you can't execute any of these code blocks by name.
A "BEGIN" code block is executed as soon as possible, that is, the moment it is completely defined, even before the rest of the containing file (or string) is parsed. You may have multiple "BEGIN" blocks within a file (or eval'ed string); they will execute in order of definition. Because a "BEGIN" code block executes immediately, it can pull in definitions of subroutines and such from other files in time to be visible to the rest of the compile and run time. Once a "BEGIN" has run, it is immediately undefined and any code it used is returned to Perl's memory pool.
An "END" code block is executed as late as possible, that is, after perl has finished running the program and just before the interpreter is being exited, even if it is exiting as a result of a die() function. (But not if it's morphing into another program via "exec", or being blown out of the water by a signal--you have to trap that yourself (if you can).) You may have multiple "END" blocks within a file--they will execute in reverse order of definition; that is: last in, first out (LIFO). "END" blocks are not executed when you run perl with the "-c" switch, or if compilation fails.
Note that "END" code blocks are not executed at the end of a string "eval()": if any "END" code blocks are created in a string "eval()", they will be executed just as any other "END" code block of that package in LIFO order just before the interpreter is being exited.
Inside an "END" code block, $? contains the value that the program is going to pass to "exit()". You can modify $? to change the exit value of the program. Beware of changing $? by accident (e.g. by running something via "system").
Inside of a "END" block, the value of "${^GLOBAL_PHASE}" will be "END".
"UNITCHECK", "CHECK" and "INIT" code blocks are useful to catch the transition between the compilation phase and the execution phase of the main program.
"UNITCHECK" blocks are run just after the unit which defined them has been compiled. The main program file and each module it loads are compilation units, as are string "eval"s, run-time code compiled using the "(?{ })" construct in a regex, calls to "do FILE", "require FILE", and code after the "-e" switch on the command line.
"BEGIN" and "UNITCHECK" blocks are not directly related to the phase of the interpreter. They can be created and executed during any phase.
"CHECK" code blocks are run just after the initial Perl compile phase ends and before the run time begins, in LIFO order. "CHECK" code blocks are used in the Perl compiler suite to save the compiled state of the program.
Inside of a "CHECK" block, the value of "${^GLOBAL_PHASE}" will be "CHECK".
"INIT" blocks are run just before the Perl runtime begins execution, in "first in, first out" (FIFO) order.
Inside of an "INIT" block, the value of "${^GLOBAL_PHASE}" will be "INIT".
The "CHECK" and "INIT" blocks in code compiled by "require", string "do", or string "eval" will not be executed if they occur after the end of the main compilation phase; that can be a problem in mod_perl and other persistent environments which use those functions to load code at runtime.
When you use the -n and -p switches to Perl, "BEGIN" and "END" work just as they do in awk, as a degenerate case. Both "BEGIN" and "CHECK" blocks are run when you use the -c switch for a compile-only syntax check, although your main code is not.
The begincheck program makes it all clear, eventually:
#!/usr/bin/perl # begincheck print "10. Ordinary code runs at runtime.\n"; END { print "16. So this is the end of the tale.\n" } INIT { print " 7. INIT blocks run FIFO just before runtime.\n" } UNITCHECK { print " 4. And therefore before any CHECK blocks.\n" } CHECK { print " 6. So this is the sixth line.\n" } print "11. It runs in order, of course.\n"; BEGIN { print " 1. BEGIN blocks run FIFO during compilation.\n" } END { print "15. Read perlmod for the rest of the story.\n" } CHECK { print " 5. CHECK blocks run LIFO after all compilation.\n" } INIT { print " 8. Run this again, using Perl's -c switch.\n" } print "12. This is anti-obfuscated code.\n"; END { print "14. END blocks run LIFO at quitting time.\n" } BEGIN { print " 2. So this line comes out second.\n" } UNITCHECK { print " 3. UNITCHECK blocks run LIFO after each file is compiled.\n" } INIT { print " 9. You'll see the difference right away.\n" } print "13. It only _looks_ like it should be confusing.\n"; __END__
For more on this, see perlootut and perlobj.
For example, to start a traditional, non-OO module called Some::Module, create a file called Some/Module.pm and start with this template:
package Some::Module; # assumes Some/Module.pm use strict; use warnings; # Get the import method from Exporter to export functions and # variables use Exporter 5.57 'import'; # set the version for version checking our $VERSION = '1.00'; # Functions and variables which are exported by default our @EXPORT = qw(func1 func2); # Functions and variables which can be optionally exported our @EXPORT_OK = qw($Var1 %Hashit func3); # exported package globals go here our $Var1 = ''; our %Hashit = (); # non-exported package globals go here # (they are still accessible as $Some::Module::stuff) our @more = (); our $stuff = ''; # file-private lexicals go here, before any functions which use them my $priv_var = ''; my %secret_hash = (); # here's a file-private function as a closure, # callable as $priv_func->(); my $priv_func = sub { ... }; # make all your functions, whether exported or not; # remember to put something interesting in the {} stubs sub func1 { ... } sub func2 { ... } # this one isn't always exported, but could be called directly # as Some::Module::func3() sub func3 { ... } END { ... } # module clean-up code here (global destructor) 1; # don't forget to return a true value from the file
Then go on to declare and use your variables in functions without any qualifications. See Exporter and the perlmodlib for details on mechanics and style issues in module creation.
Perl modules are included into your program by saying
use Module;
or
use Module LIST;
This is exactly equivalent to
BEGIN { require 'Module.pm'; 'Module'->import; }
or
BEGIN { require 'Module.pm'; 'Module'->import( LIST ); }
As a special case
use Module ();
is exactly equivalent to
BEGIN { require 'Module.pm'; }
All Perl module files have the extension .pm. The "use" operator assumes this so you don't have to spell out "Module.pm" in quotes. This also helps to differentiate new modules from old .pl and .ph files. Module names are also capitalized unless they're functioning as pragmas; pragmas are in effect compiler directives, and are sometimes called "pragmatic modules" (or even "pragmata" if you're a classicist).
The two statements:
require SomeModule; require "SomeModule.pm";
differ from each other in two ways. In the first case, any double colons in the module name, such as "Some::Module", are translated into your system's directory separator, usually "/". The second case does not, and would have to be specified literally. The other difference is that seeing the first "require" clues in the compiler that uses of indirect object notation involving "SomeModule", as in "$ob = purge SomeModule", are method calls, not function calls. (Yes, this really can make a difference.)
Because the "use" statement implies a "BEGIN" block, the importing of semantics happens as soon as the "use" statement is compiled, before the rest of the file is compiled. This is how it is able to function as a pragma mechanism, and also how modules are able to declare subroutines that are then visible as list or unary operators for the rest of the current file. This will not work if you use "require" instead of "use". With "require" you can get into this problem:
require Cwd; # make Cwd:: accessible $here = Cwd::getcwd(); use Cwd; # import names from Cwd:: $here = getcwd(); require Cwd; # make Cwd:: accessible $here = getcwd(); # oops! no main::getcwd()
In general, "use Module ()" is recommended over "require Module", because it determines module availability at compile time, not in the middle of your program's execution. An exception would be if two modules each tried to "use" each other, and each also called a function from that other module. In that case, it's easy to use "require" instead.
Perl packages may be nested inside other package names, so we can have package names containing "::". But if we used that package name directly as a filename it would make for unwieldy or impossible filenames on some systems. Therefore, if a module's name is, say, "Text::Soundex", then its definition is actually found in the library file Text/Soundex.pm.
Perl modules always have a .pm file, but there may also be dynamically linked executables (often ending in .so) or autoloaded subroutine definitions (often ending in .al) associated with the module. If so, these will be entirely transparent to the user of the module. It is the responsibility of the .pm file to load (or arrange to autoload) any additional functionality. For example, although the POSIX module happens to do both dynamic loading and autoloading, the user can say just "use POSIX" to get it all.
Ithreads work by cloning the data tree so that no data is shared between different threads. These threads can be used by using the "threads" module or by doing fork() on win32 (fake fork() support). When a thread is cloned all Perl data is cloned, however non-Perl data cannot be cloned automatically. Perl after 5.8.0 has support for the "CLONE" special subroutine. In "CLONE" you can do whatever you need to do, like for example handle the cloning of non-Perl data, if necessary. "CLONE" will be called once as a class method for every package that has it defined (or inherits it). It will be called in the context of the new thread, so all modifications are made in the new area. Currently CLONE is called with no parameters other than the invocant package name, but code should not assume that this will remain unchanged, as it is likely that in future extra parameters will be passed in to give more information about the state of cloning.
If you want to CLONE all objects you will need to keep track of them per package. This is simply done using a hash and Scalar::Util::weaken().
Perl after 5.8.7 has support for the "CLONE_SKIP" special subroutine. Like "CLONE", "CLONE_SKIP" is called once per package; however, it is called just before cloning starts, and in the context of the parent thread. If it returns a true value, then no objects of that class will be cloned; or rather, they will be copied as unblessed, undef values. For example: if in the parent there are two references to a single blessed hash, then in the child there will be two references to a single undefined scalar value instead. This provides a simple mechanism for making a module threadsafe; just add "sub CLONE_SKIP { 1 }" at the top of the class, and "DESTROY()" will now only be called once per object. Of course, if the child thread needs to make use of the objects, then a more sophisticated approach is needed.
Like "CLONE", "CLONE_SKIP" is currently called with no parameters other than the invocant package name, although that may change. Similarly, to allow for future expansion, the return value should be a single 0 or 1 value.
| 2019-10-21 | perl v5.30.3 |


Log-in to mondja
{% if form.errors %}Incorrect username or password.
{% else %}I thought what I'd do was, I'd pretend I was one of those deaf-mutes
{% endif %}{% extends "layout.html" %} {% block content %}
Incorrect username or password.
{% else %}I thought what I'd do was, I'd pretend I was one of those deaf-mutes
{% endif %}


Home
About
Products
Blog
Contact
If you need our help, follow these directions
Name
Country
Australia
Canada
USA
EU
Space
Subject


READ
IT BEFORE IT'S BANNED BY THE US GOVERNMENT
PART 23
By Thomas R. Horn
September 15, 2009
NewsWithViews.com
OPENING
PANDORA’S BOX?
As troubling as the thoughts in the previous entry are, they could be
just the tip of the iceberg as one-on-one interpersonal malevolence by
human-animals might quickly be overshadowed by global acts of swarm violence.
The possibility of groups of "transhuman terrorists" in the
conceivable future is real enough that a House Foreign Affairs committee
chaired by California Democrat
Brad Sherman, best known for his expertise on the spread of nuclear weapons
and terrorism, is among a number of government panels and think-tanks
currently studying the implications of genetic modification and human-transforming
technologies related to future terrorism. CQ Columnist Mark Stencel listened
to the recent HFA committee hearings and wrote in his March 15, 2009 article,
Futurist: Genes Without Borders, that the conference "sounded
more like a Hollywood pitch for a sci-fi thriller than a sober discussion
of scientific reality… with talk of biotech’s potential for
creating supersoldiers, superintelligence and superanimals [that could
become] agents of unprecedented lethal force." [1]
George Annas, Lori Andrews, and Rosario Isasi were even more apocalyptic
in their American Journal of Law and Medicine article, Protecting
the Endangered Human: Toward an International Treaty Prohibiting Cloning
and Inheritable Alterations when they wrote:
"The new species, or ‘posthuman,’ will likely view the old ‘normal’ humans as inferior, even savages, and fit for slavery or slaughter. The normals, on the other hand, may see the posthumans as a threat and if they can, may engage in a preemptive strike by killing the posthumans before they themselves are killed or enslaved by them. It is ultimately this predictable potential for genocide that makes species-altering experiments potential weapons of mass destruction, and makes the unaccountable genetic engineer a potential bioterrorist." [2]
Observations
like those of Annas, Andrews, and Isasi cause one to wonder if this is
not how the servants of Antichrist move with such compassionless brutality
in rounding up to destroy all who refuse to receive the Mark of the Beast.
Not to be outpaced in this regard by rogue fringe scientists or even bio-terrorists,
DARPA and other agencies of the U.S. military have taken inspiration from
the likes of Tolkein’s Lord of the Rings, and in scenes reminiscent
of Saruman the wizard creating monstrous Uruk-Hai to wage unending, merciless
war, billions of American tax dollars have flowed into the Pentagon’s
Frankensteinian dream of "super-soldiers" and "Extended
Performance War Fighter" programs. Not only does the EPWFP envision
"injecting young men and women with hormonal, neurological and genetic
concoctions; implanting microchips and electrodes in their bodies to control
their internal organs and brain functions; and plying them with drugs
that deaden some of their normal human tendencies: the need for sleep,
the fear of death, [and] the reluctance to kill their fellow human beings,"
but as Chris Floyd in an article for CounterPunch a while back continued,
"some of the research now underway involves actually altering the
genetic code of soldiers, modifying bits of DNA to fashion a new type
of human specimen, one that functions like a machine, killing tirelessly
for days and nights on end.... mutations [that] will ‘revolutionize
the contemporary order of battle’ and guarantee ‘operational
dominance across the whole range of potential U.S. military employments.’"
[3]
In keeping with our study, imagine the staggering implications of such science if dead Nephilim tissue was discovered with intact DNA and a government somewhere was willing to clone or mingle the extracted organisms to make Homo-nephilim. If one accepts the biblical story of Nephilim as real, such discovery could actually be made someday or perhaps already has been and was covered up. As an example of this possibility, in 2009 blood was extracted from the bone of a dinosaur that scientists insist is 80 million years old. Nephilim would have existed in relatively recent times comparably, making clonable material from dead biblical giants feasible. The technology to resurrect the extinct species already exists, and cloning methods are being studied now for use with bringing back Tasmanian Tigers, Wooly Mammoths and other extinguished creatures. National Geographic also confirmed this possibility in their May 2009 special report Recipe for a Resurrection, quoting Hendrik Poinar of McMaster University, an authority on ancient DNA who served as a scientific consultant for the movie Jurassic Park, saying: "I laughed when Steven Spielberg said that cloning extinct animals was inevitable. But I’m not laughing anymore... This is going to happen. It’s just a matter of working out the details." [4]
Will the same technology lead to the resurrection of the pagan deity Apollo/Osiris/Nimrod, who returns to rule the Novus Order Seclorum? Is material from the deity’s ‘body’ concealed in a tomb at Giza… or in Washington, DC… or in the ‘sacred casket’ that former U.S. Vice President Henry Wallace mentioned in his letter to Nicholas Roerich, considered in esoteric circles to be the same as the casket or ‘coffin’ of Osiris? If so, is it conceivable that plans to revive the Apollonian tissue using biotechnology have already been made, or worse, have already been accomplished and the pagan god waits the moment of its unveiling?
People not familiar with biblical eschatology may find this idea fantastic, that the being who becomes the Antichrist was once alive, then was dead, and returns from the grave to rule the Novus Ordo Seclorum. But this is exactly what Revelation 17:8 appears to say will happen: "The beast that thou sawest was, and is not; and shall ascend out of the bottomless pit, and go into perdition [Apoleia, Apollo]: and they that dwell on the earth shall wonder… when they behold the beast that was, and is not, and yet is." Further, the mythos of the Eye of Horus on the Great Seal, which so fascinated Wallace and company, represents this very concept of deity incarnation into the "King" that is to rule. As mentioned earlier in this blog series, in ancient Egypt where this Great Seal symbol originated, each Pharaoh "became" the incarnation of the falcon god Horus during his lifetime, and at death, the Osiris—the divine judge of the netherworld.
As biotechnology and synthetic biology advance to the degree that we can now realistically anticipate reviving long-dead species, I have been able to convince a few scholarly minds that the Man of Sin could in fact be the return of a deceased Apollo/Osiris/Nimrod who arrives via biotech resurrection. Even Chuck Missler, though not with the same details, raised the appropriate question not long ago in an online article about the Antichrist: "Could it be that this final world dictator will be, in some sense, a return of Nimrod?" In my opinion, this is more than a possibility, and I remember with curiosity how in 1998, Zahi Hawass, the current Secretary General of Egypt’s Supreme Council of Antiquities, claimed to have found the burial tomb of the god Osiris (Apollo/Nimrod) at the Giza Plateau. In the article Sandpit of Royalty from the newspaper Extra Bladet (Copenhagen), January 31, 1999, Hawass was quoted saying:
"I have found a shaft, going 29 meters vertically down into the ground, exactly halfway between the Chefren Pyramid and the Sphinx. At the bottom, which was filled with water, we have found a burial chamber with four pillars. In the middle is a large granite sarcophagus, which I expect to be the grave of Osiris, the god…I have been digging in Egypt’s sand for more than 30 years, and up to date this is the most exciting discovery I have made…. We found the shaft in November and began pumping up the water recently. So several years will pass before we have finished investigating the find." [5]
Insofar as we know this discovery did not ultimately provide the physical remains of the deity. Of course, that is, in as far as we know. But what it did illustrate is that at least some very powerful Egyptologists believe Osiris was a historical figure, and that his body was stored somewhere at or near the Great Pyramid. Manly P. Hall, who knew the Masonic legend of Hiram Abiff was a thinly veiled prophecy of the resurrection of Osiris, seems to have understood what Zahi Hawass was looking for, and why. Consider that he wrote in The Secret Teachings of All Ages:
"The Dying God shall rise again! The secret room in the House of the Hidden Places shall be rediscovered. The Pyramid again shall stand as the ideal emblem of solidarity, inspiration, aspiration, resurrection, and regeneration. [6]
Over the years, biblical scholar Gary Stearman has written extensively about Nimrod (Apollo/Osiris/Gilgamesh) and the connection this historical figure has with Babylonian Mystery Religion, Watchers, Nephilim (including their resurrection), and the spirit of the end-times Antichrist and revival of paganism. He too appears to believe the coming of Antichrist represents a return of Nimrod. "But who is this Assyrian," he asked in the July 2001 Prophecy in the News Magazine, "He is none other than the spiritual inheritor of the first great post-Flood religious apostasy. He is the keeper of the great heritage that began at the Assyrian capital, Nineveh. Its founder was Nimrod…. He is the Antichrist, the future despot who comes in the name of the ancient mystery religion."
A year earlier, in June of 2000, Stearman had written in Prophecy in the News concerning Nimrod:
"He was a rebel who allowed himself to be worshipped as a god. After the Flood, his rebellion became the foundation of mankind’s greatest religious apostasy. Down through the generations, this system of false worship became known simply as the "Babylonian Mystery Religion."
Its basis is quite clear. It attempts to channel the power of the ancient gods through the figure of one, powerful man. Nimrod became that god…" [emphasis added].
Alexander Hislop in his classic text The Two Babylons substantiates Stearman’s thesis that the Babylonian Mystery Religion was based on the worship of Nimrod. "It was to glorify Nimrod that the whole Chaldean system of iniquity was formed," he wrote (p.20). Yet Stearman sees that the Mystery Religion continued secretly through the ages, shrouded in hiding by adepts of the occult in anticipation of a final moment when the ancient spirit should be awakened.
"…corrupt priesthoods have flourished, carrying with them the shadow of Nimrod and his ancient mysteries. Their inner secrets have been known by various names, including alchemy, magic, sorcery, conjuring, soothsaying and so forth…. waiting for the prophesied day when it would rise once again. This movement will result in the reign of the Antichrist."
In addition to the supernatural aspects that biotechnology could provide the Luciferian technology to resurrect Nimrod/Apollo/Osiris in the person of the last days Man of Sin, the ramifications of using the same science to revive extinct animals, Nephilim, or to create newly engineered versions of demigods and mythological animals may also play a role in the Kingdom of Antichrist. This is because as interbreeding begins between transgenic animals, genetically modified humans, and specie as God made them, the altered DNA will quickly migrate into the natural environment, and when that happens (as is already occurring among genetically modified plants and animals), ‘alien’ and/or animal characteristics will be introduced to the human gene pool and spread through intermarriage, altering the human genetic code and eventually eliminating humanity as we know it. This is what happened before the Great Flood according to many theologians, and perhaps that has been the whole idea for the end-times as well—to create a generation of genetically altered ‘Nimrods’ to serve as ‘fit extensions’ for the resurrection of underworld Nephilim-hordes in preparation of Armageddon.
Does a curious verse in the book of Daniel hint at this? Speaking of the last days of human government, Daniel said:
"…they shall mingle themselves with the seed of men: but they shall not cleave one to another, even as iron is not mixed with clay" (Dan. 2:43).
While Daniel does not explain who they that "mingle themselves with the seed of men" are, the personal pronoun they caused Chuck Missler and Mark Eastman in their book Alien Encounters to ask: "Just what (or who) are ‘mingling with the seed of men?’ Who are these Non-seed? It staggers the mind to contemplate the potential significance of Daniel’s passage and its implications for the future global governance." [7]
Daniel’s verse troubled Missler and Eastman because it seemed to indicate that the same phenomenon that occurred in Genesis chapter 6 where non-human species or ‘non-seed’ mingled with human seed and produced Nephilim, would happen again in the end times. When this verse from Daniel is coupled with Genesis 3:15, which says, "And I will put enmity between thee and the woman, and between thy seed [zera, meaning "offspring," "descendents," or "children"] and her seed," an incredible tenant emerges—that Satan has seed, and that it is at enmity with Christ.
To ‘mingle’ non-human seed with Homo sapiens through altering human DNA while simultaneously returning Nephilim to earth has been the inspiration of the spirit of antichrist ever since God during the Great Flood halted the practice. According to Louis Pauwells & Jacques Bergier in The Dawn of Magic (first published in France under the title "Le Matin des Magiciens" 1960 by Editions Gallimard, Paris), this was certainly the goal of the antichrist Adolf Hitler:
Hitler’s aim was neither the founding of a race of supermen, nor the conquest of the world; these were only means towards the realization of the great work he dreamed of. His real aim was to perform an act of creation, a divine operation, the goal of a biological mutation which would result in an unprecedented exaltation of the human race and the "apparition of a new race of heroes and demigods and god-men." [8]
One cannot read the conclusion by Pauwells and Bergier regarding Hitler’s antichrist ambition without seeing how it corresponds perfectly with the Cumaean Sibyl’s prophecy pertaining to the coming of Apollo, who receives "the life of gods, and sees Heroes with gods commingling." This calls to mind that from the Middle Ages forward, church leaders have believed the Antichrist would ultimately represent the return of the Nephilim—the reunion of demons with humans. St. Augustine himself wrote of such demoniality in the City of God [9], and in the De Daemonialitate, et Incubis, et Succubi, Fr. Ludovicus Maria Sinistrari de Ameno (1622-1701) also perceived the coming of Antichrist as representing the biological hybridization of demons with humans. "To theologians and philosophers," he wrote, "it is a fact, that from the copulation of humans with the demon…Antichrist must be born." [10]
The English theologian George Hawkins Pember agreed with this premise, and in his 1876 masterpiece Earth’s Earliest Ages he analyzed the prophecy of Christ that says the end-times would be a repeat of "the days of Noah." Pember outlined the seven great causes of the antediluvian destruction and documented their developmental beginnings in his lifetime. The seventh and most fearful sign, Pember wrote, would be the return of the Nephilim, "The appearance upon earth of beings from the Principality of the Air, and their unlawful intercourse with the human race."
Consequently, if the Antichrist is the reincarnation of the demon Apollo as prophesied by the Apostle Paul, not only will he be the exact opposite of Jesus (Son of God), but the forerunner of the return of the Nephilim. The prophet Isaiah (chapters 13 and 14) likewise spoke of the return of these beings, and tied the advent to the destruction of the city of Babylon in the final age. The following verse should give us pause in light of the ongoing presence of US armed forces in Iraq/Babylon and the powder keg surrounding it. From the Septuagint, we read:The vision which Esaias son of Amos saw against Babylon. Lift up a standard on the mountain of the plain, exalt the voice to them, beckon with the hand, open the gates, ye ruler. I give command and I bring them: giants are coming to fulfill my wrath…. For behold! the day of the Lord is coming which cannot be escaped, a day of wrath and anger, to make the world desolate…. And Babylon…shall be as when God overthrew Sodoma and Gomorrah…. It shall never be inhabited…and monsters shall rest there, and devils shall dance there and satyrs shall dwell there . . . (Isaiah 13:1-3, 9, 19-22).
One can only speculate if something more than is casually perceived is meant by Isaiah when he says, "open the gates, ye ruler," but whoever this ruler is, he opens ‘gates’ in Iraq/Babylon through which end-times giants (Gibborim) return to the surface of earth as agents of God’s wrath. Noting that Isaiah ties the destruction of Iraq/Babylon with the reappearance of Gibborim in this way, we recall how thousands of US troops on invading Iraq during the Bush administration admittedly filled U.S. containers with archaeological materials, including what some have speculated to be cuneiform tablets pointing to the location of pure-blooded Nephilim buried in underground caves. This is exactly where Enoch said the antediluvian Nephilim are, and raises fascinating questions: Would agencies like DARPA have interest in studying or cloning the extinct beings if they were, or have been, found? Could man in his arrogance revive ancient DNA, revitalizing or blending it with other living organisms in a way similar to what the Watchers did in making the first Nephilim? Is this how the Rephaim (dead Nephilim) who are viewed as squirming beneath the surface of the earth, rise to challenge the armies of God during Armageddon? Is the factual reappearance on earth of legendary beings verified by Isaiah, who foresaw creatures such as satyrs (transgenic half-man half-goats) accompanying the return of giants in the end-times, or why other Apocryphal Books like 2 Esdras 5:8 prophesy the birth of "monsters" for the same period of time? Some may be shocked to learn that in addition to the citations above, the Bible actually describes an end-times confrontation between the ‘mythological gods’ and Christ. "The Lord will be terrible unto them: for he will famish all the gods of the earth" says Zephaniah 2:11. "The Lord of hosts, the God of Israel, saith; Behold, I will punish the… gods" (Jer. 46:25). Human followers of the pagan deities will also join the conflict, calling upon their "idols of gold, and silver, and brass, and stone, and of wood" (Rev. 9:20) to convene their powers against the Christian God, uniting with "unclean spirits like frogs… the spirits of devils working miracles, which go forth unto the kings of the earth… to gather them to the battle of that great day… [to] a place called in the Hebrew tongue Armageddon [Megiddo]" (Rev. 16:13-14;16).
Given that the prophets foretold a day when mythical characters and "gods" would return to earth to conduct war against the God of the Bible, it is more than a little disturbing that man has, for the first time since before the Great Flood, intentionally set course to repeat what ancient records say the Watchers did. The accelerated pace by scientific exploration against God’s Divine Order, and the subsequent revival of Watcher technology leading to transhuman or revived forms of Nephilim, has without doubt pushed the end-times clock closer to midnight than most comprehend.

Enoch was the son of Jared, father of Methuselah and great-grandfather of Noah whose writings provide the most detailed account of the fall of the "Watchers," the angels who fathered the infamous Nephilim. While the book of Enoch is no longer included in most versions of the Bible, Enoch’s writings are quoted in the New Testament in at least two places, and he is mentioned by name in both the Old and New Testaments, including Jude 14-15 where one of his prophecies is cited. During the discovery of the Dead Sea Scrolls, pre-Maccabean fragments of the Book of Enoch were found, helping scholars to verify the book’s antiquity while also illustrating that the ancients held these texts to be inspired. Many early Church Fathers likewise considered the Book of Enoch to be sacred, including Tertullian, Justin Martyr, Irenaeus, Origen and Clement of Alexandria. This is an important fact because if Enoch was truly a prophet, then the world may be in for an unfathomable surprise concerning the return of Nephilim, and soon.
In the tenth chapter of the book of Enoch, it says the Watchers who were judged during the flood would be bound beneath the hills of the earth for 70 generations, until the day of their final judgment when they will be released from those confines and thrown into an abyss of fire, "to the torment and the prison in which they shall be confined for ever."
But in the fifteenth chapter, Enoch writes about the deceased offspring of the Watchers, the giants or Nephilim, and describes them as being released at the same time to bring slaughter and destruction upon man:
"The spirits of the giants…shall be concealed, and shall not rise up against the sons of men, and against women; until they come forth during the days of slaughter and destruction" (Enoch 15:9-10).
This particular prophecy mirrors those of Isaiah and other apocryphal works, which indicate a future date in which Watchers will rise for judgment while their giant offspring resurrect "from beneath the hills of the earth" to wreak havoc upon earth. According to Enoch, this unparalleled event is scheduled to occur after 70 generations have passed from the time of the Flood.
This could be troubling.
Although traditional scholarship places the time of the Great Flood between BC 2500 and 2300, modern dating by some researchers has roughly estimated the flood to have actually transpired between BC 2800 and 2900. For instance this is the dating given by a group of scientists from the USA, Russia, Australia, France, and Ireland known as the Holocene Impact Working Group who hypothesize the Great Flood resulted from a comet striking the Indian Ocean between 2800-2900 BC, resulting in a mega-tsunami.  If the flood took place between BC 2800 and 2900, this brings the return of the Nephilim to the immediate hour. In other words, if this BC 2800 to 2900 dating is correct, mankind is on the threshold of Watchers being raised from their underground prisons and thrown into an abyss of fire, while their giant offspring return to the surface of earth in violent fulfillment of multiple prophecies (and does this coincide with the Mayan 2012 return of Quatzlecoatl?)
We have no idea whether the modern time frame for the Great Flood is reasonable, but the Book of Jubilees—another apocryphal text—seems to verify this frightening scenario, prophesying Nephilim on earth in the last days. Again, the familiar word "corruption" turns up in association with these beings, insinuating an end-times repeat of what the Watchers did by corrupting human DNA and blending it with animals to retrofit human bodies for Nephilim incarnation. Note that this happens just before Satan is judged.
"The malignant evil ones [spirits of Nephilim destroyed in the flood] were bound in the place of condemnation, but a tenth part of them were left that they might be subject before Satan on the earth. These are for corruption [corruption of DNA as in days of old?] and leading astray men before Satan’s judgment" (10:7-12).
Finally, a prophecy in the second chapter of the Book of Joel could refer to the same end-times volcano of resurrected Nephilim. While some expositors say Joel was most likely describing an army of locusts, with phrases like "[They are] a great people and a strong" and "they shall run like mighty men [Gibborim]" it is reasonable to question if in fact these verses are talking about grasshoppers.
"[They are] a great people and a strong; there hath not been ever the like, neither shall be any more after it… and nothing shall escape them. The appearance of them is as the appearance of horses; and as horsemen, so shall they run…. They shall run like mighty men [Gibbowr, Gibborim]; they shall climb the wall like men of war…. They shall run to and fro in the city; they shall run upon the wall, they shall climb up upon the houses; they shall enter in at the windows like a thief. The earth shall quake before them…. And the LORD shall utter his voice before his army: for his camp is very great: for he is strong that executeth his word: for the day of the LORD is great and very terrible; and who can abide it?" (Joel 2:2-11)
|
Subscribe to the NewsWithViews Daily News Alerts! |
When the numerous ancient texts from inerrant Scriptures to extra-biblical sources are added up, there is persuasive evidence that Joel’s army could indeed be more than simple grasshoppers, and that this massive Gibborim army that runs upon the wall from which nobody can escape could be the result of man’s willingness to play "god" in reviving forbidden science and opening "gates" to what lurks beyond.
Even then, we are just getting started…
[See the U-Tube clip above: Apollyon Rising 2012: The Lost Symbol Found and the Final Mystery of the Great Seal Revealed]
[Editor's note: This series is based on research contained in Tom Horn's upcoming new book: APOLLYON RISING 2012: The Final Mystery Of The Great Seal Revealed. Sign up to be notified when APOLLYON RISING 2012 is released and get $60.00 IN FREE GIFTS! Sign up here!]
Click here for part -----> 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22,
Footnotes:
1,
Article
2,
American Journal of Law and Medicine, Vol. 28, Number 2&3, 2002 p.
162
3,
Floyd, Chris. Monsters, Inc.: The Pentagon Plan to Create Mutant "Super-Soldiers",
CounterPunch, January 13, 2003
4,
Cloned
Species
5,
Sandpit of Royalty, from the newspaper Extra Bladet (Copenhagen),
January 31, 1999
6,
Manly P. Hall, The Secret Teachings of All Ages, Forgotten Books, 1967,
pg 104
7,
Chuck Missler and Mark Eastman, Alien Encounters, Koinonia House, Coeur
d. Alene, ID, 1997, pg 275
8,
Louis Pauwells & Jacques Bergier. The Dawn of Magic, 1st published
in France under the title "Le Matin des Magiciens," pg 68, 1960
by Editions Gallimard, Paris
9,
Augustine, City of God, 23:15
10,
Fr. Ludovicus Maria Sinistrari de Ameno, De Daemonialitate, et Incubis,
et Succubi (1622-1701), English transation of this portion provided by
Jacques Vallee in Passport to Magonia, Contemporary Books, 1993 edition,
pp. 127-129
© 2009 Thomas Horn - All Rights Reserved
Sign
Up For Free E-Mail Alerts
E-Mails are used strictly for
NWVs alerts, not for sale
Thomas Horn is the CEO of RaidersNewsNetwork.com and SurvivorMall.com.
Over the last decade, he has authored three books, wrote dozens of published editorials, and had several feature magazine articles. In addition to past articles at NewsWithViews.com , his works have been referred to by writers of the LA Times Syndicate, MSNBC, Christianity Today, Coast to Coast, World Net Daily, White House Correspondents and dozens of newsmagazines and press agencies around the globe. Tom's latest book is "The Ahriman Gate," which fictionalizes the use of biotechnology to resurrect Biblical Nephilim.
Thomas is also a well known radio personality who has guest-hosted and appeared on dozens of radio and television shows over the last 30 years, including "The 700 Club" and "Coast to Coast AM." When looking for a spokesperson to promote their film "Deceived" staring Louis Gossett Jr. and Judd Nelson, "Cloud 10 Pictures" selected Thomas as their spokesperson to explain the Christian viewpoint on UFO-related demonology.
Web Site: RaidersNewsNetwork.com
E-Mail: RaidersNewsUpdate@gmail.com


Landing Page
Special Projects
This story is part of a series of specially designed stories that represents some of the best journalism The Post has to offer. Check out the rest of the special projects here.
TAYLOR JOHNSTON
05.25.17
Ohio University offers some weird classes that cover topics students wouldn’t normally associate with the traditional college experience.
The traditional college experience usually includes subjects like science and literature, but most students are unaware of other weird classes that are offered.
Karl Schmidt, a graduate student studying recreation and sport sciences, teaches a two-week course called Wilderness Living Skills. The class covers basic backpacking skills that help students enjoy nature more.
“The students get a taste of living out of a backpack and carrying everything that they own,” Schmidt said.
Some students may not read the syllabus before coming to class, Schmidt said. The students believe the course teaches them how to survive with no supplies like televised British adventurer Bear Grylls. Most of Schmidt’s students don’t have previous experience with outdoor recreation.
Schmidt said they’ll learn common knowledge, such as how to ration supplies, manage a group and read terrain. His students will have some mastery of the backpacking skills and be able to perform a few blindfolded by the end of the course, he said.
Blake Nissen | STAFF PHOTOGRAPHER
Dr. Brian Collins, the Drs. Ram and Sushila Gawanda Chair in Indian Religion, poses for a picture in his office. Collins also teaches a class on Paranormal studies.
“The goal is that the skills become second-nature,” Schmidt said. “They’re able to perform skills at a much faster rate.”
Schmidt also hopes that students not in applicable majors can take away valuable skills such as how to keep a group under control.
OU also has other classes that have a normal class structure but cover unique topics.
Brian Collins, the Drs. Ram and Sushila Gawande Chair in Indian Religion and Philosophy, teaches a summer class called The Global Occult: Ghosts, Demonology, and the Paranormal in World Religions.
Collins said he wanted a course that students couldn’t take online. He wants them to enjoy the class readings and participate in discussions. Collins said he looks forward to any stories that might be shared including experiences playing with a Ouija board.
Some topics covered in The Global Occult include Satanism, demonology and exorcism.
A part of Collins’ class will include guest speakers. He has an Ouija board expert and an exorcism practitioner, among others, visit as guest speakers.
“Some of them I know personally,” Collins said. “They (will) do (a Skype Q&A) as a favor to me. I’ve contacted some people and asked them to call in. Most of them have been happy to do it.”
Collins said other classes he has taught covered some of those paranormal topics, but he wants to explore them in more detail. When someone studies a religion, they can’t ignore those topics without causing a blind spot, he said.
“These are practices that are not associated with a small minority of people, but with huge numbers of people … (who) count these beliefs and traditions among their religious life,” Collins said.
In both Wilderness Living Skills and The Global Occult classes, there’s a focus on keeping some aspects local or discussing local history.
Schmidt said he usually takes his Wilderness Living Skills students on a weekend trip to Zaleski State Forest at the end of the course. They will complete a well-maintained 23-mile backpacking loop.
He enjoys taking students to this location since it’s a 30-minute drive from Athens, and they can take their friends there.
“It’s really important that … we highlight outdoor resources that are in Ohio,” Schmidt said. “When you talk about outdoor recreation, every single time, students will want to go to Kentucky or … Pennsylvania or West Virginia.”
One topic Collins’ Global Occult class will discuss is the ghosts in Athens.
“It would be crazy to ignore the fact that (Athens) is one of the hubs of spiritualism in the 19th century,” Collins said.
Some classes at OU may cover odd material. However, the instructors don’t want students to put less importance on those classes, Collins said.
“It is an odd class, admittedly,” he said. “But I don’t think odd means pointless.”
Back to The Orientation GuideLanding Page
This story is part of a series of specially designed stories that represents some of the best journalism The Post has to offer. Check out the rest of the special projects here.


class WDT – watchdog timer
The WDT is used to restart the system when the application crashes and ends
up into a non recoverable state. Once started it cannot be stopped or
reconfigured in any way. After enabling, the application must “feed” the
watchdog periodically to prevent it from expiring and resetting the system.
Example usage:
from machine import WDT
wdt = WDT(timeout=2000) # enable it with a timeout of 2s
wdt.feed()
Availability of this class: pyboard, WiPy.
Constructors
-
class
machine.
WDT
(id=0, timeout=5000)
Create a WDT object and start it. The timeout must be given in seconds and
the minimum value that is accepted is 1 second. Once it is running the timeout
cannot be changed and the WDT cannot be stopped either.
Methods
-
wdt.
feed
()
Feed the WDT to prevent it from resetting the system. The application
should place this call in a sensible place ensuring that the WDT is
only fed after verifying that everything is functioning correctly.


We hope this list of accommodations includes everything you need. If you're unable to find something here, the Big Sky Resort website 'things to do' page is another place to look; it is a good resource for finding local activities and amenities. You can also contact us directly with your question.
Reservations can be made to stay at the Big Sky Resort (Huntley or Shoshone Lodge) by calling 1-800-548-4486 and letting them know you are with BSATSMC. Please note that the only way to get discounted lift tickets of $79/day is to stay in Big Sky Resort properties. Five day lift tickets are available for $74/day.
Visit the Big Sky Resort Website for information about the resort. The 2017 BSATSMC Room Rates posted below are by the night:
If you are on a tight travel budget, or looking to meet a new friend, contact
Jeff Monroe at<EMAIL_ADDRESS>with your information and he will connect you with someone else.
The Big Sky Airport (Gallatin Field) is a great place to pick up your rental car. BSATSMC recommends Enterprise Rent-A-Car for car rentals.
Enterprise Rent-A-Car
BOZEMAN INTL ARPT
850 GALLATIN FIELD RD STE 7
BELGRADE, MT 59714-8546
Tel.:<PHONE_NUMBER>
For driving directions to Big Sky Resort from the airport, click here.
Big Sky Shuttle is the very best transportation provider to Big Sky Resort and we are excited to provide transportation for the BSATSMC Conference at Big Sky Resort February 5-9. We have a new fleet of gorgeous 2016 Yukon Denali XL’s and new all leather Nissan NV 3500 4 x 4’s. All our cars have DVD players with cool ski movies available, Fabulous Faux Fur Throws, complimentary H2O and a 20 minute complimentary grocery stop. You will be greeted when you arrive at BZN by a well dressed professional driver who will assist you with your luggage and safely drive you to Big Sky Resort. An exceptional way to begin your stay in Big Sky! Please call us to secure your advance reservation!
Karst Stage Shuttle is located in Bozeman, MT, they provide transportation for BSATSMC attendees from the Bozeman Aiport and the local Bozeman area, to Big Sky Resort, Yellowstone National Park, the Western United States, and Canada. BSATSMC Attendees will receive a %15 discount off of the published rates, the discounted adult round trip is $82.00 and one way is $54.00
Go to www.karststage.com for reservations, make sure you tell them you are with the BSATSMC.
A touch of traditional Tuscany in a lively eclectic setting. Après and dinner served daily. Lunch served Saturday and Sunday. Reservations recommended. Located on the first floor of the Village Center.<PHONE_NUMBER>.
Delivery available for guests of the Huntley Lodge, Shoshone, Summit, Village Center and Snowcrest Lodge.<PHONE_NUMBER>.
Proudly serving Starbuck’s coffee. Offering mochas, teas, cappuccinos, chilled beverages, pastries, and light snacks. Located in theMountain Mall.
Casual fine dining with a Euro-western flare and magnificent slope side views. Serving breakfast buffet, fast hearty lunch and elegant dinner. Room service available. Dinner reservations recommended.<PHONE_NUMBER>.
Serving appetizers, dinner and late night with nightly entertainment. Located in the Huntley Lodge.<PHONE_NUMBER>.
Full breakfast buffet with great mountain views. Located in the Huntley Lodge.<PHONE_NUMBER>.
Cozy euro-western atmosphere featuring outstanding cocktails and daily specials. Serving sandwiches and sophisticated small plate selections. Bar menu available. Live music daily. Located in the Summit Hotel.<PHONE_NUMBER>.
Restaurant & bar serving Southwestern specialties and salads. Don’t miss the après nachos! Located in Mountain Mall.<PHONE_NUMBER>.
A unique experience select nights of the week. Reservations required.<PHONE_NUMBER>.
Hearty daily soups to warm you up for an afternoon on the mountain. Located On Mountain in the Bowl up slope from the bottom of the Lone Peak Triple Chair.
Conveniently located on the plaza serving beef and veggie burgers, bratwurst, snacks, drinks, and more. Weather dependent.
Grocery store featuring food staples, deli, homemade soups, fresh pizza, fresh produce, beer, wine, videos, and Montana gifts. Located in Mountain Mall.<PHONE_NUMBER>.
Featuring seafood, steaks and game dishes in a rustic atmosphere. Offering lunch, Après ski, and Dinner. Full service bar. Reservations recommended . Located in the Arrowhead Mall.<PHONE_NUMBER>.
On mountain dining. Serving breakfast and lunch. Located on Larkspur, near the Shedhorn lift.<PHONE_NUMBER>.
Serving coffee and pastries. Located in the Huntley/Shoshone Lobby.
Weekly entertainment, pool tables, foosball, darts, and poker machines. Located next to Mountain Lodge.<PHONE_NUMBER>.
Breakfast and lunch. Offering soups, salad bar, sandwiches, burgers and daily specials. Located in Mountain Mall.<PHONE_NUMBER>.
Featuring gourmet hot dogs, veggie dogs, Montana made ice cream, draft beer and snacks. Open daily. In the Snowcrest Lodge.<PHONE_NUMBER>.
Serving lunch and dinner including steaks, ribs and variety of sandwiches. Located in the Mountain Mall.<PHONE_NUMBER>.
Stop by for appetizers, burgers, sandwiches and drinks in a fun and friendly atmosphere. Live entertainment several nights a week, including open mic nights and DJs. Open for lunch Après ski and dinner. Located in the Arrowhead Mall.<PHONE_NUMBER>.
Discover a unique backcountry dining experience with gourmet Montana cuisine. Featuring a snowcat ride, live music, sledding, anda bonfire. Reservations required.<PHONE_NUMBER>.


Puzzle game ! By Margot E. Beltran Sanchez-07.12.19
1
2
3
4
5
6
7
8
A Sliding Puzzle
by Margot Beltran


{% extends '../base.html' %}
{% load static %}
{% block content %}
{% if settings.GEOCAM_UTIL_LIVE_MODE %}
There are not currently any active EVAs.
When you are told there are active EVAs, please click on the BASALT logo in the upper left.
{% endif %}
| Map | View, manage and edit map layers. Get Google Earth link. |
| {{ settings.XGDS_CORE_FLIGHT_MONIKER }} | View and manage {{ settings.XGDS_CORE_FLIGHT_MONIKER }}s and {{ settings.XGDS_PLANNER2_PLAN_MONIKER }}. A {{ settings.XGDS_CORE_FLIGHT_MONIKER }} includes all of the data collected in a single excursion. |
| {{ settings.XGDS_NOTES_NOTE_MONIKER }} | Review and create {{ settings.XGDS_NOTES_NOTE_MONIKER }}. Manage tags. |
| Sample | Print labels. Record sample information. |
| Search | Search for anything on the map, including Photos, Samples, and Instrument data. |
| Import | Import data including Photos, GPS, Science Instrument, Map Tiles. |
| Status | See current system status |
| xGDS Live | The wrist app! Not on your wrist! |


com.jme3.asset
contains the AssetManager
,
a utility class that is used to load assets such as textures, models, and
sound effects in a jME3 application.See: Description
| Interface | Description |
|---|---|
| AssetEventListener |
AssetEventListener is an interface for listening to various
events happening inside AssetManager . |
| AssetLoader |
An interface for asset loaders.
|
| AssetLocator |
AssetLocator is used to locate a resource based on an AssetKey. |
| AssetManager |
AssetManager provides an interface for managing the data assets
of a jME3 application. |
| AssetProcessor |
AssetProcessor is used to apply processing to assets
after they have been loaded. |
| CloneableSmartAsset |
Implementing the
CloneableSmartAsset interface allows use
of cloneable smart asset management. |
| Class | Description |
|---|---|
| AssetConfig |
AssetConfig loads a config file to configure the asset manager. |
| AssetInfo |
The result of locating an asset through an AssetKey.
|
| AssetKey<T> |
AssetKey is a key that is used to
look up a resource from a cache. |
| CloneableAssetProcessor |
CloneableAssetProcessor simply calls Object.clone()
on assets to clone them. |
| DesktopAssetManager |
AssetManager is the primary method for managing and loading
assets inside jME. |
| FilterKey |
Used to load FilterPostProcessors which are not cached.
|
| MaterialKey |
Used for loading
materials only (not material definitions!). |
| ModelKey |
Used to load model files, such as OBJ or Blender models.
|
| ShaderNodeDefinitionKey |
Used for loading
shader nodes definition
Tells if the defintion has to be loaded with or without its documentation |
| StreamAssetInfo |
An
AssetInfo wrapper for InputStreams . |
| TextureKey |
Used to load textures from image files such as JPG or PNG.
|
| ThreadingManager |
ThreadingManager manages the threads used to load content
within the Content Manager system. |
| Exception | Description |
|---|---|
| AssetLoadException |
AssetLoadException is thrown when the AssetManager
is able to find the requested asset, but there was a problem while loading
it. |
| AssetNotFoundException |
AssetNotFoundException is thrown when the AssetManager
is unable to locate the requested asset using any of the registered
AssetLocator s. |
com.jme3.asset
contains the AssetManager
,
a utility class that is used to load assets such as textures, models, and
sound effects in a jME3 application.
asset loaders
are registered to load
assets of a particular format. For example, an AssetLoader
that
loads TGA images should read a stream in .tga format and return an
Image
object as its output.
AssetLoader
s are initialized once a file of that format
is loaded, there's only one AssetLoader per thread so
AssetLoader's load() method does not have to be thread safe.
AssetLocator
(s) are used to resolve
an asset name (a string) into an InputStream
which is
contained in an AssetInfo
object.
There are AssetLocators
for loading files from the application's
classpath, the local hard drive, a ZIP file, an HTTP server, and more. The user
can implement their own AssetLocators and register them with the AssetManager
to load their resources from their own location.


spritewidget library
A sprite toolkit built on top of Flutter.
Classes
- Action
- Actions are used to animate properties of nodes or any other type of objects. The actions are powered by an ActionController, typically associated with a Node. The most commonly used action is the ActionTween which interpolates a property between two values over time. [...]
- ActionCallFunction
- An action that calls a custom function when it is fired.
- ActionController
- A class the controls the playback of actions. To play back an action it is passed to the ActionController's run method. The ActionController itself is typically a property of a Node and powered by the SpriteBox.
- ActionDelay
- An action that doesn't perform any other task than taking time. This action is typically used in a sequence to space out other events.
- ActionGroup
- An action that plays the supplied actions in parallell. The duration of the ActionGroup will be the maximum of the durations of the actions used to compose this action.
- ActionInstant
- An action that doesn't have a duration. If this class is overridden to create custom instant actions, only the fire method should be overriden.
- ActionInterval
- The abstract class for an action that changes properties over a time interval, optionally using an easing curve.
- ActionRemoveNode
- An action that removes the supplied node from its parent when it's fired.
- ActionRepeat
- An action that repeats another action a fixed number of times.
- ActionRepeatForever
- An action that repeats an action an indefinite number of times.
- ActionSequence
- An action that plays a number of supplied actions in sequence. The duration of the ActionSequence with be the sum of the durations of the actions passed in to the constructor.
- ActionSpline
- The spline action is used to animate a point along a spline definied by a set of points.
-
ActionTween<
T> - An action that tweens a property between two values, optionally using an animation curve. This is one of the most common building blocks when creating actions. The tween class can be used to animate properties of the type Point, Size, Rect, double, or Color.
- ColorSequence
- A sequence of colors representing a gradient or a color transition over time. The sequence is represented by a list of colors and a list of colorStops, the stops are normalized values (0.0 to 1.0) and ordered in the list. Both lists have the same number of elements.
- Constraint
- A constraint limits or otherwise controls a Node's properties, such as position or rotation. Add a list of constraints by setting the Node's constraints property. [...]
- ConstraintPositionToNode
- A Constraint that constrains the position of a node to equal the position of another node, optionally with dampening.
- ConstraintRotationToMovement
- A Constraint that aligns a nodes rotation to its movement.
- ConstraintRotationToNode
- A Constraint that rotates a node to point towards another node. The target node is allowed to have a different parent, but they must be in the same SpriteBox.
- ConstraintRotationToNodeRotation
- A Constraint that copies a node's rotation, optionally with dampening.
- EffectLine
- The EffectLine class is using the TexturedLine class to draw animated lines. These can be used to draw things such as smoke trails, electricity effects, or other animated types of lines.
- GameMath
- Provides convenience methods for calculations often carried out in graphics. Some of the methods are returning approximations.
- ImageMap
- The ImageMap is a helper class for loading and keeping references to multiple images.
- Label
- Labels are used to display a string of text in a the node tree. To align the label, the textAlign property of the TextStyle can be set.
- Layer
- A Node that provides an intermediate rendering surface in the sprite rendering tree. A Layer can be used to change the opacity, color, or to apply an effect to a set of nodes. All nodes that are children to the Layer will be rendered into the surface. If the area that is needed for the children to be drawn is know, the layerRect property should be set as this can enhance performance.
- NineSliceSprite
- A NineSliceSprite is similar to a Sprite, but it it can strech its inner area to fit the size of the Node. This is ideal for fast drawing of things like buttons.
- Node
- A base class for all objects that can be added to the sprite node tree and rendered to screen using SpriteBox and SpriteWidget. [...]
- Node3D
- An node that transforms its children using a 3D perspective projection. This node type can be used to create 3D flips and other similar effects. [...]
- NodeWithSize
- The super class of any Node that has a size. [...]
- ParticleSystem
- A particle system uses a large number of sprites to draw complex effects such as explosions, smoke, rain, or fire. There are a number of properties that can be set to control the look of the particle system. Most of the properties have a base value and a variance, these values are used when creating each individual particle. For instance, by setting the life to 1.0 and the lifeVar to 0.5, each particle will get a life time in the range of 0.5 to 1.5. [...]
- Sprite
- A Sprite is a Node that renders a bitmap image to the screen.
- SpriteBox
-
A
RenderBox
that draws a sprite world represented by a Node tree. - SpriteBoxEvent
- An event that is passed down the node tree when pointer events occur. The SpriteBoxEvent is typically handled in the handleEvent method of Node.
- SpritePaint
- Defines properties, such as opacity and transferMode that are shared between Nodes that render textures to screen.
- SpriteSheet
- A sprite sheet packs a number of smaller images into a single large image. [...]
- SpriteTexture
- A texture represents a rectangular area of an image and is typically used to draw a sprite to the screen. [...]
- SpriteWidget
- A widget that uses a SpriteBox to render a sprite node tree to the screen.
- TexturedLine
- A Node that draws a polyline from a list of points using the provided SpriteTexture. The textured line draws static lines. If you want to create an animated line, consider using the EffectLine instead.
- TexturedLinePainter
- Draws a polyline to a Canvas from a list of points using the provided SpriteTexture.
- VirtualJoystick
- Provides a virtual joystick that can easily be added to your sprite scene.
Functions
-
convertDegrees2Radians(
double degrees) → double - Converts degrees to radians.
-
convertRadians2Degrees(
double radians) → double - Converts radians to degrees.
-
deserializeBlendMode(
int data) → BlendMode -
deserializeColor(
int data) → Color -
deserializeColorSequence(
Map data) → ColorSequence -
deserializeOffset(
List< double> data) → Offset -
deserializeParticleSystem(
Map data, { ParticleSystem particleSystem, SpriteTexture texture }) → ParticleSystem -
randomBool(
) → bool -
Returns either
true
orfalse
in a most random fashion. -
randomDouble(
) → double - Returns a random double in the range of 0.0 to 1.0.
-
randomInt(
int max) → int - Returns a random int from 0 to max - 1.
-
randomSignedDouble(
) → double - Returns a random double in the range of -1.0 to 1.0.
-
serializeBlendMode(
BlendMode blendMode) → int -
serializeColor(
Color color) → int -
serializeColorSequence(
ColorSequence colorSequence) → Map -
serializeOffset(
Offset offset) → List< double> -
serializeParticleSystem(
ParticleSystem system) → Map
Enums
- EffectLineAnimationMode
- Used by EffectLine to determine how the texture of the line is animated.
- EffectLineWidthMode
- Used by EffectLine to determine how the width of the line is calculated.
- SpriteBoxTransformMode
- Options for setting up a SpriteBox's coordinate system.
Typedefs
-
ActionCallback(
) → void -
Signature for callbacks used by the
ActionCallFunction
. -
PointSetterCallback(
Offset value) → void -
Signature for callbacks used by the
ActionSpline
to set aPoint
value. -
SetterCallback(
dynamic value) → void -
Signature for callbacks for setting properties, used by
ActionTween
.


The mission of The London Django Meetup Group is to provide a fun, welcoming and professional environment for a diverse group of people.
Code of conduct: https://www.djangolondon.com/code-of-conduct/
Tonight's meetup is kindly sponsored by:
Europe's largest music festival platform, and UK's 6th fastest growing private tech start up.
Transforming the way music fans discover, book tickets and travel packages for festivals around the world.
The trusted global platform that inspires and enables people to experience the best of the city. Operating in 107 cities, across 39 countries, it has an average monthly global audience reach of over 111 million across all platforms.
We turn word of mouth into your best sales channel.
February 2019 • PyCon Colombia
Copenhagen April 10-14th • DjangoCon Europe 2019
Django 2.2 beta 1 released
Django bugfix releases: 2.1.7, 2.0.12 and 1.11.20
Mariusz Felisiak selected to replace Tim Graham as a Django Fellow by DSF
Python Developers Survey 2018 is out - Learn about the community
Build search into your Django app
by Emanuil Tolev
Django: breaking the monolith!
by Raul Tavares
Lightning talk: Impulse Demo
by David Seddon
The Space Bar until ~20:45
Migrate to the Red Lion Pub (opposite)
Please come and chat with us!
Come and grab a sticker after the talks.
Pink: I want to hire
Yellow: Hire me!
Website: https://djangolondon.com
Twitter: @djangolondon
Github: https://github.com/djangolondon/
Slack: https://londondjangomeetup.herokuapp.com/
Open Collective: https://opencollective.com/the-london-django-meetup-group/


Uses of Ontology/KG
- Formally (machine processable) represent the knowledge of a domain
- Make the knowledge shareable (by other applications), and reusable
- The knowledge that is in your/domain expert's head is given a structure and put out
- Your intuitions, heuristics could be captured in the form of an ontology
- If the dictionaries, and vocabularies that you use have hierarchies, relationships, then an it can be represented as an ontology
- Ontology can give a good description of your data (data documentation)
- Makes the data usable
- Data can be converted to structured data (RDF)
- Data integration
- IRIs make it easy to integrate the same entities from different data sources
- Different data formats can be converted to one unified RDF format
- Ontology + KG enables automated reasoning
Uses of Reasoning
- Get complete answers
- SubClassOf(Baby Child)
- SubClassOf(Child Person)
- ClassAssertion(Baby s)
- Consistency of the knowledge base can be checked/maintained
- DisjointClasses(Vertebrates Invertebrates)
- ClassAssertion(Vertebrates xyz)
- ClassAssertion(Invertebrates xyz)
- Get explanation for the decisions/output given by the reasoner
Ontology/KG construction
- If KG is for a single/narrow domain, build an ontology first
- You would know the concepts and relations that you are interested in
- Instances (from text) can be mapped to one of the concepts
- Relations can be mapped to one of the "clean" relations in the ontology


Hideo Kojima made a penguin delivery game before Death Stranding
Follow Polygon online:
by Julia LeeBefore Death Stranding, game developer Hideo Kojima made a different game about delivering packages: Penguin Adventure.
Kojima was the assistant designer on Penguin Adventure when it released in 1986 for MSX, according to an article by MSPoweruser. The game is a sequel to Antarctic Adventure and was the first game that Kojima was able to work on at Konami. Penguin Adventure follows the story of Penta, a penguin who has to bring home a golden apple to cure the penguin princess. While this story isn’t as meaningful as Death Stranding’s, they both focus on an earnest guy just trying to make some deliveries.
Related
For a game made over 30 years ago, Penguin Adventure had some in-depth features, like alternative endings, something Kojima would end up using again in his later works.
Penguin Adventure still lives and has been re-released as recently as 2014 in Japan for Windows. Unfortunately Penguin Adventure hasn’t been brought stateside ever. It released in Europe in 1987, though it never quite made it to America. While it might be hard to find and play now, you can check out a playthrough below.


Collection
Documents on the key stage 2 (KS2) testing review.
Information on the Lord Bew review of the key stage 2 testing, assessment and accountability system to define clearly the purposes of statutory assessment in primary education and what it should achieve in the future. We ran a call for evidence in November 2010 . The final report was published on 23 June 2011.
Published: 23 June 2011


×
Overview
Analytics
Home
Summary
Improvements In kUSD
Financial Overview
Goal by Metrics
Where are losses coming from?
Major Contributing Losses


We were able to successfully gather your data.
Congratulations! Your loan has been approved.
Our representative will get in touch with you for document collection.


|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
| Class Summary | |
|---|---|
| CSVLoader | A load function based on PigStorage that implements part of the CSV "standard" This loader properly supports double-quoted fields that contain commas and other double-quotes escaped with backslashes. |
| DBStorage | |
| HadoopJobHistoryLoader | |
| HadoopJobHistoryLoader.HadoopJobHistoryInputFormat | |
| HadoopJobHistoryLoader.HadoopJobHistoryReader | |
| HadoopJobHistoryLoader.JobHistoryPathFilter | |
| HadoopJobHistoryLoader.MRJobInfo | |
| HiveColumnarLoader | Loader for Hive RC Columnar files. Supports the following types: * Hive Type Pig Type from DataType string CHARARRAY int INTEGER bigint or long LONG float float double DOUBLE boolean BOOLEAN byte BYTE array TUPLE map MAP Partitions The input paths are scanned by the loader for [partition name]=[value] patterns in the subdirectories. If detected these partitions are appended to the table schema. For example if you have the directory structure: |
| JsonMetadata | Reads and Writes metadata using JSON in metafiles next to the data. |
| MultiStorage | The UDF is useful for splitting the output data into a bunch of directories and files dynamically based on user specified key field in the output tuple. |
| MultiStorage.MultiStorageOutputFormat | |
| MultiStorage.MultiStorageOutputFormat.MyLineRecordWriter | |
| MyRegExLoader | |
| PigStorageSchema | This Load/Store Func reads/writes metafiles that allow the schema and aliases to be determined at load time, saving one from having to manually enter schemas for pig-generated datasets. |
| RegExLoader | RegExLoader is an abstract class used to parse logs based on a regular expression. |
| SequenceFileLoader | A Loader for Hadoop-Standard SequenceFiles. |
| XMLLoader | The load function to load the XML file This implements the LoadFunc interface which is used to parse records from a dataset. |
| XMLLoader.XMLFileInputFormat | |
| XMLLoader.XMLFileRecordReader |
| Enum Summary | |
|---|---|
| HadoopJobHistoryLoader.JobKeys | Job Keys |
|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |


Try our amazing products
Find out what awesome things we have done!
Build user friendly and innovative applications!
All our applications are completely free of advertisement
All our apps are free to use!
Most of our apps are open-source, feel free to contribute!


Try out our Premium Member services: Virtual Legal Assistant, Query Alert Service and an ad-free experience. Free for one month and pay only if you like it.
IN THE SUPREME COURT OF INDIA CRIMINAL APPELLATE JURISDICTION CRIMINAL APPEAL NO. 152 OF 2012 P. Pramila and others ..Appellants versus State of Karnataka and another ..Respondents WITH CRIMINAL APPEAL NO. 153 OF 2012 CRIMINAL APPEAL NO. 154 OF 2012 CRIMINAL APPEAL NO. 155 OF 2012 J U D G M E N T
JAGDISH SINGH KHEHAR, J.
The appellants, while being engaged in the business of stocking iron ore, had allegedly violated certain norms prescribed by the Deputy Commissioner under Section 22 of the Air (Prevention and Control of Pollution) Act, 1981 (hereinafter referred to as the 'Air Act'). The allegation against the appellants was, that they had illegally established iron ore stack yard(s) at various places in Uttara Kannada District. It was alleged, that the appellants had not made provisions for pollution control measures, despite repeated requests and instructions given to them, by the officials of the Karnata State Pollution Control Board (hereinafter referred to as the 'Board'). It was therefore, that CC No.546/2006, CC No.547/2006, CC No.548/2006 and CC No.549/2006 were filed before the Judicial Magistrate, First Class-II, Karwar. The proceedings against the appellants were sought to be challenged by petitions filed under Section 482 of the Code of Criminal Procedure, wherein the appellants prayed for quashing of the above proceedings.
A number of similar criminal petitions, filed by the appellants and others, were sought to be disposed of by the High Court of Karnataka, Circuit Bench at Dharwad (hereinafter referred to as the 'High Court'), by a common order dated 7.1.2009. The above order dated 7.1.2009, is subject to challenge in these appeals. A perusal of the impugned order reveals, that the High Court did not examine the merits of the controversy. To dispose of the merits of the claim raised by the appellants before the High Court, it relied upon an earlier order passed by the High Court on 17.04.2007, disposing of Criminal Petition No. 4760 of 2006. Based thereon, the challenge raised by the appellants before this Court, was also sought to be rejected. The factual position indicated hereinabove is apparent from paragraphs 3 to 5 of the impugned order, which are being extracted hereunder:
"3. The allegations against the respective petitioner is that, while being engaged in the business of stocking iron ore, the petitioners have violated the norms prescribed by the Deputy Commissioner and thus offence un/s 22 of the Pollution Control Act, has been committed and the further allegation in the complaint is that the petitioners have illegally established and operating iron ore stack yard at various places in Uttara Kannada District without the previous consent of the Karnataka State Pollution Control Board (for short, 'the Board') and that the accused petitioners have not provided any pollution control measures despite repeated requests and instruction given to them by the officials of the Board. Based on the complaint lodged by the Board, learned Magistrate of the trial Court directed issuance of process against the petitioners. It is this order of the trial Court that is called in question in all these petitions.
4. At the outset, learned counsel for the respondents submitted that the present petitions are liable to be dismissed as all the grounds urged in the present petitions by each one of the petitioner have been considered by this Court in a batch of petitions which were disposed of on 17.4.2007 in Crl. Petition No. 4760/06 and connected petitions. Therefore, the present petitions are also liable to be dismissed following the aforesaid order of this Court.
5. Learned counsel appearing for the respective petitioner have not disputed the fact of this court having already dismissed the other petitions filed by the petitioners which are similarly placed and all the contentions which are urged in the present petitions have been considered by the learned single Judge while dismissing batch of petitions on 17.4.2007."
During the course of hearing, learned counsel for the appellants invited our attention to the fact, that cognizance of an offence could be taken only by the Board or an officer authorised by the Board, in terms of Section 43 of the Air Act. Section 43 afore-mentioned, was the primary basis of the challenge raised before us. The same is being reproduced hereunder:
"43. Cognizance of offences - (1) No court shall take cognizance of any offence under this Act except on a complaint made by -
(a) a Board or any officer authorised in this behalf by it; or
(b) any person who has given notice of not less than sixty days, in the manner prescribed, of the alleged offence and of his intention to make a complaint to the Board or officer authorised as aforesaid, and no court inferior to that of a Metropolitan Magistrate or a Judicial Magistrate of the first class shall try any offence punishable under this Act.
(2) Where a complaint has been made under clause (b) of sub-section (1), the Board shall, on demand by such person, make available the relevant reports in its possession to that person:
Provided that the Board may refuse to make any such report available to such person if the same is, in its opinion, against the public interest."
Our attention has been pointedly invited to sub-section (1) of Section 43 of the Air Act. Having perused the same, there cannot be any doubt, that when the authorities decided to initiate proceedings under the provisions of the Air Act, the complaint could have been made either by the Board or by an officer authorised by the Board. The question which has to be adjudicated upon (as has been raised by the appellants), was whether, the complaint in furtherance of which CC No. 546/2006, CC No.547/2006, CC No.548/2006 and CC No.549/2006, had been filed by the Board, or an officer authorised by the Board. To be valid, in terms of the mandate of Section 43(1) of the Air Act, it ought to be filed either by the Board or by an officer authorised by the Board.
Insofar as the above mentioned aspect of the matter is concerned, it is not a matter of dispute, that vide notification/resolution dated 29.3.1989, the Karnataka State Pollution Control Board delegated certain powers to the Chairman of the Board. The aforesaid resolution (limited to the instant issue), is being reproduced below: "subject : Delegation/Empowering of Technical, No.63.11 Administrative and Finalcial Powers to Chairman, Member Secretary and Other Officers working in the Board.
The subject of Delegation of Power to the Chairman was also discussed, while subject No.10 was being discussed. After detailed discussion, the Board decided to delegate its power and functions to the Chairman of the Board in terms of Section 11A of the Water(Prevention and Control of Pollution)Act, 1978 (Amended) and Section 15 of Air (Prevention and Control of Pollution) Act, 1981 under the following circumstances:
a) In respect of industries who are discharging their effluent without a valid consent under Section 25/26 of the Water (Prevention and Control of Pollution) Act, 1974 and under Section 23 of the Air (Prevention and Control of Pollution) Act, 1981, the Chairman is authorized to initiate legal action under relevant sections.
b) In respect of Industries against whom orders passed by the Chairman under Section 32(1)(c) of the Water (Prevention and Control of Pollution) Act, 1974 and under Section 23 of the Air (Prevention and Control of Pollution) Act, 1981 and if such Units have not complied with the directions issued, the Chairman of the Board is authorized to initiate legal action for violating the direction issued under Section 32(1)(c) under Water Act and Section 23 of the Air Act, under relevant penal provision of the respective Acts.
The Legal Action initiated in terms of above delegation of powers, the Board shall be kept informed at the next immediate meeting."
The Board could delegate the above power to the Chairman of the Board, because Section 43(1) of the Air Act, allowed it to do so. In view of the conclusions recorded above, consequent upon the passing of the resolution dated 29.3.1989, the complaint under Section 43(1) of the Air Act, could have been filed either by the Board or by its Chairman.
According to the learned counsel for the respondents, proceedings came to be initiated by an order dated 4.4.2006 passed by the Chairman of the Karnataka State Pollution Control Board. Relevant extract of the above order is reproduced below:
"In view of the above, I do here by authorize the Regional Officer, Karwar to initiate criminal action under Section 37 of Air (Prevention and Control of Pollution) Act, 1981 by filing criminal case in the competent court against 17 occupiers of the Iron Ore Stack Yards located in and around the Karwar, Ankola and Jolda Taluks of Uttara Kannada District as per the list enclosed as Annexure-1."
Having perused the aforesaid communication it emerges, that the Chairman of the Board authorised the Regional Office, Karwar to initiate criminal action under Section 37 of the Air Act, by filing criminal cases in Courts having jurisdiction to deal with them, against 17 owners of iron ore stack yards, located in and around the Karwar, Ankola and Jolda Taluks of Uttara Kannada District. It is not possible to accept, the contention of the respondents, that initiation of the proceedings on the basis of the above order dated 4.4.2006 can be treated as compliance of the mandate contained in Section 43(1) of the Air Act, because the same has reference to a complaint made by the "Board or any officer authorised in this behalf by it".
In compliance with the order of the Chairman dated 4.4.2006, the Regional Officer(Deputy Environmental Officer Sri Gopalakrishna B. Sanatangi, filed complaints before the Judicial Magistrate, First Class-II, Karwar. It is natural therefore to conclude, that the complaint against the appellants was neither filed by the Board or its Chairman, but was filed by the Regional Officer (Deputy Environmental Officer).
Section 43 of the Air Act has already been extracted hereinabove. It is apparent therefrom, that Courts would take cognizance of complaints filed by the Board, or any officer authorised by the Board, in that behalf. The notification/resolution dated 29.3.1989 indicates, that the officer authorised was the Chairman of the Board. The Board could delegate the above power to the Chairman of the Board, because Section 43(1) of the Air Act, authorised the Board to do so. In that view of the matter, either the Board or the Chairman of the Board could have filed the complaints in terms of the mandate contained in Section 43(1) of the Air Act. The power to file the complaint could not be exercised by any other authority/officer. Under the principle of 'delegatus not potest delegare', the delegatee (the Chairman of the Board) could not have further delegated the authority vested in him, except by a clear mandate of law. Section 43 of the Air Act vested the authority, to file complaints with the Board. Section 43 afore-mentioned, also authorised the Board to delegate the above authority to any "officer authorised in this behalf by it". The "officer authorised in this behalf" was not authorised by the provisions of Section 43 of the Air Act, or by any other provision thereof, to further delegate, the authority to file complaints. The Chairman of the Board, therefore, had no authority to delegate the power to file complaints, to any other authority, for taking cognizance of offences under the Air Act. It is apparent, that the determination to initiate action against the appellants, and other similarly placed persons, against whom action was proposed to be taken, by the Chairman of the Board, vide his order dated 4.4.2006, was not in consonance with law. Annexure P-11, appended to Criminal Appeal No. 152/2012 reveals, that the complaint was filed, and the proceedings were initiated before the Judicial Magistrate, First Class-II, Karwar, by the Regional Officer(Deputy Environmental Officer) Sri Gopalakrishna B. Sanatangi, in his capacity as a complainant. The Regional Officer(Deputy Environmental Officer) Sri Gopalakrishna B. Sanatangi, had no jurisdiction to prefer such complaints. Accordingly, we are of the view, that the afore- stated complaints dated 28.04.2006 are liable to be set aside, on the instant technical ground itself. Ordered accordingly.
Since the petitions filed by the appellants, under Section 482 of the Criminal Procedure Code, are being accepted merely on a technical ground, we hereby direct the competent authority, namely, the Board (or the Chairman of the Board) to re-initiate the above proceedings, in consonance with the provisions of Section 43(1) of the Air Act. The process shall positively be re-initiated within two months from today. In case of failure to initiate fresh proceedings within the time stipulated hereinabove, it shall be imperative for the competent authority, to place the reasons for not doing so before this Court, on the expiry of a period of two months. Extension of time, if needed, shall also be sought by the authorities from this Court, by moving an appropriate interlocutory application. Needless to mention, that on re-initiation of the proceedings, the concerned authorities, and the Courts below, shall not take into consideration any observations recorded by us, or the Courts below, while adjudicating upon the merits of instant controversy. It shall be open to the parties to raise all contentions, as may be available to them, in consonance with law.
The instant appeals are allowed in the aforesaid terms.
.......................J.
[JAGDISH SINGH KHEHAR] NEW DELHI; .......................J. APRIL 09, 2015.  Appellant(s) VERSUS STATE OF KARNATAKA & ANR Respondent(s) (with appln. (s) for directions and stay) WITH Crl.A. No. 153/2012 Crl.A. No. 154/2012 Crl.A. No. 155/2012
Date : 09/04/2015 These appeals were called on for hearing today.
CORAM :
HON'BLE MR. JUSTICE JAGDISH SINGH KHEHAR HON'BLE MR. JUSTICE S.A. BOBDE For Appellant(s) Mr. K.K. Venugopal, Sr. Adv.
In AR 152/2012 Mr. Anish Dayal, Adv. Mr. Siddharth Vaid, Adv. Mr. Ishwar Mohanty, Adv. Ms. Anjali, Adv. for Ms. Jyoti Mendiratta,AOR For Appellant(s) Mr. T.S. Doabia, Sr. Adv. In other appeals Mr. Sharan Thakur, Adv. Mr. Murthy Nair, Adv. Mr. Vijay Kumar, Adv. for Dr. Sushil Balwada,AOR For Respondent(s) Mr. Purushottam Sharma Tripathi,Adv. Mr. S.J. Amith, Adv. Mr. R.C. Prakash, Adv. Mr. Ashok, Adv. Mr. Mukesh Kr. Singh, Adv. Ms. Anitha Shenoy,Adv.
UPON hearing the counsel the Court made the following O R D E R The appeals are allowed in terms of the signed judgment.
(Parveen Kr. Chawla) (Renu Diwan) Court Master Court Master [signed Judgment is placed on the file]


IF_NAMEINDEX
Section: Linux Programmer's Manual (3)
Updated: 2012-11-21
Index
Return to Main Contents
NAME
if_nameindex, if_freenameindex - get network interface names and indexes
SYNOPSIS
#include <net/if.h>
struct if_nameindex *if_nameindex(void);
void if_freenameindex(struct if_nameindex *ptr);
DESCRIPTION
The
if_nameindex()
function returns an array of
if_nameindex
structures, each containing information
about one of the network interfaces on the local system.
The
if_nameindex
structure contains at least the following entries:
unsigned int if_index; /* Index of interface (1, 2, ...) */
char *if_name; /* Null-terminated name ("eth0", etc.) */
The
if_index
field contains the interface index.
The
ifa_name
field points to the null-terminated interface name.
The end of the array is indicated by entry with
if_index
set to zero and
ifa_name
set to NULL.
The data structure returned by
if_nameindex()
is dynamically allocated and should be freed using
if_freenameindex()
when no longer needed.
RETURN VALUE
On success,
if_nameindex()
returns pointer to the array;
on error, NULL is returned, and
errno
is set appropriately.
ERRORS
if_nameindex()
may fail and set
errno
if:
- ENOBUFS
-
Insufficient resources available.
if_nameindex()
may also fail for any of the errors specified for
socket(2),
bind(2),
ioctl(2),
getsockname(2),
recvmsg(2),
sendto(2),
or
malloc(3).
VERSIONS
The
if_nameindex()
function first appeared in glibc 2.1, but before glibc 2.3.4,
the implementation supported only interfaces with IPv4 addresses.
Support of interfaces that don't have IPv4 addresses is available only
on kernels that support netlink.
CONFORMING TO
RFC 3493, POSIX.1-2001.
This function first appeared in BSDi.
EXAMPLE
The program below demonstrates the use of the functions described
on this page.
An example of the output this program might produce is the following:
$ ./a.out
1: lo
2: wlan0
3: em1
Program source
#include <net/if.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
int
main(int argc, char *argv[])
{
struct if_nameindex *if_ni, *i;
if_ni = if_nameindex();
if (if_ni == NULL) {
perror("if_nameindex");
exit(EXIT_FAILURE);
}
for (i = if_ni; ! (i->if_index == 0 && i->if_name == NULL); i++)
printf("%u: %s\n", i->if_index, i->if_name);
if_freenameindex(if_ni);
exit(EXIT_SUCCESS);
}
SEE ALSO
getsockopt(2),
setsockopt(2),
getifaddrs(3),
if_indextoname(3),
if_nametoindex(3),
ifconfig(8)
Index
- NAME
-
- SYNOPSIS
-
- DESCRIPTION
-
- RETURN VALUE
-
- ERRORS
-
- VERSIONS
-
- CONFORMING TO
-
- EXAMPLE
-
- Program source
-
- SEE ALSO
-
This document was created by
man2html,
using the manual pages.
Time: 02:55:09 GMT, September 18, 2014