RE: [perl #34572] [PATCH] README.win32 instructions for nmake with ICU
i tried to build parrot on win32 yesterday. i too found the readme out of date. i didn't know how version-dependent parrot was with unicode, so i tracked down the 2.8 version of icu at ftp://ftp.software.ibm.com/software/globalization/icu/2.8 with this version installed, 'icudata.lib' is the proper name for --icushared. BTW your patch doesn't mention that you've changed versions from 2.8 to latest (currently 3.2), or update the version mentioned in the rest of the readme. if parrot runs successfully with different versions of icu (anyone?) then a patch can be applied with more specific language on installing with the versions of icu known to work, and hints on installing with unproven versions. ~jerry ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance.
RE: Numeric semantics for base pmcs
Leopold Toetsch <[EMAIL PROTECTED]> wrote: > BigNums grow on demand. It depends on value and precision. > can BigNum then start at sizeof(int)? overflow would auto-grow the BigNum to the appropriate size, and most integer math operations will keep space usage as low as possible. in fact, then int is just a degenerate case of BigNum, one that doesn't grow and throws an exception instead. or, maybe that's the case already, i should probably read the docs. ~jerry ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance.
RE: Benchmark Stuff
> > Here is the modified parrotbench script along with > > the > > new data collection script and the script to make it > > into a web page. > > > > I don't know what kind of layout/data would be > > useful > > to people so let me know if you want something else. > > > > I will update every Tuesday morning. > > I guess it helps if I share the web page to look at: > > http://perlmonk.org/~limbicregion/parrot_bench.html > good stuff. it seems that there are many more benchmark tests than runtimes. perhaps switching the axes would make it easier to read (or maybe it's just my preference for vertical scrolling over horizontal.) also, highlighting the lowest value for each bench test (perhaps by adding a little background color) might make the output easier to parse, at a glance. hrmm. looking some more, it seems 'total' is hard to interpret, since some runtimes don't run some bench tests. maybe also listing '# tests run', and 'total # tests' alongside the 'total' would help in the interpretation. ~jerry ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance.
RE: Interfaces, briefly
> since presumably interfaces are a bit more uniquely named than > methods, and an object may be able to do something some class does > while not actually being in that class. > should interface names be registered somewhere? how are collisions handled? i can imagine a scenario where multiple 'print' interfaces have been created. how will parrot handle this? or am i missing something basic? ~jerry ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance.
RE: ICU Outdated - Ideas
Leopold Toetch wrote: > Both ways - or better three stages: Its optional. If its > there, we *can* link against it. If you want/need it, and > your OS doesn't have it, well, then install it. > and if you don't want it you get... what? no unicode support? a hand-rolled solution? just what is the alternative? ~jerry ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance.
RE: [perl #30500] [PATCH] Yet another Perl Version Issue
> I attach a patch which uses Sortkey only in Versions of > Data::Dumper supporting Sortkey. In what version was Sortkey > introduced to Data::Dumer? > > bye > boe > > Data::Dumper 2.12 (introducing Sortkeys) was first released on the CPAN in perl-5.7.3. $Data::Dumper::Sortkeys is available in perl 5.6.2 or later 5.6.x releases, and has been available in every release since 5.8.0. ~jerry ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance.
RE: Events (I think we need a new name)
Dan Sugalski wrote: > It does, though, sound like we might want an alternate name for this > stuff. While event is the right thing in some places it isn't in others > (like the whole attribute/property mess) we may be well-served choosing > another name. I'm open to suggestions here... > incident? it's synonymous with "event," but it's not usually something of importance. also synonymous with "problem" in business-speak. occurrence? it doesn't roll off the tongue, but i think of an event as an occurrence worth mentioning, an important occurrence. ~jerry ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance.
[PATCH] RE: Safe execution core and ops classification
> - do we expect to have more then 32 different classes? > i see 13 operator classes currently, though my tree may be out of date > A perl script that scans ops-files for opcode classes and spits out: > > a) a pod with opcode classes headings and the list of opcodes that > belong to that class (at best created from a template, which has some > more explanation to that stuff) > the attached tarfile contains a script (tools/docs/opslist.pl) should generate a file, docs/ops/opslist.pod, with the above information > b) a C include file that defines bitmask enums for the > classes plus some > common shortcuts comming from a config file. These enums > should then be > scanned during Configure and provide a user visible PASM in > runtime/parrot/include. > If we have more then 32 classes, we'll use a ParrotSet PMC > (which will > be handy anyway) > i'm not sure where to get the info i need to do this. hope the attached script helps. > leo > --jerry ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. opsfile.tgz Description: Binary data
RE: Safe execution core and ops classification
> - do we expect to have more then 32 different classes? > i see 13 operator classes currently > A perl script that scans ops-files for opcode classes and spits out: > > a) a pod with opcode classes headings and the list of opcodes that > belong to that class (at best created from a template, which has some > more explanation to that stuff) > the attached tarfile contains a script (tools/docs/opslist.pl) should generate a file, docs/ops/opslist.pod, with the above information > b) a C include file that defines bitmask enums for the > classes plus some > common shortcuts comming from a config file. These enums > should then be > scanned during Configure and provide a user visible PASM in > runtime/parrot/include. > If we have more then 32 classes, we'll use a ParrotSet PMC > (which will > be handy anyway) > i'm not sure where to get the info i need to do this. hope the attached script helps. > leo > --jerry ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. The file opslist.tar was removed from this message.
RE: How do I....
thanks all for the clarifications... > > and they aren't listed in > ops.num yet, > > They are listed in ops.num #1374 - #1385 since quite a time. > this morning i performed a 'cvs co parrot' and ran make (win32 - msvc,) which generated the following information, leading to my statement above: cl -nologo -Gf -W3 -MD -Zi -DNDEBUG -DWIN32 -D_CONSOLE -DNO_STRICT -ZI -I./include -DHAS_JIT -DI386 xx.obj -c xx.c D:\usr\local\perl580\bin\perl.exe build_tools\ops2pm.pl ops/core.ops ops/bit.ops ops/cmp.ops ops/debug.ops ops/dotgnu.ops ops/io.ops ops/math.ops ops/object.ops ops/pmc.ops ops/rx.ops ops/set.ops ops/stack.ops ops/string.ops ops/sys.ops ops/var.ops addparent_p_p 1364not mentioned in ops.num removeparent_p_p1365not mentioned in ops.num addattribute_p_s_s 1366not mentioned in ops.num addattribute_p_sc_s 1367not mentioned in ops.num addattribute_p_s_sc 1368not mentioned in ops.num addattribute_p_sc_sc1369not mentioned in ops.num store_global_s_s_p 1370not mentioned in ops.num store_global_sc_s_p 1371not mentioned in ops.num store_global_s_sc_p 1372not mentioned in ops.num store_global_sc_sc_p1373not mentioned in ops.num store_global_p_s_p 1374not mentioned in ops.num store_global_p_sc_p 1375not mentioned in ops.num find_global_p_s_s 1376not mentioned in ops.num find_global_p_sc_s 1377not mentioned in ops.num find_global_p_s_sc 1378not mentioned in ops.num find_global_p_sc_sc 1379not mentioned in ops.num find_global_p_p_s 1380not mentioned in ops.num find_global_p_p_sc 1381not mentioned in ops.num D:\usr\local\perl580\bin\perl.exe build_tools\ops2c.pl C --core D:\usr\local\perl580\bin\perl.exe build_tools\ops2c.pl CPrederef --core D:\usr\local\perl580\bin\perl.exe build_tools\ops2c.pl CSwitch --core i'm probably reading that wrong, but i figured that meant find_global and store_global weren't in ops.num. now that i look in ops.num, i see find_global_p_s 1235 find_global_p_sc1236 but some ops do indeed seem to be missing. if putting them in is as easy as running patch against ops/ops.num with: 1391,1409d1390 < addparent_p_p 1364 < removeparent_p_p1365 < addattribute_p_s_s 1366 < addattribute_p_sc_s 1367 < addattribute_p_s_sc 1368 < addattribute_p_sc_sc1369 < store_global_s_s_p 1370 < store_global_sc_s_p 1371 < store_global_s_sc_p 1372 < store_global_sc_sc_p1373 < store_global_p_s_p 1374 < store_global_p_sc_p 1375 < find_global_p_s_s 1376 < find_global_p_sc_s 1377 < find_global_p_s_sc 1378 < find_global_p_sc_sc 1379 < find_global_p_p_s 1380 < find_global_p_p_sc 1381 then please consider converting this to a proper patch and applying it. i'm having a little trouble right now at the moment with my wincvs install, so i can't get this formatted in the preferred diff format. i hope this helps. --jerry ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance.
RE: How do I....
On Tuesday, March 16, 2004 7:32 AM, Jens Rieks wrote: > You can also use another namespace: > store_global "TCL::InternalData", "globals", the_hash > ... > find_global the_hash, "TCL::InternalData", "globals" is there a good reason why the signatures are different for 'store_global' and 'find_global'? i can see the logic for either way, but a different argument list for each is inconsistant, and a bit confusing. i know that store_global and find_global are new, and they aren't listed in ops.num yet, so modifying one of their signatures shouldn't affect too much code. where would i go about finding more info on this? i'm source diving now, but it's a deep pool and i'm not a very good swimmer yet. i'd like to submit a patch (if needed), or at least where a patch may make changes to this functionality. --jerry ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance.
RE: [FYI] mainframe inside the notebook
> [1] www.conmicro.cx/Hercules/ thanks for the info, although that link is broken. try instead: http://www.conmicro.cx/hercules/ --jerry ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance.
RE: www.parrotcode.org/ points to 0.0.10
> As promised. > > The "new" site is now live. > > -R thank you! this looks fantastic, and the html docs will be a valuable and welcome addition. --jerry ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance.
RE: [perl #27246] [PATCH] Correct ommision inconfig/gen/makefiles /befun ge.in
if this is accepted, please close [perl #27083], as it addresses this bug,
but i haven't yet seen it posted to the list.
--jerry
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Sent: Monday, March 01, 2004 2:20 AM
> To: [EMAIL PROTECTED]
> Subject: [perl #27246] [PATCH] Correct ommision
> inconfig/gen/makefiles/befun ge.in
>
>
> # New Ticket Created by [EMAIL PROTECTED]
> # Please include the string: [perl #27246]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org:80/rt3/Ticket/Display.html?id=27246 >
>
>
> There was no
> PERL = ${perl}
> definition in this file (which does exist in jako.in and
> others), hence when the
> "clean" target was called, the RM_F expansion omitted the
> perl resulting in
>
> nmake befunge clean
>
> and all the dependancies
>
> nmake languages-clean
> nmake clean
> nmake realclean
>
> failing with "invalid command or filename".
>
> Lokking around, I think that BF.in is similarly wrong, but I
> am not currently
> building that, and could be mistaken .
>
>
>
**
This e-mail and any files transmitted with it may contain privileged or
confidential information. It is solely for use by the individual for whom
it is intended, even if addressed incorrectly. If you received this e-mail
in error, please notify the sender; do not disclose, copy, distribute, or
take any action in reliance on the contents of this information; and delete
it from your system. Any other use of this e-mail is prohibited. Thank you
for your compliance.
RE: Various newbie questions.
> 1) Is there any way past this problem? > >cvs -d :pserver:[EMAIL PROTECTED]:/cvs/public co parrot > ... > ... >U parrot/ops/var.ops >cvs server: Updating parrot/pf >U parrot/pf/pf_items.c >cvs [checkout aborted]: could not chdir to > parrot/platforms: Invalid argument > as Arvindh Rajesh Tamilmani wrote earlier today, in the "[CVS ci] PLATFORMS" thread: $ cvs co '!parrot/platforms' parrot will fix this problem. see the thread for more detail. http://groups.google.com/groups?dq=&hl=en&lr=&ie=UTF-8&oe=UTF-8&threadm=2004 0224170409.34391.qmail%40web8203.mail.in.yahoo.com&prev=/groups%3Fhl%3Den%26 lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26group%3Dperl.perl6.internals > 2) I sent this question previously (22 Feb 2004 20:37 GMT) > but it never made it > onto the list. (I was unsubscribed!). > > If I make a change in win32.c, (now: > config/gen/platform/win32/exec.c) what is > the procedure (or where is this documented) to get platform.c > re-generated and > compiled into parrot.exe? > > The only mechanism I have found that does this is to > > nmake realclean > configure.pl > nmake > > which doesn't seem right somehow, but I think I've read every > documentation file > at least twice and nothing has leaped of the page as to the > right way to do > this. that's the way i do it (actually, i use "nmake distclean") --jerry ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance.
RE: [CVS ci] PLATFORMS
> Does the following command work? > > $ cvs co '!parrot/platforms' parrot > # the order should be preserved. > > Arvindh > this works for me on win32 --jerry ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance.
RE: Release doc tasks
> One thing that would help is if people ran > > perl tools/docs/write_docs.pl -d -s > > on various platforms and told me if it works - or what they runs fine on Windows 2000, with only the warning mentioned by chromatic. ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance.
RE: Rules for method resolution?
> We also have to have a way to fetch the method PMC for a named method > for later use, which is where the interesting bits come in. > > This is required for a number of reasons, including Python, so we > have to have it. The question is... *When* is the name resolved? That > is, if we do: > > findmethod P4, Pobject, "methodname" > > does the method PMC that gets stuck in P4 represent the method > "methodname" for the object *at that point in time* or does it > represent the method *at the time it is invoked*? That is, do we > defer actual lookup until invocation, or do we resolve at method find > time? > > This has some implications for when methods are overridden and > namespaces swapped in and out, so it's (unfortunately) not an > academic exercise. > -- is it too much trouble to implement both, and give the HLLs a choice of which they call? would 'findmethod_sooner' and 'findmethod_later' be too difficult to implement, or too large to add to the core ops? what do you lose by offering both, as opposed to one or the other? i wish i had more answers than questions... --jerry *no longer just a lurker* ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance.
