search for: camelcase

Hi everyone, I have a code style question: should full test programs (.c,.cpp files) use the documented CamelCase from http://llvm.org/docs/CodingStandards.html#name-types-functions-variables-and-enumerators-properly or instead use lower_with_underscores as I've been told the .ll lit test files should use? I see both in existing files, and in particular for projects/compiler-rt I cannot blindly follow the...

...r project" "hello world" "something else" > toupper(z) [1] "R PROJECT" "HELLO WORLD" "SOMETHING ELSE" I saw the tocamel() function in 'rapport', but it doesn't do what I want to achieve as it actually proceeds to camelCase/CamelCase the strings: > tocamel(z) [1] "RProject" "helloWorld" "somethingElse" But how should I proceed to obtain Camel Case? Here's what I'd like to get: c('R Project', 'Hello World', 'Something Else') Regards, Liviu -...

Hi there, At the end of last week we saw a number of commits go in that were camelCasing batches of MCStreamer::Emit* and AsmPrinter::Emit* functions. For example: - https://reviews.llvm.org/rG549b436beb4129854e729a3e1398f03429149691 - https://reviews.llvm.org/rGa55daa146166353236aa528546397226bee9363b - https://reviews.llvm.org/rG0bc77a0f0d1606520c7ad0ea72c434661786a956 Unfortunately all these

...specially if indeed there is going to be a big renaming push and this would be a continuous thing. Cheers, /Ties ________________________________________ From: Michael Kruse <llvmdev at meinersbur.de> Sent: 17 February 2020 21:16 To: Ties Stuij Cc: llvm-dev Subject: Re: [llvm-dev] amount of camelCase refactoring causing some downstream overhead My understanding is that LLVM's general policy is to not let downstream slow down upstream development. The C++ API explicitly unstable. Note that we are even considering renaming variables globally: https://lists.llvm.org/pipermail/llvm-dev/2019-S...

...be a discussion on the pain of such a transition, or how to get from here to there, but rather, if there is a better place to be. My arguments for the change are: 1. No other popular C++ coding style uses capitalized variable names. For instance here are other popular C++ conventions that use camelCase: http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml http://www.c-xx.com/ccc/ccc.php http://geosoft.no/development/cppstyle.html And, of course, the all-lower-case conventions (e.g. C++ ARM) don’t capitalize variable names. In addition, all the common C derived languages don’...

...> > > > Cheers, > > /Ties > > > > ________________________________________ > > From: Michael Kruse <llvmdev at meinersbur.de> > > Sent: 17 February 2020 21:16 > > To: Ties Stuij > > Cc: llvm-dev > > Subject: Re: [llvm-dev] amount of camelCase refactoring causing some > downstream overhead > > > > My understanding is that LLVM's general policy is to not let > > downstream slow down upstream development. The C++ API explicitly > > unstable. > > > > Note that we are even considering renaming varia...

Hi all, I''ve created and submitted a patch to resolve an issue I had while attempting to meet the OpenSocial API specifications, which dictates that the xml output have tags formatted as lower camelcase (as opposed to upper camelcase, which is currently the only option). With this patch, simply passing :camelize => true still begets the current behavior, but you can now enable lower camel-casing by passing :camelize => :lower. Please have a look if you get the chance - I appreciate your feed...

Hello, I did a fresh install of ruby182 and gem rails --include-dependencies Now when I do: rails receipts cd receipts ruby script\generate scaffold receipt receipt rails does not create the views or controller. What can I do? Thanks Frank

...gt; So: > > > > - Local variables and formal parameters should be lower_case, with > > one exception: Variables/parameters that have lambda/function > > type should follow the function-name spelling rules. > > "lower_case" is a pretty drastic change from CamelCase and camelCase. > So far the only argument for it I've seen is, "lldb uses it all over the > place." Having one subproject drive the standard for everything else > seems backward. It's certainly possible I missed other opinions on this > though. You have. For example...

...and progressing to a >connotation-free reading of language. But language is never free of >connotations, even if you and I don't see those connotations. > >I'm not seeing the change as a huge inconvenience, and this argument is >not much different than the head-butting over camelCase vs CamelCase. >Some people care deeply, others see little value in the change so why >bother; IMO it makes the people who care deeply happier, and it doesn't >particularly interfere with my work or cost me more than a bit of one >time adaptation. Thus overall it is a plus for the c...

