GNOME.org
 

[gnome-devel-docs] programming-guidelines: Use https for Wikipedia link

commit 608ded4dc736c56751c87b783ae0bb6d2199ba90
Author: Andre Klapper <a9016009 gmx de>
Date:   Fri Mar 1 02:51:54 2019 +0100

    programming-guidelines: Use https for Wikipedia link

 programming-guidelines/C/api-stability.page     |  4 ++--
 programming-guidelines/C/databases.page         |  2 +-
 programming-guidelines/C/gerror.page            |  2 +-
 programming-guidelines/C/introspection.page     |  4 ++--
 programming-guidelines/C/main-contexts.page     | 10 +++++-----
 programming-guidelines/C/tooling.page           |  2 +-
 programming-guidelines/C/unit-testing.page      |  6 +++---
 programming-guidelines/C/writing-good-code.page |  2 +-
 8 files changed, 16 insertions(+), 16 deletions(-)
---
diff --git a/programming-guidelines/C/api-stability.page b/programming-guidelines/C/api-stability.page
index 9ecbb376..0f88effa 100644
--- a/programming-guidelines/C/api-stability.page
+++ b/programming-guidelines/C/api-stability.page
@@ -183,11 +183,11 @@
     </p>
     <list>
       <item><p>
-        <link href="http://en.wikipedia.org/wiki/Application_programming_interface";>Wikipedia
+        <link href="https://en.wikipedia.org/wiki/Application_programming_interface";>Wikipedia
         page on APIs</link>
       </p></item>
       <item><p>
-        <link href="http://en.wikipedia.org/wiki/Application_binary_interface";>Wikipedia
+        <link href="https://en.wikipedia.org/wiki/Application_binary_interface";>Wikipedia
         page on ABIs</link>
       </p></item>
       <item><p>
diff --git a/programming-guidelines/C/databases.page b/programming-guidelines/C/databases.page
index 6966b0ae..1b43c604 100644
--- a/programming-guidelines/C/databases.page
+++ b/programming-guidelines/C/databases.page
@@ -120,7 +120,7 @@
         <link href="https://www.sqlite.org/c3ref/bind_blob.html";>value
         binding</link> API, rather than by constructing SQL strings then passing
         them to SQLite to parse. Constructing strings makes
-        <link href="http://en.wikipedia.org/wiki/SQL_injection";>SQL
+        <link href="https://en.wikipedia.org/wiki/SQL_injection";>SQL
         injection</link> vulnerabilities very likely, which can give attackers
         access to arbitrary user data from the database.
       </p>
diff --git a/programming-guidelines/C/gerror.page b/programming-guidelines/C/gerror.page
index 03360aed..df585f13 100644
--- a/programming-guidelines/C/gerror.page
+++ b/programming-guidelines/C/gerror.page
@@ -27,7 +27,7 @@
       <link 
href="https://developer.gnome.org/glib/stable/glib-Error-Reporting.html";><code>GError</code></link>
       is the standard error reporting mechanism for GLib-using code, and can be
       thought of as a C implementation of an
-      <link href="http://en.wikipedia.org/wiki/Exception_handling";>exception</link>.
+      <link href="https://en.wikipedia.org/wiki/Exception_handling";>exception</link>.
     </p>
 
     <p>
diff --git a/programming-guidelines/C/introspection.page b/programming-guidelines/C/introspection.page
index a0c4fb75..1afba867 100644
--- a/programming-guidelines/C/introspection.page
+++ b/programming-guidelines/C/introspection.page
@@ -27,8 +27,8 @@
       introspection</link> (abbreviated ‘GIR’) is a system which extracts APIs
       from C code and produces binary type libraries which can be used by non-C
       language bindings, and other tools, to
-      <link href="http://en.wikipedia.org/wiki/Type_introspection";>introspect</link>
-      or <link href="http://en.wikipedia.org/wiki/Language_binding";>wrap</link>
+      <link href="https://en.wikipedia.org/wiki/Type_introspection";>introspect</link>
+      or <link href="https://en.wikipedia.org/wiki/Language_binding";>wrap</link>
       the original C libraries. It uses a system of annotations in documentation
       comments in the C code to expose extra information about the APIs which is
       not machine readable from the code itself.
diff --git a/programming-guidelines/C/main-contexts.page b/programming-guidelines/C/main-contexts.page
index 441bc0fa..c3ff8a7a 100644
--- a/programming-guidelines/C/main-contexts.page
+++ b/programming-guidelines/C/main-contexts.page
@@ -64,7 +64,7 @@
     <p>
       <link 
href="https://developer.gnome.org/glib/stable/glib-The-Main-Event-Loop.html#GMainContext";><code>GMainContext</code></link>
       is a generalized implementation of an
-      <link href="http://en.wikipedia.org/wiki/Event_loop";>event loop</link>,
+      <link href="https://en.wikipedia.org/wiki/Event_loop";>event loop</link>,
       useful for implementing polled file I/O or event-based widget systems
       (such as GTK+). It is at the core of almost every GLib application. To
       understand <code>GMainContext</code> requires understanding
