I wasn't trying to say that it was specific to strings, I was saying that
it is not specific to I/O, which the name would seem to indicate...
and it keeps getting brought up as something that should be used for basic
mutable string operations.
On Sunday, May 3, 2015 at 3:20:43 PM UTC-4, Tamas
On Sunday, May 3, 2015 at 6:10:00 PM UTC-4, Kevin Squire wrote:
One thing I was confused about when I first started using Julia was that
things that are done with strings in other languages are often done
directly with IO objects in Julia.
For example, consider that, in Python, most
I think you misunderstand: IOBuffer is suggested not for mutable string
operations in general, but only for efficient concatenation of many
strings.
Best,
Tamas
On Mon, May 04 2015, Scott Jones scott.paul.jo...@gmail.com wrote:
I wasn't trying to say that it was specific to strings, I was
I have used userimg.jl to build sysimg including a file with my function,
which I know takes a long time to compile (i.e. execute the first time).
This worked for some time and then mysteriously stopped - despite loading
this sysimg, the first execution of this function takes ages. I assume
On May 4, 2015, at 3:21 AM, Tamas Papp tkp...@gmail.com wrote:
I think you misunderstand: IOBuffer is suggested not for mutable string
operations in general, but only for efficient concatenation of many
strings.
Best,
Tamas
I don’t think that I misunderstood - it’s that using
Hi,
I wrote a function to map contents of composite types to vectors and
dictionaries:
repack{S}(v::Vector, ::Type{S}) = S(v...)
repack{S}(d::Dict, ::Type{S}) = S([get(error,d,f) for f in fieldnames(S)]...)
repack{S,T}(x::S, ::Type{Vector{T}}) = T[getfield(x,f) for f in fieldnames(S)]
On Mon, May 04 2015, Scott Jones scott.paul.jo...@gmail.com wrote:
On May 4, 2015, at 3:21 AM, Tamas Papp tkp...@gmail.com wrote:
I think you misunderstand: IOBuffer is suggested not for mutable string
operations in general, but only for efficient concatenation of many
strings.
Best,
Hi Kevin,
Thanks! I will add this to my ToDo lists :)
Regards,
Ronan
Em domingo, 3 de maio de 2015 19:14:00 UTC-3, Kevin Squire escreveu:
Hi Ronan,
Looks like an interesting package!
One minor suggestion: if you ever plan to make this an actual Julia
package, it would be good to name
Thanks for your work!
But why after I build it, it shows 0.3.9-pre+6?
On Friday, May 1, 2015 at 7:49:03 PM UTC+2, Tony Kelman wrote:
Hello all! The latest bugfix release of the 0.3.x Julia line has been
released. Binaries are available from the usual place
On May 4, 2015, at 7:56 AM, Tamas Papp tkp...@gmail.com wrote:
On Mon, May 04 2015, Scott Jones scott.paul.jo...@gmail.com wrote:
On May 4, 2015, at 3:21 AM, Tamas Papp tkp...@gmail.com wrote:
I think you misunderstand: IOBuffer is suggested not for mutable string
operations in
On Monday, May 4, 2015 at 7:28:28 AM UTC-5, Sisyphuss wrote:
Thanks for your work!
But why after I build it, it shows 0.3.9-pre+6?
If you are building from a git checkout directly from the release-0.3
branch, there are commits made immediately after the tag--for instance, to
increment the
This is why I don't like Python. Imagining when doing a scalar product, we
have to write `numpy.dot(a,b)`, It's awful!
And this notation won't work on operator overload.
On Wednesday, April 29, 2015 at 8:49:34 PM UTC+2, Stefan Karpinski wrote:
This scheme seems overly focused on
You could qualify S and T so that the compiler knows they aren’t Vector and
Dict, but are instead subtypes of some custom type of your own. In general,
the translation T([getfield(x,f) for f in 1:nfields(T)]...) is not
guaranteed to return the same object / value for all types anyways.
On Mon,
I've been trying to get JavaCall to work with the latest Julia master,
after the Tuplecalypse. I am getting a method ambiguity warning, and am a
bit confused by the suggested fix. Any help appreciated.
so the warning message says:
Warning: New definition
Folks, I am a Julia newcomer. I need to get current time. And now() works
just fine. But it returns a local time. And I need GMT time.
I got to documentation. It gave me very nice description:
now() → DateTime
Returns a DateTime corresponding to the user’s system time including the
system
Yeah, the second one is a little obscure, because of a couple of issues.
-`UTC` isn't exported from the Dates module, so you'll have to use
`Dates.UTC`
-`UTC` is a *type* instead of a instance of a type, (that's what the
::Type{UTC} means)
So the correct way to call this is
now(Dates.UTC)
On
Le lundi 04 mai 2015 à 11:02 -0700, Irving Rabin a écrit :
Folks, I am a Julia newcomer. I need to get current time. And now()
works just fine. But it returns a local time. And I need GMT time.
I got to documentation. It gave me very nice description:
now() → DateTime
I would suggest that this topic is moved over to a github issue by those that
are interested/participating.
I have observed a highly useful pattern of communication over the last year on
this list: someone brings up a topic that relates to a design
question/improvement of julia, there is a
Based on recent discussions, it seems that at least some people would like
the option to have unqualified use of a function name dispatch across
modules when the argument on which the function is called unambiguously
specifies an exported method. While Julia doesn't do this automatically,
one
David: good call, but on string concatenation specifically an issue was
already opened: https://github.com/JuliaLang/julia/issues/11030
On Monday, May 4, 2015 at 12:00:00 PM UTC-7, David Anthoff wrote:
I would suggest that this topic is moved over to a github issue by those
that are
Le lundi 04 mai 2015 à 20:09 +0200, Milan Bouchet-Valat a écrit :
Le lundi 04 mai 2015 à 11:02 -0700, Irving Rabin a écrit :
Folks, I am a Julia newcomer. I need to get current time. And now()
works just fine. But it returns a local time. And I need GMT time.
I got to documentation. It
Cool. The fact that you can do this implies that the current behavior is in
a sense more fundamental than merging since you can implement merging like
this, whereas if merging were the default, it's unclear how you would
recover the current behavior.
On Mon, May 4, 2015 at 3:08 PM, David Gold
Hi David,
Thanks for the sample code. I must admit this is not exactly what *I* am
looking for, but it is very interesting.
I am not particularly good with macros code that deal with symbols... so
this is very appreciated. I think there are enough elements here to
achieve the effect I am
Yes:
@defVar(m, x[ i = 1 : length(z) ] = z[i] )
This error message is really opaque, though; I’ve updated it on JuMP master
to be a little more informative.
-Joey
On Monday, May 4, 2015 at 6:23:45 PM UTC-4, Alexandros Fakos wrote:
Hi,
z is a variable in the workspace
Ideally I would
Hi,
z is a variable in the workspace
Ideally I would like to define variable x for the optimization problem like:
@defVar(m, x[ 1 : length(z) ] = z )
which gives the error
ERROR: `Variable` has no method matching Variable(::Model,
::Array{Float64,1}, ::Float64, ::Symbol, ::ASCIIString,
Neat, merging under the control of the user who knows they mean to do so is
a great idea.
Cheers
Lex
@Stefan: Based on my experiences implementing this feature, I have to
agree. In particular, I imagine that any attempt to include an un-merge
feature would run into a lot of trouble from the fact that function names
are constants. Once you've merged methods into a function 'f', they are
there
Might be GnuTLS.jl, on which Requests has a dependency on and loads a C
library.
On Mon, May 4, 2015 at 12:39 PM, George Thomas gmt.gtho...@gmail.com
wrote:
Hi -
I get a server segmentation fault immediately as I connect to the server
via URL `localhost:8000/hello/name/` from a browser
I don't think this is related, but its usually a bad idea to set
LD_LIBRARY_PATH and an even worse idea to put /usr/local/lib, /usr/lib,
/usr/local/lib64, /usr/lib64, /lib64, or any other default system location
in that variable.
On Mon, May 4, 2015 at 4:03 PM George Thomas gmt.gtho...@gmail.com
I agree with Stefan. The default behavior should be very conservative, and
any niceties (like merging) should be optional features/extensions. Thanks
David... I'll check this out.
On Monday, May 4, 2015 at 3:36:28 PM UTC-4, Stefan Karpinski wrote:
Cool. The fact that you can do this implies
IIRC, the only C library used by the web stack is http-parser
https://github.com/joyent/http-parser. Given that LD_LIBRARY_PATH has all
those system library locations in it, it's entirely possible that you're
loading the wrong version of that library and it's causing the segfault, so
maybe
Hi -
I get a server segmentation fault immediately as I connect to the server
via URL `localhost:8000/hello/name/` from a browser (firefox or chrome). I
initiate the server listening mode via `julia example/Hello.jl' that is
included in the Morsel package (installed via Pkg.add(Morsel).
This
Thank you so much Joey!
Alex
On Monday, May 4, 2015 at 9:08:23 PM UTC-4, Joey Huchette wrote:
Yes:
@defVar(m, x[ i = 1 : length(z) ] = z[i] )
This error message is really opaque, though; I’ve updated it on JuMP
master to be a little more informative.
-Joey
On Monday, May 4, 2015 at
33 matches
Mail list logo
