-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
erb.rb: deprecate safe_level of ERB.new
Also, as it's in the middle of the list of 4 arguments, 3rd and 4th arguments (trim_mode, eoutvar) are changed to keyword arguments. Old ways to specify arguments are deprecated and warned now. bin/erb: deprecate -S option. We'll remove all of deprecated ones at Ruby 2.7+. enc/make_encmake.rb: stopped using deprecated interface ext/etc/mkconstants.rb: ditto ext/socket/mkconstants.rb: ditto sample/ripper/ruby2html.rb: ditto spec/ruby/library/erb/defmethod/def_erb_method_spec.rb: ditto spec/ruby/library/erb/new_spec.rb: ditto test/erb/test_erb.rb: ditto test/erb/test_erb_command.rb: ditto tool/generic_erb.rb: ditto tool/ruby_vm/helpers/dumper.rb: ditto tool/transcode-tblgen.rb: ditto lib/rdoc/erbio.rb: ditto lib/rdoc/generator/darkfish.rb: ditto [Feature #14256] git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@62529 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- Loading branch information
Showing
16 changed files
with
236 additions
and
70 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
cc777d0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@k0kubun
I've got a doc web site at https://msp-greg.github.io/, and I often update it along with the ruby-loco test results. Today's run just had the following shown in the log, which I haven't seen previously. This occurred while parsing the socket extension.
I haven't looked into the issue, but I thought this info might make sense to you...
EDIT: This happened under Windows (MinGW bulld) when doc'ing 62529 but running 62526.
Thanks, Greg
cc777d0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It has so many items and I couldn't find which has the result in it :)
Ummm, I can't imagine the reason that such error occurs with the change. Ruby code generated by ERB seems broken somehow. I'll try to reproduce it on some MinGW environment tomorrow. Please wait for a while.
cc777d0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry. That was really unclear, unless you're me...
Please disregard this, as after checking ruby docs at https://docs.ruby-lang.org/en and https://ruby-doc.org, it appears I must be doing something specific to show these constants in Socket.
At some point, the
Socket::Constants
module definition in trunk is no longer found by the parsing, which also causes the constants inSocket
to disappear. But, the last parsing of 2.5 they are shown here.I've got notes regarding this type of code in my doc system, but they're scattered, and I haven't needed to regularly update the code. I need to get all the notes into one file, as I don't recall where the doc system is parsing the info for
Socket::Constants
...So, I'm not sure what's causing it, so I'll check later. My doc site is generated locally, and pushed to GitHub, while ruby-loco is totally in the cloud (but I run locally for testing).
Maybe this make a bit more sense, and thanks, Greg
Aside: MJIT seems to consistently report
Of the 8, 7 are SEGV's...
cc777d0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Found the issue. A build runs at 3:00 my time (Noon JST). In the morning I update my repo and then the doc site. To generate the Socket constants, I run
ruby mkconstants.rb -o constdefs.c
in the repo. So,mkconstants.rb
was the version from this commit, but the build was several hours (and commits) behind. QED...