| SELECT sub.ip FROM | |
| (SELECT set_masklen(((generate_series(1, | |
| (2 ^ (32 - masklen('10.10.100.0/24'::cidr)))::integer - 2) + | |
| '10.10.100.0/24'::cidr)::inet), 32) as ip) AS sub | |
| WHERE sub.ip NOT IN | |
| (SELECT ip_address from ip_table) | |
| AND sub.ip > set_masklen('10.10.100.0/24', 32)+10 | |
| AND sub.ip < set_masklen(broadcast('10.10.100.0/24')::inet, 32)-5; |
| --- | |
| language: objective-c | |
| before_script: | |
| - ./scripts/travis/add-key.sh | |
| after_script: | |
| - ./scripts/travis/remove-key.sh | |
| after_success: | |
| - ./scripts/travis/testflight.sh | |
| env: | |
| global: |
| # Composition of the containers | |
| owncloud: | |
| image: owncloud | |
| ports: | |
| - 80:80 | |
| volumes_from: | |
| - owncloud-data | |
| links: | |
| - postgres:owncloud-db |
| %%% Run with 'escript app_deps.erl' | |
| %%% Change the path in filelib:wildcard/1 as required to capture all | |
| %%% your dependencies. | |
| %%% | |
| %%% Rectangular nodes will represent library apps (no processes involved) | |
| %%% and the circular nodes will represent regular apps. An arrow going from | |
| %%% 'A -> B' means 'A depends on B'. | |
| %%% | |
| %%% This script depends on graphviz being present on the system. | |
| -module(app_deps). |
| #include<iostream> | |
| #include<string> | |
| #include<sstream> | |
| #define SIZE 700 | |
| using namespace std; | |
| class large{ | |
| int no[SIZE]; | |
| /* | |
| array is used to store the large number. |
I'm looking to collect information on why certain functionality found in Erlang/OTP is usually handled instead by a third party library in people's projects.
This could be bugs, missing functionality, poor interface, performance, etc.
Examples off the top of my head that need expanding on are:
| # Usage: | |
| # ruby -e "$(curl <url_to_this_raw_gist>)" https://www.youtube.com/watch?v=Jo1tjBmwuXI | |
| youtube_url = ARGV[0] | |
| puts "YouTube URL: #{youtube_url}" | |
| `mkdir youtube` | |
| Dir.chdir "youtube" | |
| `curl https://yt-dl.org/downloads/2014.10.13/youtube-dl > youtube-dl` |
Warning: Rebar3 works for me, probably won't work for you yet.
Rebar has been an important tool for many years and many Erlang developers, but for various reasons it has come to show it's age very quickly. The code has become overly complex, especially the transitive dependency management, and became clear to me and a few others that a partial rewrite was required.
The prevalence of rebar configs in projects meant backwards compatability was a must, however features have been both added and removed.