Sponsored Content
Top Forums Programming Wuhan Coronavirus Status for China - Rapid Prototype Blynk App with ESP8266 Post 303043640 by Neo on Sunday 2nd of February 2020 10:25:57 PM
 

6 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Function prototype declaration

Hi All, I have the script as below #!bin/bash let k=9 if then echo "Start" Hello echo "End" else echo "failed" fi function Hello() { echo "hello !!!!" } I got the below error : (4 Replies)
Discussion started by: Balasankar
4 Replies

2. Programming

Embarcadero Rapid SQL query for dependency

Team I am using Embarcadero Rapid SQL V8 . When we right click on any procedure/table/view and open the contents. It has dependencies tab, which tell what all are the dependents used . My question is how does this information captured in backend to retrieve the dependency objects in... (0 Replies)
Discussion started by: Perlbaby
0 Replies

3. What is on Your Mind?

Major Changes in New UserCP (v0.63) Prototype

Regarding the latest version of the UserCP prototype (version 0.63) I have made a lot of major changes, including Added a "Posts Timeline" table for the recent posts, complimenting the non-table version earlier, which has been moved off the main menu (link at the bottom of the table). Added a... (4 Replies)
Discussion started by: Neo
4 Replies

4. Programming

NodeMCU ESP8266 Blynk SSL Application for Linux Server Load Averages

Here is a useful SSL (HTTPS) application for anyone with a remote Linux server they want to keep an eye on using Blynk and the NodeMCU ESP8266. This little app also works (have tested as well) on the WeMos D1 ESP8266 Arduino board. The NodeMCU setup could not be easier, just find a... (8 Replies)
Discussion started by: Neo
8 Replies

5. Programming

Wuhan Coronavirus Status App for China - Rapid Prototype using MQTT and the IoT OnOff IOS App

With a little bit of work, was able to build a nice "Wuhan Coronavirus Status" app using MQTT and the IoT-OnOff app. More on this technique here: ESP32 (ESP-WROOM-32) as an MQTT Client Subscribed to Linux Server Load Average Messages The result turned out nice, I think. I like the look and... (10 Replies)
Discussion started by: Neo
10 Replies

6. Programming

A Slightly Better NTP Client for the ESP8266

Was not really happy with the NTP clients for the ESP8266 because, after a few years of game engine programming, I am not a fan of a lot of code and delays in the main loop, so here is a "slightly better NTP client" for the ESP8266. In a nutshell, instead of having a delay in the main loop as a... (1 Reply)
Discussion started by: Neo
1 Replies
App::Info::Handler::Carp(3pm)				User Contributed Perl Documentation			     App::Info::Handler::Carp(3pm)

NAME
App::Info::Handler::Carp - Use Carp to handle App::Info events SYNOPSIS
use App::Info::Category::FooApp; use App::Info::Handler::Carp; my $carp = App::Info::Handler::Carp->new('carp'); my $app = App::Info::Category::FooApp->new( on_info => $carp ); # Or... my $app = App::Info::Category::FooApp->new( on_error => 'croak' ); DESCRIPTION
App::Info::Handler::Carp objects handle App::Info events by passing their messages to Carp functions. This means that if you want errors to croak or info messages to carp, you can easily do that. You'll find, however, that App::Info::Handler::Carp is most effective for info and error events; unknown and prompt events are better handled by event handlers that know how to prompt users for data. See App::Info::Handler::Prompt for an example of that functionality. Upon loading, App::Info::Handler::Carp registers itself with App::Info::Handler, setting up a number of strings that can be passed to an App::Info concrete subclass constructor. These strings are shortcuts that tell App::Info how to create the proper App::Info::Handler::Carp object for handling events. The registered strings are: carp Passes the event message to "Carp::carp()". warn An alias for "carp". croak Passes the event message to "Carp::croak()". die An alias for "croak". cluck Passes the event message to "Carp::cluck()". confess Passes the event message to "Carp::confess()". INTERFACE
Constructor new my $carp_handler = App::Info::Handler::Carp->new; $carp_handler = App::Info::Handler::Carp->new( level => 'carp' ); my $croak_handler = App::Info::Handler::Carp->new( level => 'croak' ); Constructs a new App::Info::Handler::Carp object and returns it. It can take a single parameterized argument, "level", which can be any one of the following values: carp Constructs a App::Info::Handler::Carp object that passes the event message to "Carp::carp()". warn An alias for "carp". croak Constructs a App::Info::Handler::Carp object that passes the event message to "Carp::croak()". die An alias for "croak". cluck Constructs a App::Info::Handler::Carp object that passes the event message to "Carp::cluck()". confess Constructs a App::Info::Handler::Carp object that passes the event message to "Carp::confess()". If the "level" parameter is not passed, "new()" will default to creating an App::Info::Handler::Carp object that passes App::Info event messages to "Carp::carp()". BUGS
Please send bug reports to <bug-app-info@rt.cpan.org> or file them at <http://rt.cpan.org/NoAuth/Bugs.html?Dist=App-Info>. AUTHOR
David Wheeler <david@justatheory.com> SEE ALSO
App::Info documents the event handling interface. Carp of documents the functions used by this class. App::Info::Handler::Print handles events by printing their messages to a file handle. App::Info::Handler::Prompt offers event handling more appropriate for unknown and confirm events. App::Info::Handler describes how to implement custom App::Info event handlers. COPYRIGHT AND LICENSE
Copyright (c) 2002-2008, David Wheeler. Some Rights Reserved. This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.10.1 2011-03-15 App::Info::Handler::Carp(3pm)
All times are GMT -4. The time now is 01:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy