Is the address of a local variable a constexpr?





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







8















In Bjarne Stroustrup's book "The C++ Programming Language (4th Edition)" on p. 267 (Section 10.4.5 Address Constant Expressions), he uses a code example where the address of a local variable is set to a constexpr variable. I thought this looked odd, so I tried running the example with g++ version 7.3.0 and was unable to get the same results. Here is his code example verbatim (although slightly abridged):



extern char glob;

void f(char loc) {
constexpr const char* p0 = &glob; // OK: &glob's is a constant
constexpr const char* p2 = &loc; // OK: &loc is constant in its scope
}


When I run this, I get:



error: ‘(const char*)(& loc)’ is not a constant expression


Is something happening with g++ that I'm not aware of, or is there something more to Bjarne's example?










share|improve this question




















  • 2





    Clearly, &loc can't be a constexpr. However, these lines of code don't appear on my kindle version. He does show a constexpr for the address of a "C" style string in a local function. That's legal since these are in global space while loc is an argument on the stack and not constant. Is that example what you are referring to?

    – doug
    1 hour ago













  • @doug check section 10.4.5 Address Constant Expressions. I'll update the question to make this more clear. Also, my example is abridged

    – johnnyodonnell
    1 hour ago






  • 2





    char loc is a locally declared character that is not static. The next time f() is called there is no guarantee loc will have the same address. 10.4.5 makes that distinction between an address assigned by the linker and those assigned by the compiler. 2013 Stroustrup - The C++ Programming Language 4th Edition.pdf

    – David C. Rankin
    1 hour ago








  • 1





    @DavidC.Rankin it looks like your version (a pdf) is different from mine (a hard-copy). This must have been a mistake and was updated by the time your pdf was created.

    – johnnyodonnell
    1 hour ago






  • 2





    Yes, I was kinda scratching my head as to where &glob came from, but &loc was identifiable.

    – David C. Rankin
    58 mins ago


















8















In Bjarne Stroustrup's book "The C++ Programming Language (4th Edition)" on p. 267 (Section 10.4.5 Address Constant Expressions), he uses a code example where the address of a local variable is set to a constexpr variable. I thought this looked odd, so I tried running the example with g++ version 7.3.0 and was unable to get the same results. Here is his code example verbatim (although slightly abridged):



extern char glob;

void f(char loc) {
constexpr const char* p0 = &glob; // OK: &glob's is a constant
constexpr const char* p2 = &loc; // OK: &loc is constant in its scope
}


When I run this, I get:



error: ‘(const char*)(& loc)’ is not a constant expression


Is something happening with g++ that I'm not aware of, or is there something more to Bjarne's example?










share|improve this question




















  • 2





    Clearly, &loc can't be a constexpr. However, these lines of code don't appear on my kindle version. He does show a constexpr for the address of a "C" style string in a local function. That's legal since these are in global space while loc is an argument on the stack and not constant. Is that example what you are referring to?

    – doug
    1 hour ago













  • @doug check section 10.4.5 Address Constant Expressions. I'll update the question to make this more clear. Also, my example is abridged

    – johnnyodonnell
    1 hour ago






  • 2





    char loc is a locally declared character that is not static. The next time f() is called there is no guarantee loc will have the same address. 10.4.5 makes that distinction between an address assigned by the linker and those assigned by the compiler. 2013 Stroustrup - The C++ Programming Language 4th Edition.pdf

    – David C. Rankin
    1 hour ago








  • 1





    @DavidC.Rankin it looks like your version (a pdf) is different from mine (a hard-copy). This must have been a mistake and was updated by the time your pdf was created.

    – johnnyodonnell
    1 hour ago






  • 2





    Yes, I was kinda scratching my head as to where &glob came from, but &loc was identifiable.

    – David C. Rankin
    58 mins ago














8












8








8


1






In Bjarne Stroustrup's book "The C++ Programming Language (4th Edition)" on p. 267 (Section 10.4.5 Address Constant Expressions), he uses a code example where the address of a local variable is set to a constexpr variable. I thought this looked odd, so I tried running the example with g++ version 7.3.0 and was unable to get the same results. Here is his code example verbatim (although slightly abridged):



extern char glob;

void f(char loc) {
constexpr const char* p0 = &glob; // OK: &glob's is a constant
constexpr const char* p2 = &loc; // OK: &loc is constant in its scope
}


When I run this, I get:



error: ‘(const char*)(& loc)’ is not a constant expression


Is something happening with g++ that I'm not aware of, or is there something more to Bjarne's example?










share|improve this question
















In Bjarne Stroustrup's book "The C++ Programming Language (4th Edition)" on p. 267 (Section 10.4.5 Address Constant Expressions), he uses a code example where the address of a local variable is set to a constexpr variable. I thought this looked odd, so I tried running the example with g++ version 7.3.0 and was unable to get the same results. Here is his code example verbatim (although slightly abridged):



extern char glob;

void f(char loc) {
constexpr const char* p0 = &glob; // OK: &glob's is a constant
constexpr const char* p2 = &loc; // OK: &loc is constant in its scope
}


When I run this, I get:



error: ‘(const char*)(& loc)’ is not a constant expression


Is something happening with g++ that I'm not aware of, or is there something more to Bjarne's example?







c++ c++11 constexpr memory-address






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 56 mins ago







johnnyodonnell

















asked 1 hour ago









johnnyodonnelljohnnyodonnell

378114




378114








  • 2





    Clearly, &loc can't be a constexpr. However, these lines of code don't appear on my kindle version. He does show a constexpr for the address of a "C" style string in a local function. That's legal since these are in global space while loc is an argument on the stack and not constant. Is that example what you are referring to?

    – doug
    1 hour ago













  • @doug check section 10.4.5 Address Constant Expressions. I'll update the question to make this more clear. Also, my example is abridged

    – johnnyodonnell
    1 hour ago






  • 2





    char loc is a locally declared character that is not static. The next time f() is called there is no guarantee loc will have the same address. 10.4.5 makes that distinction between an address assigned by the linker and those assigned by the compiler. 2013 Stroustrup - The C++ Programming Language 4th Edition.pdf

    – David C. Rankin
    1 hour ago








  • 1





    @DavidC.Rankin it looks like your version (a pdf) is different from mine (a hard-copy). This must have been a mistake and was updated by the time your pdf was created.

    – johnnyodonnell
    1 hour ago






  • 2





    Yes, I was kinda scratching my head as to where &glob came from, but &loc was identifiable.

    – David C. Rankin
    58 mins ago














  • 2





    Clearly, &loc can't be a constexpr. However, these lines of code don't appear on my kindle version. He does show a constexpr for the address of a "C" style string in a local function. That's legal since these are in global space while loc is an argument on the stack and not constant. Is that example what you are referring to?

    – doug
    1 hour ago













  • @doug check section 10.4.5 Address Constant Expressions. I'll update the question to make this more clear. Also, my example is abridged

    – johnnyodonnell
    1 hour ago






  • 2





    char loc is a locally declared character that is not static. The next time f() is called there is no guarantee loc will have the same address. 10.4.5 makes that distinction between an address assigned by the linker and those assigned by the compiler. 2013 Stroustrup - The C++ Programming Language 4th Edition.pdf

    – David C. Rankin
    1 hour ago








  • 1





    @DavidC.Rankin it looks like your version (a pdf) is different from mine (a hard-copy). This must have been a mistake and was updated by the time your pdf was created.

    – johnnyodonnell
    1 hour ago






  • 2





    Yes, I was kinda scratching my head as to where &glob came from, but &loc was identifiable.

    – David C. Rankin
    58 mins ago








2




2





Clearly, &loc can't be a constexpr. However, these lines of code don't appear on my kindle version. He does show a constexpr for the address of a "C" style string in a local function. That's legal since these are in global space while loc is an argument on the stack and not constant. Is that example what you are referring to?

– doug
1 hour ago







Clearly, &loc can't be a constexpr. However, these lines of code don't appear on my kindle version. He does show a constexpr for the address of a "C" style string in a local function. That's legal since these are in global space while loc is an argument on the stack and not constant. Is that example what you are referring to?

– doug
1 hour ago















@doug check section 10.4.5 Address Constant Expressions. I'll update the question to make this more clear. Also, my example is abridged

– johnnyodonnell
1 hour ago





@doug check section 10.4.5 Address Constant Expressions. I'll update the question to make this more clear. Also, my example is abridged

– johnnyodonnell
1 hour ago




2




2





