Actually, your suggestion would actually be quite nice for quit print
debugging. often I doe want to just do: `println(x)`. What about:
- print!, println! - comma separated list of values, converted to a string
- printf!, printfln! - wraps fmt!
Simples.
~Brendan
On 14/07/2013, at 12:39 PM,
The C printf way is very primative .. no new languages have used it in
ages and even C++ tried to replace it with cout and overloading .
I prefer the Java /C# way which is best from a coding simplicity and
safety point of view but can handle different cases.
stream.Write ( str1 + str2
.. no new languages have used it in ages
http://golang.org/pkg/fmt/
On 14/07/2013, at 4:29 PM, Bennie Kloosteman bkloo...@gmail.com wrote:
The C printf way is very primative .. no new languages have used it in
ages and even C++ tried to replace it with cout and overloading .
I
Le 14/07/2013 03:39, Jack Moffitt a écrit :
I propose instead:
1) Do away with the formatting stuff as the default. print!() and
println!() should just take a variable number of arguments, and each
one should be printed in its default string representation with a
space between each one. This is
I think Jack's proposal is fine, but as Bennie notes I think it's still
worth discussing whether C#-style formatting would be a better fit for us
than C-style formatting.
I'm a fan of sticking with the fmt! style
Patrick mentions that fmt! currently requires a heap allocation to work, is
this a
On Sun, Jul 14, 2013 at 12:49 PM, Benjamin Striegel
ben.strie...@gmail.com wrote:
I think Jack's proposal is fine, but as Bennie notes I think it's still
worth discussing whether C#-style formatting would be a better fit for us
than C-style formatting.
I'm a fan of sticking with the fmt!
On Sun, Jul 14, 2013 at 2:29 AM, Bennie Kloosteman bkloo...@gmail.com wrote:
The C printf way is very primative .. no new languages have used it in
ages and even C++ tried to replace it with cout and overloading .
Scala, Go and D have compile-time checked, type-safe format strings for I/O.
On 07/13/2013 10:39 PM, Jack Moffitt wrote:
1) Do away with the formatting stuff as the default. print!() and
println!() should just take a variable number of arguments, and each
one should be printed in its default string representation with a
space between each one. This is how Clojure's (and
On Sun, Jul 14, 2013 at 10:09 AM, Daniel Micay danielmi...@gmail.comwrote:
Scala, Go and D have compile-time checked, type-safe format strings for
I/O.
Unless I am missing something, Go does not check format strings at compile
time.
--
Ziad
___
On Sun, Jul 14, 2013 at 4:25 PM, Ziad Hatahet hata...@gmail.com wrote:
On Sun, Jul 14, 2013 at 10:09 AM, Daniel Micay danielmi...@gmail.com
wrote:
Scala, Go and D have compile-time checked, type-safe format strings for
I/O.
Unless I am missing something, Go does not check format strings
On Sunday, July 14, 2013, Benjamin Striegel wrote:
I think Jack's proposal is fine, but as Bennie notes I think it's still
worth discussing whether C#-style formatting would be a better fit for us
than C-style formatting.
C# style formatting has the (dis?)advantage that it is possible to
On Sun, Jul 14, 2013 at 5:06 PM, Steven Ashley ste...@ashley.net.nz wrote:
On Sunday, July 14, 2013, Benjamin Striegel wrote:
I think Jack's proposal is fine, but as Bennie notes I think it's still
worth discussing whether C#-style formatting would be a better fit for us
than C-style
On 13-07-14 10:16 AM, Daniel Micay wrote:
Without format strings as the primary way to do output, I think we'll
fall down really short on the ability to do internationalization.
I agree. I18n requires the ability to switch around parameter-order
substantially across a large-ish
13 matches
Mail list logo
