text:
Difference between revisions of "Version history"
|Line 166:
|Line 166:
* Support puck.js as external Bluetooth sensor.
* Support puck.js as external Bluetooth sensor.
===Changes on Android===
===Changes on Android===
Revision as of 09:16, 29 September 2022
This page lists all published phyphox versions with details and changelogs. Below you will first find an overview table, followed by detailed information on each version.
|Release date
|File format
|Initial release
|Bugfixes and minor improvements
|New experiments: Centrifugal acceleration and inclination
|New experiment: Acoustic stopwatch, disable unavailable experiments
|Bugfixes and minor improvements
|Experiments: Inelastic collision and timers, many improvements to existing experiments
|GPS, state saving, acceleration and magnetic spectrum
|Hotfix for iOS only.
|Czech and Polish translation
|Dutch and Russian translation
|Italian and Greek translation. Roll experiment removed from iOS.
|Portuguese translation.
|Hotfix for iOS only.
|Japanese translation. Minor bugfix.
|Bluetooth Low Energy, interactive graphs, loading experiments from zip files and QR codes, Open source
|Bugfixes, minor improvements, bright mode in remote access
|Network interface, many minor improvements and bugfixes
|Hotfix for iOS only.
|Spanish and Turkish translation, bugfixes
|Improved audio engine to directly generate tones and white noise, bugfixes
|Network connection with MQTT. Minor improvements and bugfixes.
|Improved time handling across system time, (sensor) event times and experiment time. Time axes can be switched to system time ("wall clock" time). Metadata export.
|New acoustic and improved countdown for timed run experiments.
|Customizable and improved sensor rate strategies, experimental LiDAR support
|Bug fixes, official depth sensor support (LiDAR/ToF), improved consistency between Android and iOS version, new settings menu
|Bug fixes
- 1 1.1.12
- 2 1.1.11
- 3 1.1.10
- 4 1.1.9
- 5 1.1.8
- 6 1.1.7
- 7 1.1.6
- 8 1.1.5
- 9 1.1.4
- 10 1.1.3
- 11 1.1.2
- 12 1.1.1
- 13 1.1.0
- 14 1.0.16
- 15 1.0.15
- 16 1.0.14
- 17 1.0.13
- 18 1.0.12
- 19 1.0.11
- 20 1.0.10
- 21 1.0.9
- 22 1.0.8
- 23 1.0.7
- 24 1.0.6
- 25 1.0.5
- 26 1.0.4
- 27 1.0.3
- 28 1.0.2
- 29 1.0.1
- 30 1.0.0
Changes on Android and iOS
- Support puck.js as external Bluetooth sensor.
- Fix: Output NaN instead of 0 if bearing, speed or altitude is not available in a location (GPS) event.
Changes on Android
- Decode percent-encoding in requests to the REST API.
Changes on Android and iOS
- Depth sensor (LiDAR / ToF) experiment available in tools section.
- New settings menu.
- Option to turn off screen if proximity sensor is triggered.
- Option to override system language settings.
- Option to change the remote access port.
- Improved method to determine significant digits on plot axes.
- Only show hint to new support options if they have been added in the current version.
- Visual feedback added when switching tone generator to multi tone mode.
- Show resolution in spectrum experiments.
- Bluetooth peripherals can implement an event characteristic to receive start/pause events with time synchronization information.
- Fix: Ignored localized decimal points (i.e. comma) when entering and displaying values.
Changes on Android
- Do not return to collection view after adding an experiment to it.
- Write sampe rate already on cycle 0.
- Fix: Inelastic collision requires initial press on "reset" to work.
- Fix: Crash if screenshot of a map graph is taken in landscape orientation.
- Fix: Catch unreasonable data sizes for experiment configurations sent via BLE.
- Fix: Random crash when stopping depth sensor measurement.
- Fix: Prevent data buffers of edit fields from being cleared.
Changes on iOS
- Use TrueDepth camera (front-facing camera for FaceID on all recent iPhones) as depth sensor.
- Refactor analysis modules to be consistent with the way they work on the Android version.
- This also fixes bugs related to reusing buffers as input and output on the same module and clearing in the if module.
- And this also fixes the applause meter.
- Only use reference frame with magnetic north if required by attitude sensor or calibrated magnetometer. (Should make some sensors available on devices with broken magnetometer.)
- Edit views now use a numeric keyboard with added "+/-" and "done" buttons.
- Fix: Crash in apply zoom dialog if selecting axes/units etc. on iPads.
- Fix: Avoid flickering graphs by only redrawing them after analysis cycle has been completed.
- Fix: Crash and mismatched inputs of analysis module "map".
- Fix: Do not apply sleep time to first analysis cycle.
- Fix: Placeholder for common strings is not replaced if no translation block is present.
File format update to version 1.15
- Send tags in network connections now support a clear attribute. (This has already been implemented in the Android, but was not yet documented.)
- New attribute for graphs to follow new data by default: "followX"
- New supported sensor type: gravity
- Bluetooth outputs (input tag within an output) support an offset attribute and multiple entries targeting the same characteristic will be combined accordingly. This allows sending multiple buffers to the same characteristic, for example to submit x, y and z from a 3D sensor.
Changes on Android and iOS
- New sensor rate strategies, which now default to "auto" (see https://phyphox.org/wiki/index.php/Phyphox_file_format#Input_module:_sensor).
- Experimental depth sensor support for devices with LiDAR (newer iPhone Pro and iPad Pro) or ToF (Android, tested on Samsung G10 5G) sensors. This feature is currently hidden. See https://phyphox.org/lidar for ways to try it.
- Translations of common units, quantities and similar short expressions are handled by the app and not in the file format, allowing for more nuanced translations that have been previously been prevented by name collisions (for example "s" for seconds and "S" for south).
- Added a filter to prevent formula injection into Excel via CSV.
- Time axis on the history plot of the applause meter has been disabled as this is only a rolling peek at the history and the time axis forces phyphox to plot from the beginning of the experiment.
- Fix: Analysis only executed once or not at all after user input if experiment is paused. (This for example caused the sample number in audio spectrum to only update after starting the measurement.)
- Context menu next to externally loaded experiments in the main menu now defaults to white if luminance is too low (also fix non-linear luminance calculation on iOS version)
- Fix: In remote access simple value elements break data requests for preceding graphs with same buffers. (Most notably breaking remote access for the inclination experiment and absolute plots on 3 axis sensors.)
Changes on Android
- Fix: Export via remote access not working in Excel format and some metadata missing in CSV.
- Fix: Export in Excel format not working on pre Android 7 devices.
- Fix: Youtube links blocked on Android 11.
- Fix: REST API returns success when setting a value via cmd=set failes due to a non-parsable numeric value.
- Fix: Crash due to race condition when clearing a buffer that is shown in a graph.
- Fix: Crash due to another race condition in experiments that calculate audio output in their analysis block.
- Fix: Change source for Paho MQTT library to fix broken F-Droid build process. (phyphox 1.1.9 should already have become available on F-Droid again thanks to a quick fix by "linsui")
- New automatic strategies to fix bad timestamps reported by some devices: Fix offset if sensor events are reported more than 10 seconds into the future and generate substitute timestamp if a device reports zero instead of actual timestamps.
- Use new Bluetooth permissions on Android 12, so we can ask permission to scan for nearby devices instead of asking for a location permission which might be confusing to many users.
- Android 12 style splash screen with RWTH branding.
Changes on iOS
- Load saved states on a background process and show the loading progress on screen to avoid watchdog kills in case of many large saved states.
- Fix: MQTT service tries to subscribe to empty topic if "receiveTopic" is not set.
- Fix: Colors of context menu buttons (three dots) in the main menu get mixed up.
- Audio Engine interruption (alarm clock, call, etc.) stops the experiment.
- Audio input now outputs the sample rate as soon as the audio engine is started instead of only when the audio buffer is filled, so the rate is available immediately.
- Fix: Crash if two data sets are plotted in the same graph with a time axis and one time axis data set is empty.
- Fix: Clear in analysis resets to init value instead of emptying a buffer.
- Fix: if-module input clear behavior (did only clear input if output is written).
- Fix: Formula node parsing fails if a two-parameter function is set into brackets.
- Removed the trailing slash from the remote access URL as this seems to confuse Safari.
- Fix: Proximity sensor only works after rotating the device twice. (It still only works in portrait orientation and will turn off the display. This is beyond our control and a limitation of Apples API.)
- Fix: Truncated sensor metadata list in privacy statement of network experiments. (The list actually was correct, but all requested metadata was loaded as referring to the accelerometer.)
File format update to version 1.14
- Support for sensor rate strategies and "stride" (see https://phyphox.org/wiki/index.php/Phyphox_file_format#Input_module:_sensor)
- Number of satellites of location input now reports -1 if unknown.
- New attribute "hideTimeMarkers" for graphs to hide the red time markers.
- New input and view modules for depth sensors
Changes on Android and iOS
- New acoustic countdown for timed run experiments
- Improved countdown for timed run experiments
- Hint bubbles are less blocking
- Fix: Audio Spectrum processes a partially filled audio buffer when pausing the experiment, which leads to a reduced resolution of the Fourier spectrum.
Changes on Android
- Fix: Links not working and missing apps in share menus on Android 11.
- Fix: Missing time markers and crashes on some stricter OpenGL implementations.
- Directly include Eclipse Paho libraries to hopefully fix the F-Droid build process.
Changes on iOS
- Fix: Time markers are not removed if you clear a graph
- Fix: Reduce module produces additional zero value.
- Fix: Wrong conversion of 24 bit integers (affecting both endianesses, signed and unsigned) for BLE inputs. (i.e. when using the pressure sensor of a SensorTag)
- Fix: Localized links in experiment use the URL of the base language (typically English)
File format update to version 1.13
- New "isLink" attribute to define experiment entries that only link to external pages.
Changes on Android and iOS
- Keep track of synchronization points between system time ("wall clock" time), (sensor) event times and experiment time and base all times on a common reference point.¹
- Time axes can be switched between experiment time and system time from the tool menu¹
- Pause events generate gaps in the plot and periods of paused time are marked when a time axis is used¹
- Export includes meta data about the device and recorded time reference events¹
- Time references can be accessed via REST API (remote access)¹
- Fix: Remote access not working for "Audio Oscilloscope" (problem occured on any configuration that has a view element associated with a buffer name that collides with JavaScript object keywords, in this case "length")¹
- Fix: Possible crash in sort module if inputs have different length¹
- Fix: Tone generator hangs after a specific number of periods (Android and possibly 32bit iPhones, i.e. iPhone 5s).²
- Fix: Normalization of amplitude in the resonance view of the pendulum experiment was wrong by a factor of the angular frequency.²
- Fix: Formula node fails to parse scientific notation under specific conditions.
Changes on Android
- Fix possible permission problems for sharing activities.¹
- Fix: Tone generator does not respect duration setting of audio outputs.²
- Hide decimal places in edit fields if only integer inputs are allowed.²
- Fix: Phyphox does not wait for Bluetooth MTU request to complete.
Changes on iOS
- Non-finite values (infinite or NaN) generate a gap in the graph.²
- Non-finite values are not filtered in the rangefilter module (making the Doppler effect experiment consistent with the Android version as invalid results generate gaps)²
- Fix: The be-careful-while-experimenting-dialog disrupts a directly loaded experiment.²
- Fix: App crashes when a different sample rate is forced by the system on the microphone than used for playback.²
- Fix: Crash due to race condition for certain buffer access functions affecting various analysis modules, most notably threshold in Audio Oscilloscope.²
- Fix: The app crashes if starting an audio experiment when no microphone is available.²
- Fix: Implement missing scale strategy "extend".²
- Fix: add/subtract/multiply/divide return an empty buffer if only value inputs are used.
- Fix: Graphs can disappear on screen rotation.
File format update to version 1.12
- New "timeOnX", "timeOnY", "linearTime" and "systemTime" attributes to control the display of time on specific graph axes.¹
- Time references can be sent via network connections using the new "send" type "time".¹
- Events-block to store start/stop events with timestamps.¹
- Timer analysis module has a new output "offset1970" and a new attribute "linearTime".²
¹Part of 1.1.8-beta1, released as public beta on 2020-12-21 ²Part of 1.1.8-beta2, released as public beta on 2021-01-08
Changes on Android and iOS
- External configurations in the main menu can now be shared.¹
- Defunct configurations are listed, so they can be deleted or shared to be analyzed and possibly fixed.¹
- Fix: BLE using indication instead of notification²³
- Fix: Remote access requests only last variable if a value is shown before a graph (notable in the Audio Amplitude graph not working in remote access).³
- Set fixed axis scaling on the Sonar experiment to avoid rescaling on failed measurements.
Changes on Android
- New permissions ACCESS_NETWORK_STATE and WAKE_LOCK required to determine network connection type (see next item) and to use the Paho MQTT library (see file format update)²
- Detect and hide mobile connection IP in listing of addresses for remote access. (Requires at least Android 5.0)²
- Autodetect notifications or indications on BLE connections set to use either.²
- Improve ZIP detection and always create a local copy of remote experiments before loading them.²
- Fix: Crash in audio engine if direct playback source is used with an empty buffer.
- Fix: Port ignored when opening an experiment via URL (including QR codes)²
- Fix: NaN values are rendered as random lines on some devices.²
- Fix: Slight normalization error for Gauss smooth module at the data point with exactly 3*sigma-1 datapoints remaining.³
- Fix: App crashes if an experiment is loaded with undefined XML prefixes. (i.e. an experiment with editor:xxx tags has been modified and the xmlns:editor-definition in the base element was removed.)
Changes on iOS
- Minimum iOS version increased from iOS 8 to iOS 9. (Required by Apple for XCode 12, however, there seem to be no devices that run iOS 8 but could not be updated to iOS 9, so impact should be minimal.)³
- Fix: Cannot save experiment or state after opening from "files".³
- Fix: Cannot save experiment with a slash in its title.³
- Fix: Parsing of last value from BLE inputs with formattedString conversion if there is no terminating separator character.³
File format update to version 1.11
- New network connection services "mqtt/csv" and "mqtt/json"²³
- New conversion for network connections: "csv"²³
¹Part of 1.1.7-beta1, released as public beta on 2020-10-15.
²Part of 1.1.7-beta2, released as public beta on 2020-11-10 (Android only).
³Part of 1.1.7-beta3, released as public beta on 2020-11-25
Changes on Android and iOS
- Audio spectrum now allows generating white noise.¹
- Tone generator supports dual tone generation.¹
- When leaving an experiment that ran for more than 10 seconds, phyphox shows a confirmation dialog.²
- Improved stability of start detection on sonar (especially for iOS).¹
- New "config" endpoint in the REST API (remote access) to allow reading buffer, input and export configuration.¹
- Background slightly darker (the increasing number of apps with dark-mode make our old colors look "washed out").²
- Improved units for slopes (i.e. m/s²/s becomes m/s³ and m/s² / rad/s² becomes m).²
- Fix: Quotation marks in value element mapping break remote access.
Changes on Android
- Direct config transmission via Bluetooth now also accepts plain xml.¹
- Set manifest attribute to allow unencrypted http.²
- Fix broken screenshot for interactive/fullscreen graphs.²
- Fix crash if time output of location input is not used.²
- Fix crash for graph axes with precision 0 or 1 on Samsung S6 due to Java bug https://bugs.java.com/bugdatabase/view_bug.do?bug_id=6469160.²
- Allow using vendor-specific pressure sensor if detected by name.²
- Prevent infinite loop in periodicity analysis module.²
- Fix: Graph forgets zoom state after screen off / app switch / scroll to far tab.²
- Fix: Cannot subscribe to characteristic on Chrome OS.²
- Fix: Edit field does not respond to update from other user inputs.²
- Make static buffers properly unwritable to prevent unexpected behavior by writing from modules with mixed outputs and to allow initializing them from external sources like Bluetooth.²
- Fix crash if finished network request is reported to not visible button.
- Fix crash if models use 2D sensor data.
Changes on iOS
- Prevent duplicate additions to the experiment collection¹
- Share queue among data input of sensors, BLE, GPS and the analysis process to avoid receiving input data during the execution of an analysis seqeuence.¹
- Major changes in analysis cycle logic to be closer to Android version: Analysis is run periodically regardless of sensor input, there is a run before start, "onUserInput" is used as documented, input clear is done before writing the output.²
- Fix: Access error when opening configuration from "files" app.²
- Fix: No output on abs channel for 1D sensors.²
- Fix: Scrollable tab bar on iOS13.²
- Fix: Crash if audio permission is denied.
- Disable refresh rate limit for value view elements for more fluent feedback.
File format update to version 1.10
- Audio output now supports parametric tone and white noise generation.¹
- New analysis modules: interpolate, loess and sort.¹
- New functions in formula node: min, max and heaviside.¹
- New attributes to preset timed run parameters.¹
- New attribute "cycles" for every analysis module, which determines in which runs the module is used.²
- New attribute to send blocks of network connection service "http/post" to switch between JSON arrays and JSON numbers.²
- New response conversion function "none" for network connections, which is now the default.²
- New graph attribute unitYperX to explicitly set a unit for the slope (i.e. y/x).²
- Optimization attribute removed. (This was added very little advantage but a lot of confusion.)²
- Transfer of experiment configurations now supports requesting the transfer from a second characteristic (especially useful if you are using an Arduino library that does not support reacting to subscriptions).
¹Part of 1.1.6-beta1, released as public beta on 2020-05-22.
²Part of 1.1.6-beta2, released as public beta on 2020-07-24.
Changes on Android and iOS
- Spanish translation
- Turkish translation (this has partially been enabled before by accident)
- Spectrum experiments now have a peak frequency history plot.
- The apply-zoom dialog when leaving a graph now defaults to "reset", but remembers if you want to keep the zoom for the next time.
- Fix: Remote interface breaks if NaN / null values are to be plotted. (Typically in frequency history or Doppler effect experiments)
Changes on Android
- Fix for Bluetooth Experiments failing to load if using specific conversion functions on many Android devices.
- Fix Bluetooth input conversion "formattedString" failing when using indices without explicitly specifying empty labels.
- Fix: GPS experiments crash on phone that do not offer a network-based location service.
- Fix black background of graph toolbar on some devices (i.e. Pixel 3).
Changes on iOS
- Fix unresponsive Bluetooth scan result dialog
- Fix for Bluetooth: Pick write with/without response depending on peripheral's capabilities
- Fix Bluetooth input conversion "formattedString" failing when using labels (this is different than the similar Android fix)
- Fix for crash when sending an empty /control or /export request to the remote access webserver
File format update to version 1.9
- New Bluetooth device atttribute "mtu" to request a specific MTU size
- Support for new sensor type "attitude"
Hotfix for iOS only. Menus were unreadyble in iOS 13 with dark mode.
Changes on Android and iOS
- New network interface allowing to send and/or receive data to/from network services.
- New sensor db experiment, that allows you to contribute information about your device to our new (upcoming) sensor database.
- Highlight nearest BLE devices if multiple with same name are present.
- Use common time reference for multiple sensors, improving their synchronization.
- Location services (i.e. GPS) now use a database to translate elevation above the reference geoid and the WGS84 ellipsoid directly in phyphox and giving both values. This also fixes getting ellipsoid instead of geoid data on Android 10 devices.
Changes on Android
- Notify user if location service is not enabled when trying to scan for BLE devices.
- Fix attribute clash of phyphox and the web editor.
- Fix remote access problem on Android 4 devices.
- Improve title display for long titles
- Code maintenance under the hood (thanks to "TacoTheDank")
Changes on iOS
- Fix wrong values if picking data points from logarithmic plots
- Fix applause meter losing scores
- Use advertised name of BLE devices instead of the local name buffered by iOS
- Update BLE scan results, so changes in signal strength can be seen
- Fix analysis logic: Run analysis if input data has been changed by previous analysis run
- Fix some analysis crashes due to invalid integers
- Include EduRoom SDK (eduroom.de)
- Accept old "out" attribute for audio inputs to fix compatibility issues with older experiments
File format update to version 1.8
- Elements to define network interface
- autoConnect function to allow connection to BLE devices without scanning
- New formatting options for info elements: bold, italic, align and size
- New option to ignore sensor availability
Changes on Android and iOS
- Serbian translation (in Latin script)
- Remote access stores settings (font size, layout) until the end of the browser session
- Remote access now has a bright mode (should help on low-contrast projectors)
- Fix error in distance calculation of location/GPS experiment. (Introduced in 1.1.0, please check any distance data generated in 1.1.0 or 1.1.1)
- Add 1/min to acceleration spectrum and magnetic spectrum to directly get RPM from engines
Changes on Android
- Save scroll position of experiment list after entering an experiment or adding/removing items
Changes on iOS
- Add gap between value and unit in value view elements to avoid confusing units
- Show optional dialogs and hints (save experiment locally, press arrow to start, etc.) after showing the Bluetooth scan dialog instead of not showing them at all
- Fix separators in experiment layouts
Changes on Android
- Offer additional apps when exporting (using a view-intent in addition to the share-intent)
- Fix crash in data picker
Changes on iOS
- Fix: Elevator experiment not working due to an error in the new formula parser
- Fix: Crash of color plot (mostly when starting the sonar experiment)
- Fix: Color map not showing if any z value is infinite (encountered in magnetic spectrum)
- Fix: Crash when picking data points in graph with history (i.e. in the sonar experiment)
- Fix: Crash in reduce module for fewer y than x data points
- Fixes for iOS 13: Crash when opening experiments and design of tab bar
Changes on Android and iOS
- Phyphox is licenced under the GNU General Public Licence from this version onwards
- Bluetooth Low Energy support
- Bluetooth Experiments included: Generic heart rate sensor, generic HID mouse, PocketLab One, PocketLab Voyager, Sensirion Smart Humigadget, Texas Instruments SensorTag CC1350/CC2650
- Interactive graphs (zooming, picking points, linear fit)
- New experiment: Applause meter
- Multi-line plots
- Bar charts
- Color plots (used in spectrum experiments)
- Open experiments from zip files or QR codes
- Raw sensor experiments now feature a multi-line version
- New languages: Chinese (simplified script), French, Vietnamese
- Acoustic stopwatch has a new "many" tab , which allows measuring of an unlimited number of events, giving each interval and calculating the rate (Hz or bpm) and average interval of all events
- Improvements to make the sonar more reliable
- Performance optimizations for several experiments
- Distance from start info for GPS-Experiment
- Inclination experiment now features several different reference systems
- Removed the libraries jquery and flot from the remote interface, which now uses chart.js instead
- Remote interface now starts with a font-size recommended by the browser and allows changing the font size
- Picking data points in the remote interface
- The remote interface allows to show a single graph filling the full screen
- Remote interface now communicates through a queue to avoid missed requests by the single-threaded webserver on the phone
- Introduced a default color palette, which is used for coloring multiple graphs and can be referenced to by using names (red, blue, etc.) instead of RGB-values
- Experiment configurations can be loaded directly from BLE devices
- New device info report from menu on main screen
- Add color to special categories (saved states and simple custom experiments)
- Allow external experiments to define icon and category colors
- Allow renaming of saved states
- Use experiment title as default file name when exporting data, saved states or screenshots
- Show state title in experiment info
- Add hint to start button and add logic to hint bubbles, so they only show up until the user has used the specific function a few times
- Fix: Wrong scaling of data in Doppler experiment due to outlying points
- Fix: Consider available precision in remote interface to avoid retrieving the same value multiple times
- Improve magnetic ruler for longer measurements
- Fix inelastic collision experiment only working after pressing "reset"
- Disable export and explain it to the user if an experiment configuration does not define an export
Changes on Android
- Fix calculation of GPS height above geoid (MSL) if non-GPS satellite systems (GLONASs) are used
- Vertical accuracy in GPS data if supported by some Android 8+ devices
- Support temperature and humidity sensors
- Support vendor-specific sensors by guessing their function by name
- Improved performance by using native code for some operations
- Improved Fourier transform performance by using the FFTW library
- Allow screen rotation during measurement (now consistent with iOS)
- Prevent adding identical experiments multiple times
- Add notice when no address for the remote access is available
- GPS now also uses network data by default and offers to force GPS only in the menu
- Fix: Crash on malformed icon data
- Fix: Sort categories case-insensitive
- Fix loading experiments from URLs without query strings
- Fix: Result response from webserver used broken JSON format.
- Limit state title length
Changes on iOS
- Complete rewrite of experiment parser. Much faster and much more stable when loading external experiments with errors.
- Buffer rewritten. This should fix previous crashes in long-term measurements due to a race condition when accessing the buffers.
- Respect save area guides to avoid drawing the UI in areas used by system buttons or the notch (iPhone X and similar)
- Fix: Missing parts of a translation fall back to English defaults
- Fix: Pick experiment language according to app language and avoid using unreleased languages already present in the experiment definition files
- Fix: Re-saving states crashes the app
- Fix: Power function fails for negative exponents
File format update to version 1.7
- New graph types and multiple graphs
- New Bluetooth Low Energy definitions
- New "formula" analysis module
- New "reduce" analysis module
- New "map" analysis module
- New attribute to enable analysis optimization (only re-run modules if their inputs have changed)
- Label and unit can (and should) be separated for graphs to allow giving the right unit when reading a single data point
- Colors can be names instead of RGB hex values
- Value and info elements may now be colored
- Temperature and humidity sensor types
Changes on Android and iOS
- Japanese translation
Changes on Android
- Fix: Light experiment not accessible if the list of preferred languages (Android settings) does not contain any language directly supported by phyphox.
Hotfix for iOS only. Unfinished translations were used as they were present in experiment files for testing, but should not have been selected by phyphox.
Changes on Android and iOS
- Portuguese translation
Changes on iOS
- Fix flickering of audio oscilloscope
Changes on Android and iOS
- Italian translation.
- Greek translation.
Changes on iOS
- Experiment "Roll" deactivated by Apple's request.
Changes on Android and iOS
- Dutch translation.
- Russian translation.
- Inelastic collision experiment hides invalid intervals.
- Translations are now also applied to units.
Changes on Android
- Fix lines connecting to first point when loading a previously saved state.
Changes on iOS
- Fix crash when value element has empty map tag.
Changes on Android and iOS
- Czech translation.
- Polish translation.
- Introduced a new "language" entry to the info menu on the main screen.
- Fix: Flickering in motion stopwatch.
Changes on Android
- Update to file format 1.6 and support audio sample rate output. (Which has been introduced as a hotfix to iOS previously.)
Hotfix for iOS only. The previous update introduced a problem when the system defaults to a rate of 44.1kHz. With the fix file format version 1.6 was introduced (partially) to support reading the actual sample rate. The full introduction of format 1.6 happened with version 1.0.11 for both platforms.
Changes on Android and iOS
- Location (GPS) experiment now calculates the distance travelled.
- Pendulum experiment shows a genreic results page first.
- Minor optimizations of remote access communication.
- Minor optimizations of text in experiments.
- Fix: Inclination experiment now resumes at correct timestamp.
- Fix: Jittery axis in roll experiment.
Changes on Android
- Allow installation on external storage.
- Added some MIME types to allow opening phyphox files from more third-party apps.
- Correct GPS height from WGS84 ellipsoid to geoid if possible.
- Adaptive Icons for Android 8.0.
- Fix: Order of external links now matches definition in custom experiments.
- Fix: Rotation lock ignored in main menu.
Changes on iOS
- Wider text fields.
- Icon-Positioning in tool bar no longer optimized by the app as this lead to problems on some iOS 11 versions.
- Remove subject text when sharing data or screenshots as this generates multiple files in iOS and leads to more trouble than it's worth.
- Fix: Crash when using the remote access in hotspot mode.
- Fix: Crash when saving a saved state a second time.
- Fix: Crash when activating remote access while port 80 is already in use.
- Fix: Crash when the system does not support an audio rate of 48 kHz (for example when using AirPlay).
- Fix: Crash when external link has not been translated in custom experiment.
- Fix: Highlighted link not visible if not translated.
- Fix: Some sensors do not produce data on iPods (fix not tested).
Changes for both Android and iOS
- Fix wrong time axis of audio scope.
- Allow unusual frequencies in tone generator but add a warning.
- Rename centrifugal acceleration to centripetal.
Changes for Android
- Fix OK-button not accessible on startup (small screens with enlarged fonts)
- Fix rare crash in GPS module
- Combine wrong GPS status to "deactivated/active"
Changes for iOS
- Fix flickering of audio scope.
- Fix crash on audio playback, mostly on iOS11.
Changes for both Android and iOS
- Save or share and load experiment states including your recorded data – even across platforms.
- GPS support.
- Audio autocorrelation and spectrum show corresponding musical notes.
- You can now pick between different number of samples in audio spectrum.
- New experiments: Accelerometer and magnetometer spectrum.
- Time period of audio scope is now selectable.
- Improved algorithm for audio autocorrelation.
- Audio amplitude can now be calibrated to give sound pressure level in dB.
- Splash screen with university logo.
- Show magnetometer accuracy.
- Move clear function to the action bar as a button.
- Minor improvements to TalkBack / VoiceOver by adding descriptions to unlabeled buttons.
- Buffer for acoustic stopwatch and inelastic collision has been increased, which might help on slower phones.
Changes for Android
- Fix crash on Android 7.1 and Android O when reading non-3D sensors (like pressure or light).
- Fix crash when rotating while the description hint starts showing.
- Fix crash on bad experiment icons in main menu.
Changes for iOS
- Fix crash on consecutive Fourier transforms.
- Code has been converted to Swift 3. Ideally, there should be no noticable change. Ideally.
- Old, discontinued audio engine has been replaced.
- Fix: VoiceOver stopped working when phyphox handled audio.
- University logo added to credits dialog.
File format update to version 1.5
- Allow initializing buffers using a list of values.
- Add mapping of ranges to value element to show text instead of numbers.
- Add accuracy channel to sensors (magnetometer only).
- Allow for dynamic sleep times of analysis cycles.
- New analysis modules: round and log.
- Fix handling of start value in subrange module.
- Fix on Android: FFT module now uses actual number of data points instead of just the buffer size.
- Fix on iOS: Button elements could not use buffers as inputs.
Changes for both Android and iOS
- New experiment: Inelastic collision.
- New timer experiments: Motion stopwatch, proximity stopwatch and optical stopwatch. The existing acoustic stopwatch has been moved to this section.
- Support for the proximity sensor.
- Raw sensor experiments now also give the absolute value of 3D data.
- The info button at the top now opens a small menu with links to our FAQ, help and experiment collection.
- Added resonance page to the experiments "spring" and "pendulum".
- The "pendulum" experiment now has a page, which allows estimating the length of the string.
- Added a third view to the "sonar", plotting the correlation against the raw time axis.
- Performance improvements for "sonar" and "acoustic stopwatch" for slower devices.
- The "elevator" experiment now also shows the acceleration using the accelerometer.
- The remote interface starts in a new "narrow" layout, similar to a phone screen. You can still switch to the old full-screen layouts via the menu of the remote interface.
- The rate limit for the raw data experiments has been removed, so they acquire data at the maximum rate allowed by your device.
- Fix: Graph scaling not applied on remote interface.
Changes for Android
- We now read the recording from the mic in smaller chunks to improve the timing of the analysis cycle.
- Default margins removed from all view elements as these are now controlled by the new separator view module. (See file format changes below.)
- Name the sensor which is not available when trying to open an experiment.
- Fix: Crashes when experiments use string icons with less than three character.
- Fix: Rare crash when showing hint tooltip.
- Fix: Do not show save-locally dialog if the experiment was not loaded successfully. Trying to save in such cases led to a crash.
- Fix: The optimization for the analysis assumes it can skip empty buffers as there is no data to be processed, resulting in problems, when a buffer is empty because it has been cleared intentionally. Instead we now keep track if a buffer has been touched.
- Fix: When averaging, the first sensor value is returned immediately without averaging.
- Fix: The edit box in the experiment "Magnetic ruler" resets to the default value.
- Fix: Repeatable inputs were not mapped correctly if they were not used in the first period of repeatable inputs. This affected the rangefilter in a way, that it would not behave correctly if the second input should be filtered, but not the first one.
Changes for iOS
- Audio recordings are buffered internally and only exposed to the analysis buffers just before an analysis cycle starts. This way, it is guaranteed, that the buffer will not be changed during the analysis process and you do not need to create a local copy. This makes it consistent with the behavior of the Android version.
- Display a hyphen instead of "NaN".
- Added a default text when sharing a screenshot. This hopefully prevents some third-party apps from inserting the image file path as default text.
- Fix: Range filter does not work correctly in cases in which the first value of the second input is filtered.
- Fix: Remote access stops working after leaving the app and returning to the existing session.
File format update to version 1.4
- New absolute output for all sensors, so you do not have to calculate it yourself in your analysis.
- New separator view element. This allows to add margins or lines to group your views.
- New analysis module: subrange. This simply returns the values within an index range. Much faster than using the rangefilter for this task.
- The analysis modules "if" and "append" as well as the view "button" now allow a new input type. Besides "value" and "buffer", you may now set them to "empty", practically being a constant buffer of length zero.
- Slightly change behavior for "if" module: If the output is flagged to be cleared before writing, this is only done if the condition for an input has been met. This means, that the output is not cleared if there was no input for a certain case and you can conditionally clear an output by assigning an input of type "empty" to a case.
Changes for both Android and iOS
- We now use the calibrated magnetometer by default and allow switching to the raw magnetometer from the menu if available on the device.
- Added an explanation link to the sensor-not-available notification.
- Acoustic stopwatch now supports multiple timers and allows for setting a minimum delay.
- Sonar now features a reverse mode where you enter a distance and can determine the speed of sound.
- Fix: Append-module now accepts value-type input.
- Fix: Update fails when switching to raw data in remote experiment of the roll experiment (and possibly others).
- Fix: Some spelling errors in the experiments.
Changes for Android
- Fix: Very short audio loops failed.
- Fix: Remote access failed when infinite numbers occur.
- Fix: Crash on Samsung Galaxy S4 when repeatedly playing audio.
Changes for iOS
- Fix: Run analysis even when not triggered by a sensor event to allow for self-modifying experiments like a gradually changing tone generator.
- Fix: Possible crash in average module (race condition mostly triggered on iOS8).
- Fix: Axis labels were not translated in the remote interface.
- Fix: Crash in binning module when dx is set to zero.
- Fix: Handle audio setup changes (plugging in a headset) more gracefully.
Main Changes
- New experiment: Acoustic stopwatch
- More options when exporting in CSV format: There now are variants with a comma as decimal point and the number format is now consistent across both platforms.
- Grey out experiments that are unavailable
- Add video links to the experiment menu as well (or any link marked as highlight)
Changes to the phyphox file format
- New analysis module: if
- New view element: button
- New initializing attribute for buffers
Fixes for Android
- Improved behavior when hiding keyboard
- Fix possible crash when switching to different app
- Update views in stopped state
- Fix auto-orientation not respecting system setting
- Fix opening phyphox:// URLs with parameters
- Fix for the (half-official) Bluetooth support. Note, that this will changed and replaced by Bluetooth 4.0 / BLE in the future.
- Apply size setting of value view element to the remote interface.
Fixes for iOS
- Fix magnetometer calibration factor. (Note: We are using the uncalibrated magnetometer values, which may be way off from what you expect for small fields like the earth's magnetic field, but which should be good for stronger field. However, we might switch to the calibrated one in the future to avoid confusion, but which might introduce other problems.)
- Fix for not stripping trailing zeros if a fixed number of digits is defined for a value view element
- New experiments: Centrifugal force and inclination
- Simple view for raw sensors, just giving numbers
- Improved descriptions and labels for several experiments
- Better time axis calculation in elevator experiment
- Updated experiment file format to 1.2: New modules for statistics and trigonometry. Also more control over value and graph view elements.
Fixes on iOS
- Disappearing view elements after rotation or scrolling
- Crash when starting web interface on iOS8
- Crash when entering zeros in Doppler effect
- Crash in autocorrelation module (experiments "Spring", "Pendulum" and "Autocorrelation")
- Missing data points in remote interface (mostly elevator and roll)
- Could not open external experiments on iOS8
- Strip white-spaces from description
Fixes on Android
- Fix wrong play-button animation after screen being turned off
- Do not show the save-locally-dialog again after rotation
- Show "-" instead of "NaN" when no data is available
- Improved reliability of remote interface when doing partial data updates
- Fix possible crash when switching apps while graph is visible
- Fix crash when closing experiment without dismissing the info-tooltip
- Hint to guide inexperienced users to the experiment info.
- Ask if externally loaded experiment should be added to collection. (You can still do so later via the menu as before.)
- Disable back swipe gesture to avoid involuntarily closing an experiment when swiping between tabs. (iOS only)
- Limit min/max of allowed values in some experiments (phyphox file format has been updated for this)
- Values entered in experiments are now only used for calculations after the user confirms the input (hitting the confirmation button on the virtual keyboard) or changes the focus away from the edit box. This behaviour now matches the one from the iOS version and prevents unnecessary recalculations while entering numbers. (Android only)
- Fix decimal values not being allowed. (iOS only)
- Fix problematic recalculation when clearing buffer. (iOS only)
- Handle flawed phyphox files more gracefully and report errors. This will be improved further in future updates. (iOS only)
Minor changes
- Added now mandatory explanation when requesting permission to access the microphone.
- Internal code changes required for iOS 10 targets. These changes should not be visible, but since some libraries have been updated, there may still be some changes, that we did not anticipate.
- Fix crashes on iPad when trying to export data or sharing a screenshot.
- Fix rare crash in experiment most likely to occur when switching apps or displaying a dialog.
- Fix remote interface being unable to reconnect after switching to a different experiment.
Initial release


text:
BC(1) NetBSD General Commands Manual BC(1)Powered by man-cgi (2021-06-01). Maintained for NetBSD by Kimmo Suominen. Based on man-cgi by Panagiotis Christias.
bc -- arbitrary precision calculator language
bc [-hilqsvw] [long-options] [file ...]
bc is a language that supports arbitrary precision numbers with interac- tive execution of statements. There are some similarities in the syntax to the C programming language. A standard math library is available by command line option. If requested, the math library is defined before processing any files. bc starts by processing code from all the files listed on the command line in the order listed. After all files have been processed, bc reads from the standard input. All code is executed as it is read. (If a file contains a command to halt the processor, bc will never read from the standard input.) This version of bc contains several extensions beyond traditional bc implementations and the POSIX draft standard. Command line options can cause these extensions to print a warning or to be rejected. This docu- ment describes the language accepted by this processor. Extensions will be identified as such. OPTIONS -h, --help Print the usage and exit. -i, --interactive Force interactive mode. -l, --mathlib Define the standard math library. -q, --quiet Quiet mode. -s, --standard Process exactly the POSIX bc language. -v, --version Print the version number and copyright and quit. -w, --warn Give warnings for extensions to POSIX bc. NUMBERS The most basic element in bc is the number. Numbers are arbitrary preci- sion numbers. This precision is both in the integer part and the frac- tional part. All numbers are represented internally in decimal and all computation is done in decimal. (This version of bc truncates results from divide and multiply operations.) There are two attributes of num- bers, the length and the scale. The length is the total number of sig- nificant decimal digits in a number and the scale is the total number of decimal digits after the decimal point. For example: .000001 has a length of 6 and scale of 6. 1935.000 has a length of 7 and a scale of 3. VARIABLES Numbers are stored in two types of variables, simple variables and arrays. Both simple variables and array variables are named. Names begin with a letter followed by any number of letters, digits and under- scores. All letters must be lower case. (Full alpha-numeric names are an extension. In POSIX bc all names are a single lower case letter.) The type of variable is clear by the context because all array variable names will be followed by brackets ([]). There are four special variables, scale, ibase, obase, and last. scale defines how some operations use digits after the decimal point. The default value of scale is 0. ibase and obase define the conversion base for input and output numbers. The default for both input and output is base 10. last (an extension) is a variable that has the value of the last printed number. These will be discussed in further detail where appropriate. All of these variables may have values assigned to them as well as used in expressions. COMMENTS Comments in bc start with the characters ``/*'' and end with the charac- ters ``*/''. Comments may start anywhere and appear as a single space in the input. (This causes comments to delimit other input items. For example, a comment can not be found in the middle of a variable name.) Comments include any newlines (end of line) between the start and the end of the comment. To support the use of scripts for bc, a single line comment has been added as an extension. A single line comment starts at a ``#'' character and continues to the next end of the line. The end of line character is not part of the comment and is processed normally. EXPRESSIONS The numbers are manipulated by expressions and statements. Since the language was designed to be interactive, statements and expressions are executed as soon as possible. There is no ``main'' program. Instead, code is executed as it is encountered. (Functions, discussed in detail later, are defined when encountered.) A simple expression is just a constant. bc converts constants into internal decimal numbers using the current input base, specified by the variable ibase. (There is an exception in functions.) The legal values of ibase are 2 through 36. (Base values greater than 16 are an exten- sion.) Assigning a value outside this range to ibase will result in a value of 2 or 36. Input numbers may contain the characters 0-9 and A-Z. (Note: They must be capitals. Lower case letters are variable names.) Single digit numbers always have the value of the digit regardless of the value of ibase. (i.e. A = 10.) For multi-digit numbers, bc changes all input digits greater or equal to ibase to the value of ibase - 1. This makes the number ``ZZZ'' always be the largest 3 digit number of the input base. Full expressions are similar to many other high level languages. Since there is only one kind of number, there are no rules for mixing types. Instead, there are rules on the scale of expressions. Every expression has a scale. This is derived from the scale of original numbers, the operation performed and in many cases, the value of the variable scale. Legal values of the variable scale are 0 to the maximum number repre- sentable by a C integer. In the following descriptions of legal expressions, ``expr'' refers to a complete expression and ``var'' refers to a simple or an array variable. A simple variable is just a name and an array variable is specified as name[expr]. Unless specifically mentioned the scale of the result is the maximum scale of the expressions involved. - expr The result is the negation of the expression. ++ var The variable is incremented by one and the new value is the result of the expression. -- var The variable is decremented by one and the new value is the result of the expression. var ++ The result of the expression is the value of the vari- able and then the variable is incremented by one. var -- The result of the expression is the value of the vari- able and then the variable is decremented by one. expr + expr The result of the expression is the sum of the two expressions. expr - expr The result of the expression is the difference of the two expressions. expr * expr The result of the expression is the product of the two expressions. expr / expr The result of the expression is the quotient of the two expressions. The scale of the result is the value of the variable scale. expr % expr The result of the expression is the remainder and it is computed in the following way: To compute a%b, first a/b is computed to scale digits. That result is used to compute a-(a/b)*b to the scale of the maximum of scale + scale(b) and scale(a). If scale is set to zero and both expressions are integers this expression is the integer remainder function. expr ^ expr The result of the expression is the value of the first raised to the second. The second expression must be an integer. (If the second expression is not an integer, a warning is generated and the expression is truncated to get an integer value.) The scale of the result is scale if the exponent is negative. If the exponent is posi- tive, the scale of the result is the minimum of the scale of the first expression times the value of the exponent and the maximum of scale and the scale of the first expression. (e.g. scale(a^b) = min(scale(a)*b, max( scale, scale(a))).) It should be noted that expr^0 will always return the value of 1. ( expr ) This alters the standard precedence to force the evalua- tion of the expression. var = expr The variable is assigned the value of the expression. var <op>= expr This is equivalent to var = var <op> expr with the exception that the ``var'' part is evaluated only once. This can make a difference if ``var'' is an array. Relational expressions are a special kind of expression that always eval- uate to 0 or 1, 0 if the relation is false and 1 if the relation is true. These may appear in any legal expression. (POSIX bc requires that rela- tional expressions are used only in if, while, and for statements and that only one relational test may be done in them.) The relational oper- ators are: expr1 < expr2 The result is 1 if expr1 is strictly less than expr2. expr1 <= expr2 The result is 1 if expr1 is less than or equal to expr2. expr1 > expr2 The result is 1 if expr1 is strictly greater than expr2. expr1 >= expr2 The result is 1 if expr1 is greater than or equal to expr2. expr1 == expr2 The result is 1 if expr1 is equal to expr2. expr1 != expr2 The result is 1 if expr1 is not equal to expr2. Boolean operations are also legal. (POSIX bc does NOT have boolean oper- ations.) The result of all boolean operations are 0 and 1 (for false and true) as in relational expressions. The boolean operators are: !expr The result is 1 if expr is 0. expr && expr The result is 1 if both expressions are non-zero. expr || expr The result is 1 if either expression is non-zero. The expression precedence is as follows: (lowest to highest) 1. || operator, left associative 2. && operator, left associative 3. ! operator, nonassociative 4. Relational operators, left associative 5. Assignment operator, right associative 6. + and - operators, left associative 7. *, / and % operators, left associative 8. ^ operator, right associative 9. unary - operator, nonassociative 10. ++ and -- operators, nonassociative This precedence was chosen so that POSIX compliant bc programs will run correctly. This will cause the use of the relational and logical opera- tors to have some unusual behavior when used with assignment expressions. Consider the expression: a = 3 < 5 Most C programmers would assume this would assign the result of ``3 < 5'' (the value 1) to the variable ``a''. What this does in bc is assign the value 3 to the variable ``a'' and then compare 3 to 5. It is best to use parenthesis when using relational and logical operators with the assign- ment operators. There are a few more special expressions that are provided in bc. These have to do with user defined functions and standard functions. They all appear as ``name (parameters)''. See the section on functions for user defined functions. The standard functions are: length (expression) The value of the length function is the number of significant digits in the expression. read () The read function (an extension) will read a number from the standard input, regardless of where the function occurs. Beware, this can cause problems with the mixing of data and program in the standard input. The best use for this function is in a pre- viously written program that needs input from the user, but never allows program code to be input from the user. The value of the read function is the number read from the standard input using the current value of the variable ibase for the conver- sion base. scale (expression) The value of the scale function is the number of digits after the decimal point in the expression. sqrt (expression) The value of the sqrt function is the square root of the expression. If the expression is negative, a run time error is generated. STATEMENTS Statements (as in most algebraic languages) provide the sequencing of expression evaluation. In bc statements are executed ``as soon as possible''. Execution happens when a newline in encountered and there is one or more complete statements. Due to this immediate execution, new- lines are very important in bc. In fact, both a semicolon and a newline are used as statement separators. An improperly placed newline will cause a syntax error. Because newlines are statement separators, it is possible to hide a newline by using the backslash character. The sequence ``\<nl>'', where <nl> is the newline appears to bc as whitespace instead of a newline. A statement list is a series of statements sepa- rated by semicolons and newlines. The following is a list of bc state- ments and what they do: (Things enclosed in brackets ([]) are optional parts of the statement.) expression This statement does one of two things. If the expres- sion starts with <variable> <assignment> ..., it is con- sidered to be an assignment statement. If the expres- sion is not an assignment statement, the expression is evaluated and printed to the output. After the number is printed, a newline is printed. For example, ``a=1'' is an assignment statement and ``(a=1)'' is an expres- sion that has an embedded assignment. All numbers that are printed are printed in the base specified by the variable obase. The legal values for obase are 2 through BC_BASE_MAX. (See the section LIMITS.) For bases 2 through 16, the usual method of writing numbers is used. For bases greater than 16, bc uses a multi- character digit method of printing the numbers where each higher base digit is printed as a base 10 number. The multi-character digits are separated by spaces. Each digit contains the number of characters required to represent the base ten value of ``obase-1''. Since num- bers are of arbitrary precision, some numbers may not be printable on a single output line. These long numbers will be split across lines using the ``\'' as the last character on a line. The maximum number of characters printed per line is 70. Due to the interactive nature of bc, printing a number causes the side effect of assigning the printed value to the special variable last. This allows the user to recover the last value printed without having to retype the expression that printed the number. Assigning to last is legal and will overwrite the last printed value with the assigned value. The newly assigned value will remain until the next number is printed or another value is assigned to last. (Some installations may allow the use of a single period (.) which is not part of a number as a short hand notation for last.) string The string is printed to the output. Strings start with a double quote character and contain all characters until the next double quote character. All characters are take literally, including any newline. No newline character is printed after the string. print list The print statement (an extension) provides another method of output. The list is a list of strings and expressions separated by commas. Each string or expres- sion is printed in the order of the list. No terminat- ing newline is printed. Expressions are evaluated and their value is printed and assigned to the variable last. Strings in the print statement are printed to the output and may contain special characters. Special characters start with the backslash character (\). The special characters recognized by bc are `a' (alert or bell), `b' (backspace), `f' (form feed), `n' (newline), `r' (carriage return), `q' (double quote), `t' (tab), and `\' (backslash). Any other character following the backslash will be ignored. { statement_list } This is the compound statement. It allows multiple statements to be grouped together for execution. if (expression) statement1 [else statement2] The if statement evaluates the expression and executes statement1 or statement2 depending on the value of the expression. If the expression is non-zero, statement1 is executed. If statement2 is present and the value of the expression is 0, then statement2 is executed. (The else clause is an extension.) while (expression) statement The while statement will execute the statement while the expression is non-zero. It evaluates the expression before each execution of the statement. Termination of the loop is caused by a zero expression value or the execution of a break statement. for ([expression1]; [expression2]; [expression3]) statement The for statement controls repeated execution of the statement. Expression1 is evaluated before the loop. Expression2 is evaluated before each execution of the statement. If it is non-zero, the statement is evalu- ated. If it is zero, the loop is terminated. After each execution of the statement, expression3 is evalu- ated before the reevaluation of expression2. If expression1 or expression3 are missing, nothing is eval- uated at the point they would be evaluated. If expression2 is missing, it is the same as substituting the value 1 for expression2. (The optional expressions are an extension. POSIX bc requires all three expres- sions.) The following is equivalent code for the for statement: expression1; while (expression2) { statement; expression3; } break This statement causes a forced exit of the most recent enclosing while statement or for statement. continue The continue statement (an extension) causes the most recent enclosing for statement to start the next itera- tion. halt The halt statement (an extension) is an executed state- ment that causes the bc processor to quit only when it is executed. For example, if (0 == 1) halt will not cause bc to terminate because the halt is not executed. return Return the value 0 from a function. (See the section on functions.) return (expression) Return the value of the expression from a function. (See the section on functions.) As an extension, the parenthesis are not required. PSEUDO STATEMENTS These statements are not statements in the traditional sense. They are not executed statements. Their function is performed at "compile" time. limits Print the local limits enforced by the local version of bc This is an extension. quit When the quit statement is read, the bc processor is terminated, regardless of where the quit statement is found. For example, if (0 == 1) quit will cause bc to terminate. warranty Print a longer warranty notice. This is an extension. FUNCTIONS Functions provide a method of defining a computation that can be executed later. Functions in bc always compute a value and return it to the caller. Function definitions are "dynamic" in the sense that a function is undefined until a definition is encountered in the input. That defi- nition is then used until another definition function for the same name is encountered. The new definition then replaces the older definition. A function is defined as follows: define name ( parameters ) { newline auto_list statement_list } A function call is just an expression of the form ``name (parameters)''. Parameters are numbers or arrays (an extension). In the function defini- tion, zero or more parameters are defined by listing their names sepa- rated by commas. All parameters are call by value parameters. Arrays are specified in the parameter definition by the notation ``name []''. In the function call, actual parameters are full expressions for number parameters. The same notation is used for passing arrays as for defining array parameters. The named array is passed by value to the function. Since function definitions are dynamic, parameter numbers and types are checked when a function is called. Any mismatch in number or types of parameters will cause a runtime error. A runtime error will also occur for the call to an undefined function. The auto_list is an optional list of variables that are for "local" use. The syntax of the auto list (if present) is ``auto name, ...;''. (The semicolon is optional.) Each name is the name of an auto variable. Arrays may be specified by using the same notation as used in parameters. These variables have their values pushed onto a stack at the start of the function. The variables are then initialized to zero and used throughout the execution of the function. At function exit, these variables are popped so that the original value (at the time of the function call) of these variables are restored. The parameters are really auto variables that are initialized to a value provided in the function call. Auto variables are different than traditional local variables because if func- tion A calls function B, B may access function A's auto variables by just using the same name, unless function B has called them auto variables. Due to the fact that auto variables and parameters are pushed onto a stack, bc supports recursive functions. The function body is a list of bc statements. Again, statements are sep- arated by semicolons or newlines. Return statements cause the termina- tion of a function and the return of a value. There are two versions of the return statement. The first form, ``return'', returns the value 0 to the calling expression. The second form, ``return (expression)'', com- putes the value of the expression and returns that value to the calling expression. There is an implied ``return (0)'' at the end of every func- tion. This allows a function to terminate and return 0 without an explicit return statement. Functions also change the usage of the variable ibase. All constants in the function body will be converted using the value of ibase at the time of the function call. Changes of ibase will be ignored during the execu- tion of the function except for the standard function read, which will always use the current value of ibase for conversion of numbers. Several extensions have been added to functions. First, the format of the definition has been slightly relaxed. The standard requires the opening brace be on the same line as the define keyword and all other parts must be on following lines. This version of bc will allow any num- ber of newlines before and after the opening brace of the function. For example, the following definitions are legal. define d (n) { return (2*n); } define d (n) { return (2*n); } Functions may be defined as void. A void funtion returns no value and thus may not be used in any place that needs a value. A void function does not produce any output when called by itself on an input line. The key word void is placed between the key word define and the function name. For example, consider the following session. define py (y) { print "--->", y, "<---", "0; } define void px (x) { print "--->", x, "<---", "0; } py(1) --->1<--- 0 px(1) --->1<--- Since py is not a void function, the call of py (1) prints the desired output and then prints a second line that is the value of the function. Since the value of a function that is not given an explicit return state- ment is zero, the zero is printed. For px (1), no zero is printed because the function is a void function. Also, call by variable for arrays was added. To declare a call by vari- able array, the declaration of the array parameter in the function defi- nition looks like ``name []''. The call to the function remains the same as call by value arrays. MATH LIBRARY If bc is invoked with the -l option, a math library is preloaded and the default scale is set to 20. The math functions will calculate their results to the scale set at the time of their call. The math library defines the following functions: s (x) The sine of x, x is in radians. c (x) The cosine of x, x is in radians. a (x) The arctangent of x, arctangent returns radians. l (x) The natural logarithm of x. e (x) The exponential function of raising e to the value x. j (n, x) The Bessel function of integer order n of x.
The following environment variables are processed by bc: POSIXLY_CORRECT This is the same as the -s option. BC_ENV_ARGS This is another mechanism to get arguments to bc. The format is the same as the command line arguments. These arguments are processed first, so any files listed in the environment arguments are processed before any com- mand line argument files. This allows the user to set up "standard" options and files to be processed at every invocation of bc. The files in the environment vari- ables would typically contain function definitions for functions the user wants defined every time bc is run. BC_LINE_LENGTH This should be an integer specifying the number of char- acters in an output line for numbers. This includes the backslash and newline characters for long numbers.
In /bin/sh, the following will assign the value of pi to the shell vari- able pi. pi=$(echo "scale=10; 4*a(1)" | bc -l) The following is the definition of the exponential function used in the math library. This function is written in POSIX bc. scale = 20 /* Uses the fact that e^x = (e^(x/2))^2 When x is small enough, we use the series: e^x = 1 + x + x^2/2! + x^3/3! + ... */ define e(x) { auto a, d, e, f, i, m, v, z /* Check the sign of x. */ if (x<0) { m = 1 x = -x } /* Precondition x. */ z = scale; scale = 4 + z + .44*x; while (x > 1) { f += 1; x /= 2; } /* Initialize the variables. */ v = 1+x a = x d = 1 for (i=2; 1; i++) { e = (a *= x) / (d *= i) if (e == 0) { if (f>0) while (f--) v = v*v; scale = z if (m) return (1/v); return (v/1); } v += e } } The following is code that uses the extended features of bc to implement a simple program for calculating checkbook balances. This program is best kept in a file so that it can be used many times without having to retype it at every use. scale=2 print "\nCheck book program!\n" print " Remember, deposits are negative transactions.\n" print " Exit by a 0 transaction.\n\n" print "Initial balance? "; bal = read() bal /= 1 print "\n" while (1) { "current balance = "; bal "transaction? "; trans = read() if (trans == 0) break; bal -= trans bal /= 1 } quit The following is the definition of the recursive factorial function. define f (x) { if (x <= 1) return (1); return (f(x-1) * x); } EDITLINE OPTIONS bc is compiled using the editline(3) library. This allows the user to do editing of lines before sending them to bc. It also allows for a history of previous lines typed. This adds to bc one more special variable. This special variable, history is the number of lines of history retained. The default value of -1 means that an unlimited number of his- tory lines are retained. Setting the value of history to a positive num- ber restricts the number of history lines to the number given. The value of 0 disables the history feature. For more information, read the user manual for the editline(3) library. DIFFERENCES This version of bc was implemented from the POSIX P1003.2/D11 draft and contains several differences and extensions relative to the draft and traditional implementations. It is not implemented in the traditional way using dc(1). This version is a single process which parses and runs a byte code translation of the program. There is an "undocumented" option (-c) that causes the program to output the byte code to the stan- dard output instead of running it. It was mainly used for debugging the parser and preparing the math library. A major source of differences is extensions, where a feature is extended to add more functionality and additions, where new features are added. The following is the list of differences and extensions. LANG environment This version does not conform to the POSIX standard in the processing of the LANG environment variable and all environment variables starting with LC_. names Traditional and POSIX bc have single letter names for functions, variables and arrays. They have been extended to be multi-character names that start with a letter and may contain letters, numbers and the under- score character. strings Strings are not allowed to contain NUL characters. POSIX says all characters must be included in strings. last POSIX bc does not have a last variable. Some implementations of bc use the period (.) in a similar way. comparisons POSIX bc allows comparisons only in the if statement, the while statement, and the second expression of the for statement. Also, only one relational operation is allowed in each of those statements. if statement, else clause POSIX bc does not have an else clause. for statement POSIX bc requires all expressions to be present in the for statement. &&, ||, ! POSIX bc does not have the logical operators. read function POSIX bc does not have a read function. print statement POSIX bc does not have a print statement . continue statement POSIX bc does not have a continue statement. return statement POSIX bc requires parentheses around the return expres- sion. array parameters POSIX bc does not (currently) support array parameters in full. The POSIX grammar allows for arrays in func- tion definitions, but does not provide a method to spec- ify an array as an actual parameter. (This is most likely an oversight in the grammar.) Traditional imple- mentations of bc have only call-by-value array parame- ters. function format POSIX bc requires the opening brace on the same line as the define key word and the auto statement on the next line. =+, =-, =*, =/, =%, =^ POSIX bc does not require these "old style" assignment operators to be defined. This version may allow these "old style" assignments. Use the limits statement to see if the installed version supports them. If it does support the "old style" assignment operators, the state- ment ``a =- 1'' will decrement a by 1 instead of setting a to the value -1. spaces in numbers Other implementations of bc allow spaces in numbers. For example, ``x=1 3'' would assign the value 13 to the variable x. The same statement would cause a syntax error in this version of bc. errors and execution This implementation varies from other implementations in terms of what code will be executed when syntax and other errors are found in the program. If a syntax error is found in a function definition, error recovery tries to find the beginning of a statement and continue to parse the function. Once a syntax error is found in the function, the function will not be callable and becomes undefined. Syntax errors in the interactive execution code will invalidate the current execution block. The execution block is terminated by an end of line that appears after a complete sequence of state- ments. For example, a = 1 b = 2 has two execution blocks and { a = 1 b = 2 } has one execution block. Any runtime error will termi- nate the execution of the current execution block. A runtime warning will not terminate the current execution block. interrupts During an interactive session, the SIGINT signal (usu- ally generated by the control-C character from the ter- minal) will cause execution of the current execution block to be interrupted. It will display a "runtime" error indicating which function was interrupted. After all runtime structures have been cleaned up, a message will be printed to notify the user that bc is ready for more input. All previously defined functions remain defined and the value of all non-auto variables are the value at the point of interruption. All auto variables and function parameters are removed during the clean up process. During a non-interactive session, the SIGINT signal will terminate the entire run of bc. LIMITS The following are the limits currently in place for this bc processor. Some of them may have been changed by an installation. Use the limits statement to see the actual values. BC_BASE_MAX The maximum output base is currently set at 999. The maximum input base is 16. BC_DIM_MAX This is currently an arbitrary limit of 65535 as dis- tributed. Your installation may be different. BC_SCALE_MAX The number of digits after the decimal point is limited to INT_MAX digits. Also, the number of digits before the decimal point is limited to INT_MAX digits. BC_STRING_MAX The limit on the number of characters in a string is INT_MAX characters. exponent The value of the exponent in the raise operation (^) is limited to LONG_MAX. variable names The current limit on the number of unique names is 32767 for each of simple variables, arrays and functions.
If any file on the command line can not be opened, bc will report that the file is unavailable and terminate. Also, there are compile and run time diagnostics that should be self-explanatory.
This man page documents bc version nb1.0.
Philip A. Nelson <firstname.lastname@example.com> ACKNOWLEDGEMENTS The author would like to thank Steve Sommars for his extensive help in testing the implementation. Many great suggestions were given. This is a much better product due to his involvement.
Error recovery is not very good yet. NetBSD 9.1 April 16, 2017 NetBSD 9.1

subset: commoncrawl


text:
Elizabeth Locke Amber Venetian Glass Intaglio "Cab Putto and Duck" Stud Earrings with Citrine
$4,1502 - 3 Day Delivery Purchase by phone at (800) 263-9510
Product Details
- 19k yellow gold
- color: amber
- Venetian glass intaglios backed with mother-of-pearl
- Round 5 mm cabochon citrine
- side gold dots on thin bezel
- pierced only, stud with butterfly back
- Approximate measurement including bezel 26mm vertically by 10mm across
- Available to ship via UPS or FedEx ER104096 service
Delivery & Returns
We ship all packages signature required by either FedEx or UPS. Orders placed before 2PM EST Monday – Thursday ship that day. Orders placed after 2PM EST on Thursday or during the weekend ship the following Monday. Signed signature waivers are required for those who wish the package left at the door.
Note that some rural addresses may take two days or longer to receive their packages.
We want you to be happy with your purchase, so we provide a 7-day return period.
If you decide that you would like to return your purchase, please request a return label via email to [email protected] or you may phone us at (800) 263-9510.
Sized rings, special orders and sale items are nonreturnable.


text:
Elisabeth Shue Scene
A married woman is ready to test out the libertine lifestyle in a Fountainebleau swingers club
Elisabeth Shue Scene
First name: Doryse, Age: 48 yo, City: Fountainebleau (FL)
We've been fans of libertine encounters for a few years now. My boyfriend and I try new experiences between libertines from time to time, lately it's swingers. Age is not important, but respect is essential for all of us to sleep together. We are only looking for a libertine man for hard sex. We are free on Sunday for this libertine plan on Fountainebleau. You can meet me outside. Don't hesitate to write a comment, we'll be happy to read it. We hope to give you a date for a beautiful libertine encounter. Kisses. See you soon.
Nymphomaniac in a relationship would love to have sex with a stranger on Ocala
Elisabeth Shue Scene
First name: Klervia, Age: 37 yo, City: Ocala (FL)
Hi there, I'm a very attractive and exciting woman who is 37 years old. My name is Klervia. We prefer to meet you at our home but if you want we can move on Ocala and its surroundings. We're only available during the week for this future threesome hookup. We've been fans of libertine dating for a few years now. We test new hot things regularly, these days it's swinging. We want a man or couple without taboo for this fuck because we want to have sex as much as possible!!! Mr. should preferably be tall, sorry but it's my little whim lately. So we want to take our pleasure with another libertine. We are quite open-minded. We are waiting for your responses. Big kisses.
Looking for a naughty plan with an older woman in Laredo
Elisabeth Shue Scene
First name: Maria-celeste, Age: 39 yo, City: Laredo (TX)
Welcome men, I am a slutty woman who is 39 years old and my name is Maria-celeste. I work in a lingerie shop. Otherwise, I'm separated because I want to sleep with a lot of guys. I want a guy who's hot and has a really nice member so he can give me a lot of pleasure because I'm such a horny slut. I know how to handle my hookups to make them want me. A hot date should make me come. I want a guy who's a good cunnilingus. Otherwise I'm a fan of sodomy but in a gentle way. I'm not against meeting up outdoors if you're into that. I'm attracted to a naughty guy who wants to dominate during our sexy encounter. I'm only here to enjoy myself. I don't care whether it's at your place or not, as long as it's clean. I can easily move around Laredo and its surroundings. I'm often free during the day. So, I'm looking forward to reading your comments. I'm looking forward to seeing you. I think we're going to get along great during this naughty meeting. I'm leaving! Big kisses.
I'm a hot cougar looking for some fun in the city
Elisabeth Shue Scene
First name: Rose-claire, Age: 41 yo, City: Grand Island (NE)
I am 41 years old, I live in Grand Island and I am a divorced mature woman. I much prefer online dating for the good reason that it allows me to talk with people more easily. I'm way too shy to go out clubbing or pub-crawling for potential guys. A one night stand should make me orgasm. I need a h that is a good browser. I'm also a fan of anal sex, but with tact. I'm not personally against a hookup in the great outdoors if you're into exhibitionism. I'm attracted to a naughty guy who wants to dominate during our sexy evening. I'm here to enjoy myself. I like gentlemen who are charming. I also need a naughty guy who's been spoiled by nature, because otherwise I don't enjoy myself. I just want to enjoy myself like never before. I'll be expecting you at the end of the week, and rather in the afternoon. We can meet up wherever you want, but it has to be near Grand Island. I will read your offers with impatience. I can't wait for our first date, it's what has me the most excited... kisses Rose-claire.
A pretty redhead girl would like to find a good fuck on Arvada
Elisabeth Shue Scene
First name: Christal, Age: 34 yo, City: Arvada (CO)
I'm a girl who's good at sucking dick to make you hard as a bull. Other than that, I love trying out unconventional sexual practices like double penetration. In reality, I don't have a preference about my one night stands. It is, however, important that the latter be free-spirited. I love foreplay because I enjoy taking my time before we see each other. We can meet up in Arvada and its surroundings. I can generally join you in the late afternoon to see each other. I'm eagerly awaiting your proposals. I'm looking forward to our first date, it's really exciting for me... kisses Christal.
No strings attached meeting Santa Clara: 35 year old woman who is up for anything
Elisabeth Shue Scene
First name: Shayli, Age: 35 yo, City: Santa Clara (CA)
I can move around easily in Santa Clara and its surroundings. I'm often available during the day. I don't care whether it's at your place or a hotel, as long as the places are clean. I just want to find a guy for a one night stand because I love having wild, no-strings-attached sex with someone I don't know. I like a lot of different foreplay so I need a big pig who can really deliver. I prefer a man who is quite young and the most important with a nice tool to give me a lot of pleasure as I am quite hot. I know how to deal with my encounters to charm them. Therefore, if you wish to get to know me better, please contact me. I hope you understood me and that you will be able to charm me. See you soon.
Beautiful married slut on Fall River for an exhibitionist meeting in the forest
Elisabeth Shue Scene
First name: Alysha, Age: 49 yo, City: Fall River (MA)
Hi guys, my name is Alysha and I'm in a relationship, I'm 49 years old. I'm very cute. My boyfriend and I are swingers. I'm looking for a nice, naughty guy who will make me come with my man because I am a greedy girl who loves having 2 guys for herself. Since we work every day, we would like to see you on the weekends and preferably at our place or in a hot club nearby Fall River. I engage in candaulism because I enjoy sleeping with another rascal but always under the watchful eye of my husband. I'm really greedy when I make love and I particularly appreciate being licked languorously. Now we want to discover your most libertine desires. I hope to read your messages. Kisses! See you soon.
Hot announcement: woman in couple on Flagstaff for a hot one-night stand
Elisabeth Shue Scene
First name: Cassydie, Age: 47 yo, City: Flagstaff (AZ)
I really enjoy giving blowjobs because it gets me off a lot. I need a guy who will be good at licking my pussy. I personally love taking your cock in my mouth and I'm pretty good at it. However, I want to be taken savagely as I love virile guys with a big penis. I'm a slut who wants to cum. I agree to set up a meeting at my place for this future hookup. I am also available during the day and during the week. I just want to fuck well. I love guys who are very tall. In addition, I demand a man who is spoiled by nature, because otherwise I don't get my foot. If you'd like, you can write a naughty proposal. I hope to see you on Flagstaff for this fuck session. Big kisses. Bye-bye.
A young woman on Stamford wants to try sex with some older guys
Elisabeth Shue Scene
First name: Marialine, Age: 27 yo, City: Stamford (CT)
I don't usually have a type when it comes to one night stands. However, it is mandatory that this lover be especially naughty. I need some foreplay because I love being all excited before we have sex together. I am new to libertine games like swinging or others. I want to do these things with a man who is an expert. For this sex plan, I am free on the weekends. I want to set up a first date at the restaurant so we can get to know each other. If you want, you can leave a comment. I hope to meet you in Stamford for this fuck. Kisses. See you later.
Nymphomaniac looking for fun in an outdoor threesome
Elisabeth Shue Scene
First name: Ghislaine, Age: 20 yo, City: Mauldin (SC)
Hi everyone, I'm a beautiful girl who is engaged, my name is Ghislaine and I'm 20 years old. I moved to Mauldin and I'm quite liberated. We love being in private clubs for pleasure. We are a very open couple. I personally prefer sex in threes because I'm greedy and my boyfriend is okay with sharing me. We just want to have fun with you. This is why we post on this libertine site because we love discovering other couples during wild nights. We would prefer to meet you at our apartment, but if you want we can come to Mauldin and its surroundings. We're mostly available for sex in the evening. Don't hesitate to leave a little note, we'll be delighted to discover it. We hope to give you a date for a beautiful libertine encounter. Big kisses. Bye Bye.
- Blue Mountain State Nude
- Tara Spencer Nairn Nude
- Lace Underwear Selfie
- Charlize Theron Nude Scenes
- Lake Bell Nude Scenes
- Mantis Nude
- Beverly Lynne Fucking
- Boobs Hanging Upside Down
- By The Sea Nude Scene
- Tuesday Weld Nude Photos
- Ophélie Bau Nude
- Ashley Judd Marilyn
- Florence Hall Nude
- Megan Fox Nude Jennifer's Body
- Dare Tits
- Photos Of Pamela Anderson Nude
- The Girl Next Door Nude
- Tamsin Greig Hot
- Brie Larson Breast


text:
Whipped Cream Chargers For Sale | Fast Express Delivery To Eumemmerring VIC 3177
Buy Whipped Cream Chargers | Quick Express Postage to Eumemmerring VIC 3177. See the full range of our products in our Whip cream charger online shop.
Popular Whip Cream Charger Items For Sale With Express Delivery To Eumemmerring VIC 3177
SSES Unflavoured Cream Chargers$33.97 – $2,984.97 Select options
Whip-It Chargers (N2O)$43.97 – $1,839.97 Select options
BestWhip Cream Chargers$35.97 – $2,994.97 Select options
Mosa Whipped Cream Chargers$54.00 – $647.00 Select options
SupremeWhip Cream Chargers$34.97 – $2,994.97 Select options
Ezywhip Pro Whipped Cream Chargers$52.00 – $637.00 Select options
ISI Pro Cream Chargers$60.00 – $1,080.00 Select options
Strawberry Flavoured Cream Chargers – FreshWhip$41.97 – $208.97 Select options
Banana Flavoured Cream Chargers – Infusionwhip$41.97 – $208.97 Select options
Blueberry Flavoured Cream Chargers – Infusionwhip$41.97 – $208.97 Select options
Cherry Flavoured Cream Chargers – Infusionwhip$41.97 – $208.97 Select options
Coconut Flavoured Cream Chargers – Infusionwhip$41.97 – $208.97 Select options
Related Products
Purchase Whipped Cream Chargers now and get them fast delivered express to your location. We also sell other related products. Check out the Best Cream whip Shop! Cheap prices & fast delivery.
If you want same day delivery (same night) aka right now delivery you may like to contact the following sites: Nangsta, Nang Delivery, Nangs Delivery, Best Nangs, Nang Delivery Melbourne.
Yes, we deliver all over Australia via Australia post or fast courier.
Our main delivery areas are major cities. However, we can also deliver to regional areas. You can get your products where ever Australia post deliver to.
Melbourne South Eastern Suburbs ;
Are you in Eumemmerring VIC 3177? We can get Nangs to you quickly!
Eumemmerring is a suburb in Melbourne Victoria Australia 32 km south-east from Melbourne's central business district. Its local government area is the City of Casey. At the 2016 Census Eumemmerring had a population of 1948.


text:
Planet X - The 2017 Arrival
The world's #1 eTextbook reader for students. VitalSource is the leading provider of online textbooks and course materials. More than 15 million users have used our Bookshelf platform over the past year to improve their learning experience and outcomes. With anytime, anywhere access and built-in tools like highlighters, flashcards, and study groups, it's easy to see why so many students are going digital with Bookshelf.
Over 2.7 million
titles available from more than 1,000 publishers
Over 65,000
customer reviews with an average rating of 9.5
Over 5 billion
digital pages viewed over the past 12 months
Over 7,000
institutions using Bookshelf across 241 countries


text:
This Business & Marketing Content & Content Perk Package is focused on "Maximizing The Value Of Your Time"
Only $27!
It starts with a Five Post Blog Series totaling no less than 2500 words.
- Take Radical Responsibility for Your Time;
- Let's Be Honest about How You Spend Your Time;
- Protect Your Time: Learn to Say "No" to Others;
- How to Let Go of Busy Work that Steals Your Time; and
- You Can Create the Time You Need.
About White Label Perks: Kelly McCausey, Samantha Angel & Avery Wilmer
Kelly has been helping entrepreneurs create the business they dream of online for more than 15 years, she knows content marketing from the inside out.
Samantha is a talented graphic designer with an eye for beautiful feminine images.
Avery is a copywriter who teaches her clients how to make content marketing fun and profitable.
Together they craft timely content you can use to connect with your community, grow your list and add to your bottom line.
More About This Pack:
We've crafted Ten Social Friendly Graphics to compliment the written content and make your posts more shareable.
Images come with PSD Files and we provide the beautiful typography as transparent PNG files so you can match them up with other photos if you wish. (Can be managed with PicMonkey or Canva if you don't have Photoshop!)
To save you even more time, we've written 30 Quick Social Blurbs you can use to promote your posts via Social Media.
We've Crafted These List Building Content Perks:
We provide you with an eCover & a Call to Action Graphic to be displayed with each part of the Blog Post Series.
A Beautiful Web eBooklet presenting the blog post content and images in one downloadable, easy to review format – with thoughtful questions included to spark thoughts.
A Printable Implementation Workbook, repeats the questions and provides space for journaling their answers to encourage time spent soaking in the ideas shared!
A series of three email autoresponders to connect with your leads.
Plus, our simple to implement opt-in copy to make it easy for you to get your landing page up quickly.
Add your own final 'Call to Action' page and invite your people to take their next step with you!


text:
|Show clams in the Middle East with profiles available.
|Show all clams of concern in the Middle East.
|Common Name
|Range ***
|No clams found for the criteria selected.
|Featured Articles:
Eight Species Declared Extinct But May Still be Out There
Twelve Incredibly Odd Endangered Creatures
Rare white giraffes sighted for the first time in Kenya
Captive cheetah gives birth to largest litter ever recorded
|More articles
This list combines species from several endangered species lists. Using the total count of species found on this site as an official count of endangered species of the world is not recommended. For more information on what creatures are listed on this site, please visit our About EEC page.


text:
Multiplayer discussion forum for Total War: Shogun 2
A forum for Fall of the Samurai multiplayer guides, FAQs, and faction strategies.
AggonyDuck's FoTS Avatar MP...
09-25-2013, 22:56
A forum for organization and discussion of Tournaments and Ladders hosted on the Org.
Clan Wars Competition XXXI -...
01-27-2013, 20:42
Forum for general clan communication, recruiting, and coordination.
12-24-2012, 16:49
A forum for Total War: Shogun 2 multiplayer guides, FAQs, and strategies.
09-21-2012, 16:33
A forum for players to sign and discuss the TW Code of Honour.
Welcome To The Code of Honor...
11-23-2017, 14:27


text:
In ancient Israel , it came to pass that a trader by the name of Abraham Com did take unto himself a healthy young wife by the name of Dorothy. (Dot)
Dot Com was a comely woman, large of breast, broad of shoulder, and long of leg. Indeed, she was often called Amazon Dot Com.
And she said unto Abraham, her husband, "Why dost thou travel so far from town to town with thy goods when thou canst trade without ever leaving thy tent?"
And Abraham did look at her as though she were several saddle bags short of a camel load, but simply said, "How, dear?"
And Dot replied, "I will place drums in all the towns and drums in between to send messages saying what you have for sale, and they will reply telling you who hath the best price. The sale can be made on the drums and delivery made by Uriah's Pony Stable (UPS)."
Abraham thought long and decided he would let Dot have her way with the drums.
And the drums rang out and were an immediate success. Abraham sold all the goods he had at the top price, without ever having to move from his tent.
To prevent neighboring countries from overhearing what the drums were saying, Dot devised a system that only she and the drummers knew. It was known as Must Send Drum Over Sound (MSDOS), and she also developed a language to transmit ideas and pictures – Hebrew To The People (HTTP).
And the young men did take to Dot Com's trading as doth the greedy horsefly take to camel dung. They were called Nomadic Ecclesiastical Rich Dominican Sybarites, or NERDS.
And lo, the land was so feverish with joy at the new riches and the deafening sound of drums that no one noticed that the real riches were going to that enterprising drum dealer, Brother William of Gates, who bought off every drum maker in the land. Indeed he did insist on drums to be made that would work only with Brother Gates' drumheads and drumsticks.
And Dot did say, "Oh, Abraham, what we have started is being taken over by others."
And Abraham looked out over the Bay of Ezekiel, or eBay as it came to be known.
He said, "We need a name that reflects what we are."
And Dot replied, "Young Ambitious Hebrew Owner Operators."
"YAHOO," said Abraham.
And because it was Dot's idea, they named it YAHOO Dot Com.
Abraham's cousin, Joshua, being the young Gregarious Energetic Educated Kid (GEEK) that he was, soon started using Dot's drums to locate things around the countryside.
It soon became known as God's Own Official Guide to Locating Everything (GOOGLE).
That is how it all began.
And that's the truth.
Note: Author unknown. Sometimes you find a real Gem out there in the Internet Wild!