summaryrefslogtreecommitdiff
path: root/win32/fcrypt.c
Commit message (Collapse)AuthorAgeFilesLines
* Omnibus removal of register declarationsKarl Williamson2012-08-181-9/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This removes most register declarations in C code (and accompanying documentation) in the Perl core. Retained are those in the ext directory, Configure, and those that are associated with assembly language. See: http://stackoverflow.com/questions/314994/whats-a-good-example-of-register-variable-usage-in-c which says, in part: There is no good example of register usage when using modern compilers (read: last 10+ years) because it almost never does any good and can do some bad. When you use register, you are telling the compiler "I know how to optimize my code better than you do" which is almost never the case. One of three things can happen when you use register: The compiler ignores it, this is most likely. In this case the only harm is that you cannot take the address of the variable in the code. The compiler honors your request and as a result the code runs slower. The compiler honors your request and the code runs faster, this is the least likely scenario. Even if one compiler produces better code when you use register, there is no reason to believe another will do the same. If you have some critical code that the compiler is not optimizing well enough your best bet is probably to use assembler for that part anyway but of course do the appropriate profiling to verify the generated code is really a problem first.
* The Borland Chainsaw MassacreSteve Hay2011-09-101-4/+0
| | | | | Remove support for the Borland C++ compiler on Win32, as agreed here: http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2011-09/msg00034.html
* Silence some more Borland compiler warningsSteve Hay2006-08-301-0/+4
| | | | | | | | | | | (See: http://www.nntp.perl.org/group/perl.daily-build.reports/40471) - Change the cryptic pragma warn strings into numbers that are more easily recognized, and add a new one (8027). - Add a similar pragma warn line to fcrypt.c, which doesn't use win32.h. p4raw-id: //depot/perl@28769
* Silence bcc32 compiler warnings from win32/fcrypt.c (almost)Steve Hay2005-06-231-36/+37
| | | | | | | | It still whines about 'in' and 'b' being assigned values that are never used on lines 348 and 505 respectively (as side effects of the calls to c2l and l2c respectively), but I'm not sure how to shut them up. p4raw-id: //depot/perl@24947
* Include fcrypt.c for crypt() on WindowsSteve Hay2003-08-141-0/+578
Message-ID: <3F3B9F14.4040609@uk.radan.com> (Sarathy okayed the idea.) p4raw-id: //depot/perl@20702