...rsday, February 20, 2020 1:16 PM To: Robinson, Paul <paul.robinson at sony.com> Cc: Philip Reames <listmail at philipreames.com>; Eric Christopher <echristo at gmail.com>; llvm-dev at lists.llvm.org; Valentin Churavy <v.churavy at gmail.com> Subject: Re: [llvm-dev] amount of camelCase refactoring causing some downstream overhead On Wed, Feb 19, 2020 at 12:10 PM Robinson, Paul via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote: Hi Philip, I think you might be reading more into the suggestion/discussion than is actually there. *...

.... Where are the drop table calls? I couldn''t find them. My more immediate problem so far is that I''m getting this error: /Users/pupeno/Projects/rails/rails/activerecord/lib/active_record/connection_adapters/abstract_adapter.rb:210:in `log'': Mysql::Error: Table ''camelcase'' already exists: CREATE TABLE `CamelCase` (`id` int(11) DEFAULT NULL auto_increment PRIMARY KEY, `name` varchar(255)) ENGINE=InnoDB (ActiveRecord::StatementInvalid) It started happening when I was playing with adding and not adding value. The whole output is bellow. The puzzling part is t...

[I hope the repost isnt'' "minded". Following the advice of another thread I''ve changed the subject to a question. If I haven''t included important info, please ask. My database is being unduly killed. Jodi] Cheers on-the-Rails-ers, Before I start, I''ve read the ActiveRecord docs on eager loading, but for the life of me, I can''t seem to get

...;'name ASC'') end render :partial => ''auto_complete_for_team_name'' end and in the partial (_auto_complete_for_team_name.rhtml), I have: <ul> <% for team in @teams do -%> <li> <div class="first_line"><%=h team.name.camelcase -%></div> <div class="second_line"><%=h team.city.name.camelcase -%> - <%=h team.city.country.name.camelcase -%> </li> <% end -%> </ul> and it all works with the exception that when I select on of the items from the ajax generated...

...-dev-bounces at lists.llvm.org> On Behalf Of Philip Reames via llvm-dev Sent: Wednesday, February 19, 2020 2:07 PM To: Eric Christopher <echristo at gmail.com> Cc: llvm-dev <llvm-dev at lists.llvm.org>; Valentin Churavy <v.churavy at gmail.com> Subject: Re: [llvm-dev] amount of camelCase refactoring causing some downstream overhead Eric, I disagree. Strongly. I see the very fact we're engaging in the discussion of "just being polite" here as normalizing a proposed change in policy which has potentially profound negative consequences for the project long term. I...

...;> > /Ties >> > >> > ________________________________________ >> > From: Michael Kruse <llvmdev at meinersbur.de> >> > Sent: 17 February 2020 21:16 >> > To: Ties Stuij >> > Cc: llvm-dev >> > Subject: Re: [llvm-dev] amount of camelCase refactoring causing some >> downstream overhead >> > >> > My understanding is that LLVM's general policy is to not let >> > downstream slow down upstream development. The C++ API explicitly >> > unstable. >> > >> > Note that we are eve...

...ositive comments on the review thread. Thank you for driving this forward! -Chris > On Jul 4, 2019, at 9:50 PM, Rui Ueyama <ruiu at google.com> wrote: > > Hi all, > > I wrote a tool <https://reviews.llvm.org/D64123> to batch-rename variable names so that they are in camelCase, and I applied the tool to lld subdirectory. You can see my change at https://reviews.llvm.org/D64121 <https://reviews.llvm.org/D64121>. If you have any comments, please reply. > > If people are happy about this change, I can do the same thing for other directories including LLVM itsel...

Hi, I wonder if there''s an easy way to access the associated Model class from its Controller. Something that would allow me to write snippets like the following: class PeopleController < ApplicationController def some_method person_model_class = self.some_method_to_retrieve_the_person_model_class() end end Cheers, Marco -- Posted via

I''m creating a new rails app. The application is named BigIdea. Should I create this project using: 1. rails bigidea or 2. rails big_idea I know both will work, but just want to get off to the right start using the proper rails naming convention. Thanks! Brian -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this

Hi Rui, I’m totally positive on switching to camelCase convention. In fact I have been always uncomfortable with the current naming approach. My only suggestion/concern is that we should provide a transition path not only for the trunk code in the repository, but for eventual out-of-trunk code with implementations of custom architectures. I have curr...