@@ -424,7 +424,7 @@ do_computation (gpointer user_data)
       global-default or thread-default contexts. Otherwise,
       <code>GSource</code>s created in the application may be dispatched
       when the application is not expecting it, causing
-      <link href="http://en.wikipedia.org/wiki/Reentrancy_%28computing%29";>re-entrancy
+      <link href="https://en.wikipedia.org/wiki/Reentrancy_%28computing%29";>re-entrancy
       problems</link> for the application code.
     </p>
 
@@ -495,7 +495,7 @@ do_computation (gpointer user_data)
       the function should be executing in</em>. This assumes the typical case
       that every thread has a <em>single</em> main context running in a main
       loop. A main context effectively provides a work or
-      <link href="http://en.wikipedia.org/wiki/Message_queue";>message
+      <link href="https://en.wikipedia.org/wiki/Message_queue";>message
       queue</link> for the thread — something which the thread can
       periodically check to determine if there is work pending from
       another thread. Putting a message on this queue – invoking a function in
@@ -518,7 +518,7 @@ do_computation (gpointer user_data)
         data it accesses. This assumes that other threads are implemented
         similarly and hence most data is only accessed by a single thread, with
         threads communicating by
-        <link href="http://en.wikipedia.org/wiki/Message_passing";>message
+        <link href="https://en.wikipedia.org/wiki/Message_passing";>message
         passing</link>. This allows each thread to update its data at its
         leisure, which significantly simplifies locking.
      </p>
@@ -710,7 +710,7 @@ main (void)
         <p>
           To maintain thread safety, data which is potentially accessed by
           multiple threads must make those accesses mutually exclusive using a
-          <link href="http://en.wikipedia.org/wiki/Mutual_exclusion";>mutex</link>.
+          <link href="https://en.wikipedia.org/wiki/Mutual_exclusion";>mutex</link>.
           Data potentially accessed by multiple threads:
           <code>thread1_main_context</code>, passed in the fork call to
           <code>thread1_main</code>; and <code>some_object</code>, a reference to
diff --git a/programming-guidelines/C/tooling.page b/programming-guidelines/C/tooling.page
index 015849c2..a16f5a2f 100644
--- a/programming-guidelines/C/tooling.page
+++ b/programming-guidelines/C/tooling.page
@@ -423,7 +423,7 @@ EXTRA_DIST = $(VALGRIND_SUPPRESSIONS_FILES)</code>
 
     <p>
       lcov supports
-      <link href="http://en.wikipedia.org/wiki/Code_coverage#Basic_coverage_criteria";>
+      <link href="https://en.wikipedia.org/wiki/Code_coverage#Basic_coverage_criteria";>
       branch coverage measurement</link>, so is not suitable for demonstrating
       coverage of safety critical code. It is perfectly suitable for
       non-safety critical code.
diff --git a/programming-guidelines/C/unit-testing.page b/programming-guidelines/C/unit-testing.page
index 2b733a53..6837b182 100644
--- a/programming-guidelines/C/unit-testing.page
+++ b/programming-guidelines/C/unit-testing.page
@@ -195,7 +195,7 @@ EXTRA_DIST = $(test_files)
     <p>
       Certain types of code are quite repetitive, and require a lot of unit
       tests to gain good coverage; but are appropriate for
-      <link href="http://en.wikipedia.org/wiki/Test_data_generation";>test data
+      <link href="https://en.wikipedia.org/wiki/Test_data_generation";>test data
       generation</link>, where a tool is used to automatically generate test
       vectors for the code. This can drastically reduce the time needed for
       writing unit tests, for code in these specific domains.
@@ -280,11 +280,11 @@ json-schema-generate --invalid-only schema.json</code>
         for testability</link>
       </p></item>
       <item><p>
-        <link href="http://en.wikipedia.org/wiki/Software_testability";>Software
+        <link href="https://en.wikipedia.org/wiki/Software_testability";>Software
         testability</link>
       </p></item>
       <item><p>
-        <link href="http://en.wikipedia.org/wiki/Dependency_injection";>Dependency
+        <link href="https://en.wikipedia.org/wiki/Dependency_injection";>Dependency
         injection</link>
       </p></item>
       <item><p>
diff --git a/programming-guidelines/C/writing-good-code.page b/programming-guidelines/C/writing-good-code.page
index 6cb93272..1ff2983b 100644
--- a/programming-guidelines/C/writing-good-code.page
+++ b/programming-guidelines/C/writing-good-code.page
@@ -135,7 +135,7 @@
         </link>, by Martin Fowler.
       </p></item>
       <item><p>
-        <link href="http://en.wikipedia.org/wiki/Design_Patterns";>
+        <link href="https://en.wikipedia.org/wiki/Design_Patterns";>
           Design Patterns: Elements of Reusable Object-Oriented Software
         </link>, by Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides.
       </p></item>
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]