char loc is a locally declared character that is not static. The next time f() is called there is no guarantee loc will have the same address. 10.4.5 makes that distinction between an address assigned by the linker and those assigned by the compiler. 2013 Stroustrup - The C++ Programming Language 4th Edition.pdf

– David C. Rankin
1 hour ago







char loc is a locally declared character that is not static. The next time f() is called there is no guarantee loc will have the same address. 10.4.5 makes that distinction between an address assigned by the linker and those assigned by the compiler. 2013 Stroustrup - The C++ Programming Language 4th Edition.pdf

– David C. Rankin
1 hour ago






1




1





@DavidC.Rankin it looks like your version (a pdf) is different from mine (a hard-copy). This must have been a mistake and was updated by the time your pdf was created.

– johnnyodonnell
1 hour ago





@DavidC.Rankin it looks like your version (a pdf) is different from mine (a hard-copy). This must have been a mistake and was updated by the time your pdf was created.

– johnnyodonnell
1 hour ago




2




2





Yes, I was kinda scratching my head as to where &glob came from, but &loc was identifiable.

– David C. Rankin
58 mins ago





Yes, I was kinda scratching my head as to where &glob came from, but &loc was identifiable.

– David C. Rankin
58 mins ago












3 Answers
3






active

oldest

votes


















6














Bjarne Stroustrup's book "The C++ Programming Language (4th Edition)" on p. 267 refers to the following code:



constexpr const char* p1="asdf";


This is OK because "asdf" is stored in a fixed memory location.



void f(char loc) {
constexpr const char* p0 = &glob; // OK: &glob's is a constant
constexpr const char* p2 = &loc; // OK: &loc is constant in its scope
}


However, loc is not in a fixed memory location. it's on the stack and will have varying locations depending on when it is called.






share|improve this answer
























  • So, you're saying that Bjarne should not have said that &loc will be "OK", right?

    – johnnyodonnell
    1 hour ago













  • The example code I used in the question is taken verbatim. After looking at @doug's pdf, I think the hard-copy book that I own is incorrect. I think this mistake was updated in later versions.

    – johnnyodonnell
    1 hour ago











  • Is it the same as this? github.com/boydfd/books/blob/master/seeing/stalled/…

    – jackw11111
    59 mins ago











  • @jackw11111 my version is different from the pdf provided in that link. doug provided a link to the same pdf. My hard-copy and that pdf show different examples for section 10.4.5

    – johnnyodonnell
    58 mins ago



















2














It appears that the example from section 10.4.5 provided in my hard-copy of the "The C++ Programming Language (4th Edition)" is incorrect. And so I've concluded that the address of a local variable is not a constexpr.



The example appears to have been updated in some pdf versions as seen here:



enter image description here






