Saturday, February 14, 2015

Digest for comp.lang.c++@googlegroups.com - 12 updates in 5 topics

Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo>: Feb 14 12:35AM -0500

> your example program even to a string literal, which may
> reside in read-only memory)?
 
> Best regards, Jens
 
There can be different implementations of operator>>. For example, one might
want to use it to try to extract from the stream and throw away as many
characters as the length of the C string pointed to by the const char* parameter
(in the OP's example specifically, 3 characters). I am curious about the real
intent, too, though.
 
-Pavel
"Norman J. Goldstein" <normvcr@telus.net>: Feb 14 09:23AM -0800

On 02/13/2015 09:35 PM, Pavel wrote:
> (in the OP's example specifically, 3 characters). I am curious about the real
> intent, too, though.
 
> -Pavel
 
operator>>( istream&,const char* ) succeeds if the extracted characters
exactly match the supplied const char*. Leading white space is ignored.
I find this a convenient way to help parse a file.
jt@toerring.de (Jens Thoms Toerring): Feb 14 08:05PM

> operator>>( istream&,const char* ) succeeds if the extracted characters
> exactly match the supplied const char*. Leading white space is ignored.
> I find this a convenient way to help parse a file.
 
Thank you for the clarification. It's the one hazards of
operator overloading I see that different people may have
different ideas about what it's meant to do...
 
Best regards, Jens
--
\ Jens Thoms Toerring ___ jt@toerring.de
\__________________________ http://toerring.de
Jorgen Grahn <grahn+nntp@snipabacken.se>: Feb 14 11:02PM

On Sat, 2015-02-14, Jens Thoms Toerring wrote:
 
> Thank you for the clarification. It's the one hazards of
> operator overloading I see that different people may have
> different ideas about what it's meant to do...
 
People complain too much about operator overloading sometimes ... but
here I have to admit I don't like it. If I see "is >> foo", I'm going
to assume it follows the standard pattern -- because a std::istream is
involved, not just because of the ">>".
 
/Jorgen
 
--
// Jorgen Grahn <grahn@ Oo o. . .
\X/ snipabacken.se> O o .
Robert Wessel <robertwessel2@yahoo.com>: Feb 14 01:08AM -0600

On Wed, 11 Feb 2015 19:42:33 GMT, scott@slp53.sl.home (Scott Lurndal)
wrote:
 
>>> switch to being a FORTRAN programmer and punch my code into cards.
 
>>Modern Fortran is well supported on Solaris :)
 
>Although card readers never were supported on Solaris :-)
 
 
Perhaps not explicitly by the OS, but a number of moderate speed card
readers with serial output existed. In particular readers capable of
reading mark-sense cards (remember the ones where you used a pencil to
darken the "holes" in the cards), were fairly widely used.
 
Many of those would, at least in basic mode, just read a card, output
the 80 (or 40, or 64 or...) characters, and slap on a CR (or the
like), and go on to the next card. Not really a lot that needed
support in the OS. Various readers had support for some sort of
binary/transparent mode, too.
 
One of my friends in HS used one of those to handle the voting for
homecoming king and queen, but it was not on Solaris. Although
Solaris actually didn't exist at the time (its predecessor, the BSD
based SunOS, did, of course).
Jorgen Grahn <grahn+nntp@snipabacken.se>: Feb 14 08:07PM

On Thu, 2015-02-12, Cholo Lennon wrote:
> On 02/12/2015 04:21 PM, Ian Collins wrote:
>> Cholo Lennon wrote:
...
> code has to compile well with all of them (Luckily VC++ 2003 is almost
> dead in our production base). I love C++ but I can tell you, is not as
> easy as lots of people love to say.
 
I'm a Unix guy, but can the VC++ 2003/2005 part be the source of the
confusion here? Wasn't it just a few years ago that Microsoft decided
to implement recent C++ standards properly?
 
If not all of your compilers are C++98-capable, then yes, portability
will be a daily problem.
 
(gcc 3.4.x is also a decade old. I remember being rather happy with
it, but I've had to update my code a few times because gcc let some
things through which turned out to be properly flagged as compile-time
errors in later versions.)
 
/Jorgen
 
--
// Jorgen Grahn <grahn@ Oo o. . .
\X/ snipabacken.se> O o .
Christopher Pisz <nospam@notanaddress.com>: Feb 13 06:09PM -0600

