similar to: Underscores and Fortran code

good evening all, i upgraded my last samba 2.2.7a (dog2) this afternoon and have run into problems. first, the setup: windows 2000 clients three sites on three seperate subnets connected by t1 through routers. each site has a samba server that authenticates the users on its subnet. the workgroup name for each server is dognet. /etc/passwd, /etc/group, and smbpasswd are synced up manually.

Full_Name: Manikandan Narayanan Version: 2.8.1 OS: linux-gnu Submission from: (NULL) (155.91.28.231) Hi R-folks, I have two three-line text files: tst1, tst2 (they are the same except that the second line is longer in tst1; see cat() cmds below). read.table is only able to read the 3rd line in tst1, however reads tst2 correctly as shown below. This happens both in R 2.5.1 (windows) and R

hi, i am looking for a solution whereupon calling myEntityObject.to_xml does not convert my attributes containing underscores into hyphens. at the moment an attribute named "my_own_attribute" is converted into <my-own-attribute>. does anybody have an idea how to change that and have to_xml generate <my_own_attribute> thanks ciao robertj -- Posted via

Are there technical reasons that package names cannot be snake case? This seems to be enforced by `.standard_regexps()$valid_package_name` which currently returns "[[:alpha:]][[:alnum:].]*[[:alnum:]]" Is there any technical reason this couldn't be altered to accept `_` as well, e.g. "[[:alpha:]][[:alnum:]._]*[[:alnum:]]" I realize that historically `_` has not

Hi folks, currently I'm running Dovecot 1.2.1. Compiled from source on Fedora 10 Linux 32 Bit (all patches). Clients are Pine 4.64, Thunderbird 2.0.0.22 and Mutt 1.5.20 (using "=b" for server-side searching). When a message contains the text "under_score" and I let the server search for it, Dovecot does not find it in messages with a Content-Transfer-Encoding of

Hello In a component, I was trying to do: $bar = "lets make a new string with $name_$foo in it." however the "$name_" fails to appear in the resulting string: "lets make a new string with valueOfFoo in it." Is there something special about $name_ here? If I replace the underscore with a dash (... $name-$foo ... ) it works fine. thanks Jesse Jesse

When using Textpattern with PHP Markdown Extra there is a problem with the textpattern tags. Tags like <txp:image id="42" /> are parsed, but tags like <txp:site_name /> that have an underscore are not. Any ideas how to deal with this? Thanks list, -- Peter Sinn peter.sinn at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi all, I've just started using the Friedrich Leisch's Sweave package to generate LaTeX reports with results of my analyses embedded as required. I've encountered a bit of a problem though in the processing of the resulting *.tex file that is as far as I can tell, down to the fact that my variable names have underscores ('_') in their names. The relevant section of code

Greetings: I am writing a basic accounting module for an app. Rather unfortunately the name "transactions" is a reserved term in Rails (being the only accounting term trully representational of a financial transaction). I am left to come up with other names. One such name was f_transaction. This worked on the DB level, but I noticed that the Model name dropped the underscore, thus

Dear R People: In the DASL library, there is a story about hot dogs. Here are the data: Beef 186 495 Beef 181 477 Beef 176 425 Beef 149 322 Beef 184 482 Beef 190 587 Beef 158 370 Beef 139 322 Beef 175 479 Beef 148 375 Beef 152 330 Beef 111 300 Beef 141 386 Beef 153 401 Beef 190 645 Beef 157 440 Beef 131 317 Beef 149 319 Beef 135 298 Beef 132 253 Meat 173 458 Meat 191 506 Meat 182 473 Meat 190

I'm having problems with functions starting with underscores '_foo' <- function(x) {1} seems to work but I can't assign an attribute to this function attr('_foo', 'bar') <- 'pow' Any way of doing this? This is for a C++ -> R wrapping system so I'd like to keep the C++ names which start with underscores. (please cc: responses to me

On 09/08/2019 4:37 p.m., Gabriel Becker wrote: > Duncan, > > > On Fri, Aug 9, 2019 at 1:17 PM Duncan Murdoch <murdoch.duncan at gmail.com > <mailto:murdoch.duncan at gmail.com>> wrote: > > On 09/08/2019 2:41 p.m., Gabriel Becker wrote: > > Note that this proposal would make mypackage_2.3.1 a valid > *package name*, > > whose

I sent this earlier under with the subject "artificial sugar causes cancer" and I think some spam filters ate it. Here it is again: ====================================== All, If you look at http://rubyforge.org/tracker/index.php?func=detail&aid=6760&group_id=797&atid=3149 you''ll see that Chad (the submitter) found the source of the bug. Unfortunately, the source

Won't it be better to have a convention that allows lowercase, dash, underscore and dot as only valid characters for new package names and keep the ancient format validation scheme for older package names? This could be implemented by a single function, taking a strictNaming_b_1 parameter which defaults to true. Easy to use, and compliance results will vary according to the parameter value,

Martin, Thank you for discussing this amongst R-core and for detailing the R-core discussion here. Some specific examples where having underscores available would have been useful. 1. My primerTree package (2013) was originally primer_tree, but I had to change the name to camelCase to comply with the check requirements. Using camelCase in the package name makes reading code jarring, as the

Hi all, I've noticed that OpenSSH 7.7 adds stricter validation of user environment strings from authorized_keys files. While strict validation is a good thing from a security perspective, this new change specifically blocks underscores which are common to include in a user environment string. This results in the key being rejected outright. Including underscores in a user environment is a

I do not follow you Gabriel. Package name must not use digit numbers. Tarbal will use them, taken from the DESCRIPTION file, version field. That's why I consider the weird case name you presented as irrelevant, and not to be considered. Le ven. 9 ao?t 2019 ? 20:41, Gabriel Becker <gabembecker at gmail.com> a ?crit : > > > On Fri, Aug 9, 2019 at 11:05 AM neonira Arinoem

Naming policies are always tricky. The one proposed by Hadley, as the one proposed by Google, are usable but not optimal according to most common needs, that are 1. Name a package 2. Name a class 3. Name a function 4. Name a parameter of a function 5. Name a variable My approach is the following 1. Package names should be made of lowercase characters, dash, dot and underscore 2. Class names

Hello, After much tinkering I managed to build packages using the 64bit version of R with the help of hints from http://www.murdoch-sutherland.com/Rtools/ and http://www.stats.ox.ac.uk/~ripley/Win64/W64porting.html and R-admin Manual. But a hack was required, and this seems to be related to a comment about underscores at the end of the second reference above (but this comment is about FUTURE

Hi List, I'm trying to build R-2.0.1 on and AMD64/Linux (Suse 9.1) and I get the following error while running the configure script. ... checking for dummy main to link with Fortran libraries... none checking for Fortran name-mangling scheme... lower case, underscore, extra underscore checking whether g77 appens underscores to external names... yes checking whether mixed C/Fortran code can