share|improve this answer































    1














    Just to add to other answers that have pointed out the mistake, C++ standard only allows constexpr pointers to objects of static-storage duration, one past the end of such, or nullptr. See [expr.const/8] specifically #8.2;



    It's worth noting that:





    • string-literals have static-storage duration:

    • Based on constraints in declaring extern variables, they'll inherently have static-storage duration or thread local-storage duration.


    Hence this is valid:



    #include <string>

    extern char glob;
    std::string boom = "Haha";

    void f(char loc) {
    constexpr const char* p1 = &glob;
    constexpr std::string* p2 = nullptr;
    constexpr std::string* p3 = &boom;
    }





    share|improve this answer
























      Your Answer






      StackExchange.ifUsing("editor", function () {
      StackExchange.using("externalEditor", function () {
      StackExchange.using("snippets", function () {
      StackExchange.snippets.init();
      });
      });
      }, "code-snippets");

      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "1"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55698844%2fis-the-address-of-a-local-variable-a-constexpr%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      6














      Bjarne Stroustrup's book "The C++ Programming Language (4th Edition)" on p. 267 refers to the following code:



      constexpr const char* p1="asdf";


      This is OK because "asdf" is stored in a fixed memory location.



      void f(char loc) {
      constexpr const char* p0 = &glob; // OK: &glob's is a constant
      constexpr const char* p2 = &loc; // OK: &loc is constant in its scope
      }


      However, loc is not in a fixed memory location. it's on the stack and will have varying locations depending on when it is called.






      share|improve this answer
























      • So, you're saying that Bjarne should not have said that &loc will be "OK", right?

        – johnnyodonnell
        1 hour ago













      • The example code I used in the question is taken verbatim. After looking at @doug's pdf, I think the hard-copy book that I own is incorrect. I think this mistake was updated in later versions.

        – johnnyodonnell
        1 hour ago











      • Is it the same as this? github.com/boydfd/books/blob/master/seeing/stalled/…

        – jackw11111
        59 mins ago











      • @jackw11111 my version is different from the pdf provided in that link. doug provided a link to the same pdf. My hard-copy and that pdf show different examples for section 10.4.5

        – johnnyodonnell
        58 mins ago
















      6














      Bjarne Stroustrup's book "The C++ Programming Language (4th Edition)" on p. 267 refers to the following code:



      constexpr const char* p1="asdf";


      This is OK because "asdf" is stored in a fixed memory location.



      void f(char loc) {
      constexpr const char* p0 = &glob; // OK: &glob's is a constant
      constexpr const char* p2 = &loc; // OK: &loc is constant in its scope
      }


      However, loc is not in a fixed memory location. it's on the stack and will have varying locations depending on when it is called.






      share|improve this answer
























      • So, you're saying that Bjarne should not have said that &loc will be "OK", right?

        – johnnyodonnell
        1 hour ago













      • The example code I used in the question is taken verbatim. After looking at @doug's pdf, I think the hard-copy book that I own is incorrect. I think this mistake was updated in later versions.

        – johnnyodonnell
        1 hour ago











      • Is it the same as this? github.com/boydfd/books/blob/master/seeing/stalled/…

        – jackw11111
        59 mins ago











      • @jackw11111 my version is different from the pdf provided in that link. doug provided a link to the same pdf. My hard-copy and that pdf show different examples for section 10.4.5

        – johnnyodonnell
        58 mins ago














      6












      6








      6







      Bjarne Stroustrup's book "The C++ Programming Language (4th Edition)" on p. 267 refers to the following code:



      constexpr const char* p1="asdf";


      This is OK because "asdf" is stored in a fixed memory location.



      void f(char loc) {
      constexpr const char* p0 = &glob; // OK: &glob's is a constant
      constexpr const char* p2 = &loc; // OK: &loc is constant in its scope
      }


      However, loc is not in a fixed memory location. it's on the stack and will have varying locations depending on when it is called.






      share|improve this answer













      Bjarne Stroustrup's book "The C++ Programming Language (4th Edition)" on p. 267 refers to the following code:



      constexpr const char* p1="asdf";


      This is OK because "asdf" is stored in a fixed memory location.



      void f(char loc) {
      constexpr const char* p0 = &glob; // OK: &glob's is a constant
      constexpr const char* p2 = &loc; // OK: &loc is constant in its scope
      }


      However, loc is not in a fixed memory location. it's on the stack and will have varying locations depending on when it is called.







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered 1 hour ago









      dougdoug

      8621410




      8621410













      • So, you're saying that Bjarne should not have said that &loc will be "OK", right?

        – johnnyodonnell
        1 hour ago













      • The example code I used in the question is taken verbatim. After looking at @doug's pdf, I think the hard-copy book that I own is incorrect. I think this mistake was updated in later versions.

        – johnnyodonnell
        1 hour ago











      • Is it the same as this? github.com/boydfd/books/blob/master/seeing/stalled/…

        – jackw11111
        59 mins ago











      • @jackw11111 my version is different from the pdf provided in that link. doug provided a link to the same pdf. My hard-copy and that pdf show different examples for section 10.4.5

        – johnnyodonnell
        58 mins ago



















      • So, you're saying that Bjarne should not have said that &loc will be "OK", right?

        – johnnyodonnell
        1 hour ago













      • The example code I used in the question is taken verbatim. After looking at @doug's pdf, I think the hard-copy book that I own is incorrect. I think this mistake was updated in later versions.

        – johnnyodonnell
        1 hour ago











      • Is it the same as this? github.com/boydfd/books/blob/master/seeing/stalled/…

        – jackw11111
        59 mins ago











      • @jackw11111 my version is different from the pdf provided in that link. doug provided a link to the same pdf. My hard-copy and that pdf show different examples for section 10.4.5

        – johnnyodonnell
        58 mins ago

















      So, you're saying that Bjarne should not have said that &loc will be "OK", right?

      – johnnyodonnell
      1 hour ago







      So, you're saying that Bjarne should not have said that &loc will be "OK", right?

      – johnnyodonnell
      1 hour ago















      The example code I used in the question is taken verbatim. After looking at @doug's pdf, I think the hard-copy book that I own is incorrect. I think this mistake was updated in later versions.

      – johnnyodonnell
      1 hour ago





      The example code I used in the question is taken verbatim. After looking at @doug's pdf, I think the hard-copy book that I own is incorrect. I think this mistake was updated in later versions.

      – johnnyodonnell
      1 hour ago













      Is it the same as this? github.com/boydfd/books/blob/master/seeing/stalled/…

      – jackw11111
      59 mins ago





      Is it the same as this? github.com/boydfd/books/blob/master/seeing/stalled/…

      – jackw11111
      59 mins ago













      @jackw11111 my version is different from the pdf provided in that link. doug provided a link to the same pdf. My hard-copy and that pdf show different examples for section 10.4.5

      – johnnyodonnell
      58 mins ago





      @jackw11111 my version is different from the pdf provided in that link. doug provided a link to the same pdf. My hard-copy and that pdf show different examples for section 10.4.5

      – johnnyodonnell
      58 mins ago













      2














      It appears that the example from section 10.4.5 provided in my hard-copy of the "The C++ Programming Language (4th Edition)" is incorrect. And so I've concluded that the address of a local variable is not a constexpr.



      The example appears to have been updated in some pdf versions as seen here:



      enter image description here






      share|improve this answer




























        2














        It appears that the example from section 10.4.5 provided in my hard-copy of the "The C++ Programming Language (4th Edition)" is incorrect. And so I've concluded that the address of a local variable is not a constexpr.



        The example appears to have been updated in some pdf versions as seen here:



        enter image description here






        share|improve this answer


























          2












          2








          2







          It appears that the example from section 10.4.5 provided in my hard-copy of the "The C++ Programming Language (4th Edition)" is incorrect. And so I've concluded that the address of a local variable is not a constexpr.



          The example appears to have been updated in some pdf versions as seen here:



          enter image description here






          share|improve this answer













          It appears that the example from section 10.4.5 provided in my hard-copy of the "The C++ Programming Language (4th Edition)" is incorrect. And so I've concluded that the address of a local variable is not a constexpr.



          The example appears to have been updated in some pdf versions as seen here:



          enter image description here







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 52 mins ago









          johnnyodonnelljohnnyodonnell

          378114




          378114























              1














              Just to add to other answers that have pointed out the mistake, C++ standard only allows constexpr pointers to objects of static-storage duration, one past the end of such, or nullptr. See [expr.const/8] specifically #8.2;



              It's worth noting that:





              • string-literals have static-storage duration:

              • Based on constraints in declaring extern variables, they'll inherently have static-storage duration or thread local-storage duration.


              Hence this is valid:



              #include <string>

              extern char glob;
              std::string boom = "Haha";

              void f(char loc) {
              constexpr const char* p1 = &glob;
              constexpr std::string* p2 = nullptr;
              constexpr std::string* p3 = &boom;
              }





              share|improve this answer




























                1














                Just to add to other answers that have pointed out the mistake, C++ standard only allows constexpr pointers to objects of static-storage duration, one past the end of such, or nullptr. See [expr.const/8] specifically #8.2;



                It's worth noting that:





                • string-literals have static-storage duration:

                • Based on constraints in declaring extern variables, they'll inherently have static-storage duration or thread local-storage duration.


                Hence this is valid:



                #include <string>

                extern char glob;
                std::string boom = "Haha";

                void f(char loc) {
                constexpr const char* p1 = &glob;
                constexpr std::string* p2 = nullptr;
                constexpr std::string* p3 = &boom;
                }





                share|improve this answer


























                  1












                  1








                  1







                  Just to add to other answers that have pointed out the mistake, C++ standard only allows constexpr pointers to objects of static-storage duration, one past the end of such, or nullptr. See [expr.const/8] specifically #8.2;



                  It's worth noting that:





                  • string-literals have static-storage duration:

                  • Based on constraints in declaring extern variables, they'll inherently have static-storage duration or thread local-storage duration.


                  Hence this is valid:



                  #include <string>

                  extern char glob;
                  std::string boom = "Haha";

                  void f(char loc) {
                  constexpr const char* p1 = &glob;
                  constexpr std::string* p2 = nullptr;
                  constexpr std::string* p3 = &boom;
                  }





                  share|improve this answer













                  Just to add to other answers that have pointed out the mistake, C++ standard only allows constexpr pointers to objects of static-storage duration, one past the end of such, or nullptr. See [expr.const/8] specifically #8.2;



                  It's worth noting that:





                  • string-literals have static-storage duration:

                  • Based on constraints in declaring extern variables, they'll inherently have static-storage duration or thread local-storage duration.


                  Hence this is valid:



                  #include <string>

                  extern char glob;
                  std::string boom = "Haha";

                  void f(char loc) {
                  constexpr const char* p1 = &glob;
                  constexpr std::string* p2 = nullptr;
                  constexpr std::string* p3 = &boom;
                  }






                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered 35 mins ago









                  WhiZTiMWhiZTiM

                  18.1k33153




                  18.1k33153






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Stack Overflow!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55698844%2fis-the-address-of-a-local-variable-a-constexpr%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      Masuk log Menu navigasi

                      Identifying “long and narrow” polygons in with PostGISlength and width of polygonWhy postgis st_overlaps reports Qgis' “avoid intersections” generated polygon as overlapping with others?Adjusting polygons to boundary and filling holesDrawing polygons with fixed area?How to remove spikes in Polygons with PostGISDeleting sliver polygons after difference operation in QGIS?Snapping boundaries in PostGISSplit polygon into parts adding attributes based on underlying polygon in QGISSplitting overlap between polygons and assign to nearest polygon using PostGIS?Expanding polygons and clipping at midpoint?Removing Intersection of Buffers in Same Layers

                      Старые Смолеговицы Содержание История | География | Демография | Достопримечательности | Примечания | НавигацияHGЯOLHGЯOL41 206 832 01641 606 406 141Административно-территориальное деление Ленинградской области«Переписная оброчная книга Водской пятины 1500 года», С. 793«Карта Ингерманландии: Ивангорода, Яма, Копорья, Нотеборга», по материалам 1676 г.«Генеральная карта провинции Ингерманландии» Э. Белинга и А. Андерсина, 1704 г., составлена по материалам 1678 г.«Географический чертёж над Ижорскою землей со своими городами» Адриана Шонбека 1705 г.Новая и достоверная всей Ингерманландии ланткарта. Грав. А. Ростовцев. СПб., 1727 г.Топографическая карта Санкт-Петербургской губернии. 5-и верстка. Шуберт. 1834 г.Описание Санкт-Петербургской губернии по уездам и станамСпецкарта западной части России Ф. Ф. Шуберта. 1844 г.Алфавитный список селений по уездам и станам С.-Петербургской губернииСписки населённых мест Российской Империи, составленные и издаваемые центральным статистическим комитетом министерства внутренних дел. XXXVII. Санкт-Петербургская губерния. По состоянию на 1862 год. СПб. 1864. С. 203Материалы по статистике народного хозяйства в С.-Петербургской губернии. Вып. IX. Частновладельческое хозяйство в Ямбургском уезде. СПб, 1888, С. 146, С. 2, 7, 54Положение о гербе муниципального образования Курское сельское поселениеСправочник истории административно-территориального деления Ленинградской области.Топографическая карта Ленинградской области, квадрат О-35-23-В (Хотыницы), 1930 г.АрхивированоАдминистративно-территориальное деление Ленинградской области. — Л., 1933, С. 27, 198АрхивированоАдминистративно-экономический справочник по Ленинградской области. — Л., 1936, с. 219АрхивированоАдминистративно-территориальное деление Ленинградской области. — Л., 1966, с. 175АрхивированоАдминистративно-территориальное деление Ленинградской области. — Лениздат, 1973, С. 180АрхивированоАдминистративно-территориальное деление Ленинградской области. — Лениздат, 1990, ISBN 5-289-00612-5, С. 38АрхивированоАдминистративно-территориальное деление Ленинградской области. — СПб., 2007, с. 60АрхивированоКоряков Юрий База данных «Этно-языковой состав населённых пунктов России». Ленинградская область.Административно-территориальное деление Ленинградской области. — СПб, 1997, ISBN 5-86153-055-6, С. 41АрхивированоКультовый комплекс Старые Смолеговицы // Электронная энциклопедия ЭрмитажаПроблемы выявления, изучения и сохранения культовых комплексов с каменными крестами: по материалам работ 2016-2017 гг. в Ленинградской области