Juergen Boemmels wrote:
> chartypes/usascii.c
> cc1: warnings being treated as errors
> chartypes/usascii.c:35: warning: initialization from incompatible pointer
type
> make: *** [chartypes/usascii.o] Error 1
>
> The offending line is
> &usascii_transcode_from_unicode, /* from_unicode() */
In
"Brent Dax" <[EMAIL PROTECTED]> writes:
> ...
> t/op/stringNOK 117# Failed test (t/op/string.t at line
> 1981)
> # got: 'ASCII is the same as UTF8
> # ÇÇ'
> # expected: 'ASCII is the same as UTF8
> # ASCII is the same as UTF8
> # '
> # Looks lik
Leopold Toetsch <[EMAIL PROTECTED]> writes:
> > ... t/pmc/n.t is failing for me right now, but that's
> > probably because I have an ancient libnci.so that happens to be lying
> > around. Is everyone else just skipping this test?
>
> I'm always running nci.t.
How do you do that?
On a clean check
...
t/op/stringNOK 117# Failed test (t/op/string.t at line
1981)
# got: 'ASCII is the same as UTF8
# ÇÇ'
# expected: 'ASCII is the same as UTF8
# ASCII is the same as UTF8
# '
# Looks like you failed 1 tests of 117.
t/op/stringdubious
Andy Dougherty (via RT) <[EMAIL PROTECTED]> writes:
> The following patch eliminates the following (correct!) warnings during
> the Configure process:
Thanks, applied
boe
"vcv" <[EMAIL PROTECTED]> writes:
> Granted I haven't gotten my hands dirty with the guts of parrot yet, but it
> looks good to me, and makes sense.
>
> Thanks for the fix though, it works great now :)
>
> However, it did introduce a warning (on Win32):
>
> io.ops(59) : warning C4022: 'PIO_fdop
# New Ticket Created by Steve Clark
# Please include the string: [perl #23832]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=23832 >
Attached is a patch to tidyup a couple of things in longopt.c
- there were a couple of in
Granted I haven't gotten my hands dirty with the guts of parrot yet, but it
looks good to me, and makes sense.
Thanks for the fix though, it works great now :)
However, it did introduce a warning (on Win32):
io.ops(59) : warning C4022: 'PIO_fdopen' : pointer mismatch for actual
parameter
2
---
Hello,
Nobody yet commented to my proposed change of fdopen semantics
http://groups.google.de/groups?selm=m2ptifuukf.fsf%40helium.physik.uni-kl.de
so I checked in the part.
This change mainly changes the semantics of getfd
The returned value is no longer the index in the
interpreter->piodata->tab
Dan Sugalski wrote:
>
> If we can get things nailed down for a friday release (which
> I'd really like) I propose we name the thing "Dubloon" (or
> doubloon, whichever is actually correct)
http://www.hyperdictionary.com/dictionary/doubloon
> \Doub*loon"\, n. [F. doublon, Sp. doblon. See {Double
If we can get things nailed down for a friday release (which I'd really
like) I propose we name the thing "Dubloon" (or doubloon, whichever is
actually correct)
Dan
"Vladimir Lipskiy" <[EMAIL PROTECTED]> writes:
> Seems like Juergen did apply only one of two patches which I proposed on
> 06.09.2003
> See Re: Win32 Build Issues (was Re: Linking pdump and dissassemble)
> 06.09.2003 4:40
Ooops. These were two independend patches with the same name.
Thanks appl
12 matches
Mail list logo