On 2/13/2015 1:39 PM, DSF wrote:
> DSF
> "'Later' is the beginning of what's not to be."
> D.S. Fiscus
 
I am not sure on the details of their various editions. They keep adding
and subtracting more every year. It is annoying to no end.
 
Unless you are doing something with a team or business, professional
version is adequate in most cases.
 
Community edition looks like it just have a bunch of crap you get for
free anyway built into it, from what I am reading. Git extensions and
the like. You'd still have to pay for Azure and all that jazz (which is
a rip off imo.)
 
Adobe's subscription model is a joke. I worked out the cost and it would
be almost 5x as expensive given my frequency of upgrading photoshop.
 
I hate subscription models in general. If I buy it, I want it in a box
on my shelf, licensed for my lifetime. They are all out to squeeze more
money out of Joe User. Businesses already subscribe to MSDN anyway and
have access to whatever they like.
 
At any rate. If you are looking for a new version of visual studio, I'd
say now is not the time to buy, as MSVS 2014 is very near to release.
Christopher Pisz <nospam@notanaddress.com>: Feb 13 06:12PM -0600

On 2/13/2015 6:09 PM, Christopher Pisz wrote:
> have access to whatever they like.
 
> At any rate. If you are looking for a new version of visual studio, I'd
> say now is not the time to buy, as MSVS 2014 is very near to release.
 
Hrm, well I looked it up and evidently it is free.
So,...umm download it and find out the answers to all your questions :P
DSF <notavalid@address.here>: Feb 14 01:13AM -0500

On Fri, 13 Feb 2015 18:09:38 -0600, Christopher Pisz
>on my shelf, licensed for my lifetime. They are all out to squeeze more
>money out of Joe User. Businesses already subscribe to MSDN anyway and
>have access to whatever they like.
 
I *HATE* subscription models. Not only for the reasons you mention,
but also because you have no choice when it comes to upgrading. If
they've removed a feature you use often (but maybe most users don't),
or changed how every operation works because they've discovered a
"better" way - Tough Luck! You can't fall back on your previous
version because it doesn't exist.
 
 
>At any rate. If you are looking for a new version of visual studio, I'd
>say now is not the time to buy, as MSVS 2014 is very near to release.
 
As you noted in your follow-up post, the Community version is free.
Hence my disbelief that it is identical to the Pro version, save for
licensing.
 
I already have downloaded it, but I am having VirtualBox problems. I
will not install it into my main system. "C:" is not my programming
drive, "E:" is. The last time I installed a version of VS Express, I
set every path I could change to E:\etc... It installed about 20% of
itself on E: and the other 80% in C:\Windows and C:\Program Files. And
after uninstallation, it left so much of itself on C: that I wound up
deleting/reinstalling Windows to get rid of the bloat.
 
By the way, I guess that's another reason I've stuck with the
Borland compiler for so long. It stores very little in the Windows
directory and, because of that, is fairly portable.
 
Thanks again,
DSF
"'Later' is the beginning of what's not to be."
D.S. Fiscus
David Brown <david.brown@hesbynett.no>: Feb 14 01:40PM +0100

On 14/02/15 07:13, DSF wrote:
> itself on E: and the other 80% in C:\Windows and C:\Program Files. And
> after uninstallation, it left so much of itself on C: that I wound up
> deleting/reinstalling Windows to get rid of the bloat.
 
It is software from MS - you didn't think it would follow the rules for
a Windows program did you? MS software often has trouble with a setup
that is something other than the standard - everything on C:, Windows in
C:\Windows, programs always in C:\Program Files (good luck if you use a
different language version of windows with a different folder name
here!), latest updates on everything, and so on. And while other
software gets installed in its own folders, MS has the "right" to stomp
all over Windows with whatever it wants to put there, changing DLL's,
adding stuff to your path, changing your defaults.
 
 
Vlad from Moscow <vlad.moscow@mail.ru>: Feb 14 02:16AM -0800

Maybe it is interesting what you are discussing but my question aboun C/C++ journals.:)
 
On Sunday, February 8, 2015 at 11:26:00 PM UTC+3, Martijn Lievaart wrote:
izmirli <nanoturko@gmail.com>: Feb 14 01:03AM -0800

look at the books ;
Real-Time_C_Efficient_Object Oriented_and_Template_Microcontroller_Programming.Chris Kormanyos
Interfacing with C++ Jayantha Katupitiya Kim Bentley.
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to comp.lang.c+++unsubscribe@googlegroups.com.
Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)