You can write macros that have varargs,
Dumb hardware engineer question:
Why use macros when you can write a function?
___
Boston-pm mailing list
Boston-pm@mail.pm.org
http://mail.pm.org/mailman/listinfo/boston-pm
On Wed, Apr 17, 2013 at 09:29:34AM -0500, Greg London wrote:
You can write macros that have varargs,
Dumb hardware engineer question:
Why use macros when you can write a function?
In this very simple case it makes no significant difference.
--
David Cantrell | top google result for internet
On Wed, Apr 17, 2013 at 09:29:34AM -0500, Greg London wrote:
You can write macros that have varargs,
Dumb hardware engineer question:
Why use macros when you can write a function?
In this very simple case it makes no significant difference.
When WOULD it make a difference?
The only thing
On Wed, Apr 17, 2013 at 09:38:08AM -0500, Greg London wrote:
On Wed, Apr 17, 2013 at 09:29:34AM -0500, Greg London wrote:
You can write macros that have varargs,
Dumb hardware engineer question:
Why use macros when you can write a function?
In this very simple case it makes no
Ben Tilly bti...@gmail.com writes:
On Wed, Apr 17, 2013 at 7:29 AM, Greg London em...@greglondon.com wrote:
Why use macros when you can write a function?
Lisp weenie answer: because the arguments to functions may produce
side effects, while with macros you can control that. Of course the
On Wed, Apr 17, 2013 at 8:51 AM, Mike Small sma...@panix.com wrote:
Ben Tilly bti...@gmail.com writes:
On Wed, Apr 17, 2013 at 7:29 AM, Greg London em...@greglondon.com wrote:
Why use macros when you can write a function?
Lisp weenie answer: because the arguments to functions may produce
Hi all,
On Wed, 17 Apr 2013 15:53:36 +0100
David Cantrell da...@cantrell.org.uk wrote:
On Wed, Apr 17, 2013 at 09:38:08AM -0500, Greg London wrote:
On Wed, Apr 17, 2013 at 09:29:34AM -0500, Greg London wrote:
You can write macros that have varargs,
Dumb hardware engineer question:
Ben Tilly bti...@gmail.com writes:
...
If I have a vector of type Foo, then an iterator over it has type
std::vector Foo ::iterator.
If I have a map from Foo to Bar, then an iterator over it has type
std::map Foo, Bar ::iterator.
If I have a set of things of type Foo, then an iterator over
Greg London writes:
Greg
At the risk of giving you useless information which could lead to more
useless information, are you genuinely executing on a platform where C++ is
your only option, or is it simply that C++ seemed like the only obvious
choice? If you have a compiler that targets the