pynt-devel Mailing List for Pynt (Page 6)

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Your measurement of success is by the INCH.
Be her pleasure machine!
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
Having problems with the length of your dick? Use our medicine, and<br>
it will take four fat women and a team of Clydesdales to jack you off. <a href="http://slaysandg.com/">http://slaysandg.com/</a><br>
</html>

would you prefer to have an average cock or something that will really knock the fucking socks off her http://www.onther.com/

shopping online for a watch? have you seen our selection yet? =
http://www.acadez.com/
once you see the massive selection, it will be hard to resist =
http://hpfsms.com/
WATCH KGLJ TRADE ON
MONDAY OCTOBER 15, 2007
WE ARE 100% CONFIDENT THAT THIS ONE WILL BE THE RUNNER OF THE YEAR!

Name: Kingslake Energy, Inc.
Symbol: KGLJ
Price: $1.51
5-D Target: $4
Rating: Agressive Buy

ADD KGLJ TO YOUR RADAR ON MONDAY OCTOBER 15!
RIDE THE WAVE LIKE A SURFER! END UP ON TOP!
DON'T LET KGLJ PASS YOU BY!

DISCLAIMER: This is not an offer to buy or sell any security. ASA Press =
discloses that they were paid ten thousand dollars for distribution of =
this report.
This report contains forward-lqqking statements. Please do due diligence =
before investing in any company. Best of luck to you in the markets this =
morning!
Good day pynt-devel

Alert to all investors!
Look at D-M-X-C!
5-day price: ~$0.50

Check it at 31.09.2007
iskytinn
iskusta
iskijiun
iskovro
R,umor N,e'w-s,: 
O nc'ology M+e*d'. I_n,c_.  (O TC: ONC_O) a C ancer Trea.tmen*t Sol+utio =
ns Gr*oup is s*a_i.d to h,a*v,e 

e.xperien+ced o_v*e_r a 1-000% incre+a se in reve-nue-s f_o-r t+h-e =
fis'cal 3_r'd quarte+r end-ing J,u.l*y,, 
2*0 0+7 c.omp-ared w,i't,h t*h-e pri.or y*e+a*r whil.e fisca.l f.ourth =
quar+ter res'ults f_o_r 2-0 0,7 a.r'e on
tr.ack to ex_ceed t.h i-s yea-r=92s t hird quar'ter resu,lts. 

O-N_C.O addition*al_ly p_lans to incre*+ase ser-vice offe_ri'ngs wh'ich =
a-r.e c,urrentl,y unde*rwa-y. 

Don_=92t w_a.i.t f_o+r t+h,e n'e'w s to c,o,m e o_u+t a'n,d l'o-s*e =
t.h'e opp--ortunity to g*e-t in fro-nt of the
gen'eral inv esti ng publ-ic.  O_ncolo*gy M+e.d is in a m,ult,ibillion =
d-ollar in.d ustry w h_e'r*e 
t_h_e*y a r+e gaini+ng mark*et sha re rap-idly. 

C+a l,l y-o-u.r bro'ker n_o*w f o*r O_N'C+O . 

http://clubcf.net/
regards pynt-devel
The guys get jealous now when they see me in the bathroom

Muhtashem j
Stimulate your virility with today’s most effective products for men!
Get it here at the lowest imaginable price – in as short time as possible!
These goods keep men all around the world satisfied – now it is your turn!
http://Corona.mucpace.cn

Hello my friend,
Guys, I love this shop so much, you won't regret
Cool shop in a one click
http://Byrne.oldsymbol.cn
Forget about all your ED problems with these products – once and for all!
Significant results in shortest time – no need in long-lasting therapy!
Millions of men all over the world use these brand-name goods – and enjoy it!
http://urmoxsx.togethernote.hk/?625152714915
ANLEGER UHR BJ5N.F!!!
DIE RALLYE IST GESTARTET

Firma: BOERSE INVEST BETEI
WKN : 797639
ISIN : CH0012802093
Markt: Frankfurt
Kürzel : BJ5N.F
Preis: 1.90
5-Tag Prognose: 3.00

KAUFEN KAUFEN KAUFEN!
BJ5N.F ESGESCHAFT FIN UNTER PARI!

http://img358.imageshack.us/my.php?image=40955107fc6.png
Up,  in  days.

But the present treatment by her husband and brother was everything save chivalrous.

Dear Open Source developer

I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate.
You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it.

With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development.

With many thanks for your participation,
Benno Luthiger

PS:
The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/.
We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list.

_______________________________________________________________________

Benno Luthiger
Swiss Federal Institute of Technology Zurich
8092 Zurich

Mail: benno.luthiger(at)id.ethz.ch
_______________________________________________________________________
I've just checked in whole bunch of new code, more or less a complete 
rewrite. I plan on updating the documentation sometime this week, then 
we'll do a 0.1.0 release. The main differences between this version and 
the last are:

* No more ant integration. Need to revisit this, see if it's something we 
still want to do. Ideally writing tasks in pynt will be a lot easier than 
in ant (if not we need to change pynt), so it might be worth just writing 
new versions of the most common tasks. 
* No more python style indentation syntax (too controversial). Blocks now 
end with an "end" statement.
* Added a "export" keyword to indicate which methods/fields should be 
imported by other pynt files. I've also switched the "load" and "import" 
keywords, so that you now use "import" to import other pynt files, and 
"load" to load java classes.
* Can no longer embed variables into strings (ie "my name is {name}"). 
Need to revisit this.
* The pipe syntax is gone for scanning for files - use the Scan method in 
files.pynt instead (which is not as clean, i admit)
* Slight changes to the "load" syntax
* Removed new() method to create a new pynt object, but added a "this" 
keyword that can be used to return the current stack frame.
* Started using upper case for the first letter of method names, to avoid 
collisions

See the pynt.pynt file for an example of a lot of these changes
___

Short term issues:

* Better syntax for creating PyntFiles 
* Sort out collection types (need an easy way to handle paths, filesets, 
etc)
* Reassigning a value to a variable should fail
* Tests
* A lot of other things i can't think of right now
___

Long term issues:

* Syntax for regular expressions and xml
___

Possible changes:

* I'm considering removing the need for parenthesis on method calls. This 
would make methods behave more like our built in functions (and indeed, 
things like "print" and "show" could be implemented as pynt functions, not 
built in constructs). So for example, instead of writing:

Javac(files=myfiles,output="dest")

You would just write:

Javac files=myfiles output=dest

Which I think is cleaner when typing things at the interactive prompt. 
However, you would no longer be obvious whether you were calling a method 
or a target (do we care?) 

* A bigger change i'm considering would be to make *every* expression 
evaluated in a lazy way, not just targets. This would make pynt similar to 
a lot of functional languages with lazy evaluation (ie Haskell). The 
benefit is that developers won't need to define explicit targets. The 
downside is that it can seem a bit counter-intuitive at times.

How it works is that whenever you see an assignment in pynt, the value on 
the right will *not* be evaluated until the value on the left is used. For 
example:

> foo = print "10"      # produces no output
> foo                            # now evaluates "print 10"
10

This basically eliminates the need for "target" and "build" expressions. 
You could just have:

javac = Javac classpath=myclasspath ...
jar = Jar files=(Scan javac.output)...
test = classpath=javac.classpath...

Then from the command line, typing "jar" would cause the "Jar files=..." 
expression to be evaluated, and the "javac.output" expression will cause 
"Javac classpath-..." to be evaluated. But the "test" line will not be 
evaluated. Looks promising, but need to try it out on larger build files 
to see how it works.
___

Thoughts?

Matt Foemmel
ThoughtWorks, Inc.
Download it here:

https://sourceforge.net/project/showfiles.php?group_id=77874

Matt Foemmel
ThoughtWorks, Inc.
I've added a statement to let you run external programs. For example, the 
following will run the compiler:

exec "javac Foo.java"

I also added a PyntAST class, which has a convenience method for throwing 
a PyntException with the line and column numbers fill in. I still need to 
change all of the AST classes to extend this class (indirectly), and 
change all the places where we throw exceptions to use the error() 
method...
I agree I do like this syntax.  However I wasn't entirely clear if you were
saying that import is only for importing other scripts or if import was
also going to be used to load jars into the system.  If you were thinking
of both I think it would make sense to have it be something like:
      import junit.jar as junit
            or
      import junit.pynt as junit

this will help to make it more clear when looking at the build script what
exactly is being imported.

Mike

                      mpf...@Th...                                                                                                  
                      Sent by:                           To:       pyn...@li...                                              
                      pyn...@li...        cc:                                                                                     
                      ceforge.net                        Subject:  [pynt-devel] imports                                                          

                      04/11/2003 05:31 PM                                                                                                        

I'm trying to think of a way to have the "import" statement work across
multiple pynt scripts, was wondering what you thought about this idea. What
I'd like to do is have something like this:

import ant

ant.javac.debug = true
ant.javac.optimize = false
...etc...

So when "ant" gets imported, a single object gets returned and assigned to
the "ant" variable. This object has inner objects for each of the ant
tasks. Pynt would also make sure that "ant" only gets imported once. This
avoids name collisions and allows us to resovle references imported targets
correctly.

For example, let's say I want to compile junit, antlr, and pynt, where
antlr depends on junit, and pynt depends on both:

* junit.pynt *
target compile:
        ...

* antlr.pynt *
import junit

target compile:
        build junit.compile
        ...

* pynt.pynt *
import junit
import antlr

target compile:
        build junit.compile, antlr,compile
        ...

In this case, junit.pynt would only get run once, even though it is
imported twice. You can think of each pynt script as defining a singleton
object, and the imports simply create a reference to that singleton. We
would need to set up some sort of PYNTPATH to tell pynt where to look for
the imported scripts (ie "import junit" would look for "junit.pynt", or
maybe for a jar file called "junit.par" or something).

thoughts?

I'm trying to think of a way to have the "import" statement work across 
multiple pynt scripts, was wondering what you thought about this idea. 
What I'd like to do is have something like this:

import ant

ant.javac.debug = true
ant.javac.optimize = false
...etc...

So when "ant" gets imported, a single object gets returned and assigned to 
the "ant" variable. This object has inner objects for each of the ant 
tasks. Pynt would also make sure that "ant" only gets imported once. This 
avoids name collisions and allows us to resovle references imported 
targets correctly.

For example, let's say I want to compile junit, antlr, and pynt, where 
antlr depends on junit, and pynt depends on both:

* junit.pynt *
target compile:
        ...

* antlr.pynt *
import junit

target compile:
        build junit.compile
        ...

* pynt.pynt *
import junit
import antlr

target compile:
        build junit.compile, antlr,compile
        ...

In this case, junit.pynt would only get run once, even though it is 
imported twice. You can think of each pynt script as defining a singleton 
object, and the imports simply create a reference to that singleton. We 
would need to set up some sort of PYNTPATH to tell pynt where to look for 
the imported scripts (ie "import junit" would look for "junit.pynt", or 
maybe for a jar file called "junit.par" or something).

thoughts?
I've added these tasks to the pynt sourceforge project.  The task list =
can
be found at
https://sourceforge.net/pm/task.php?group_id=3D77874&set=3Dcustom&group=
_project_id=3D28221&_assigned_to=3D0&_status=3D1&SUBMIT=3DBrowse.
  This should allow us to keep track of what needs to be worked on with=
out
needing to keep several different e-mails.  It should also keep more th=
an
one person unknowingly working on the same tasks.

Mike

                                                                       =
                                                                       =
  =20
                      mpf...@Th...                        =
                                                                       =
  =20
                      Sent by:                           To:       <pyn=
t-...@li...>                                         =
  =20
                      pyn...@li...        cc:           =
                                                                       =
  =20
                      ceforge.net                        Subject:  [pyn=
t-devel] todo list                                                     =
  =20
                                                                       =
                                                                       =
  =20
                                                                       =
                                                                       =
  =20
                      04/09/2003 01:36 PM                              =
                                                                       =
  =20
                                                                       =
                                                                       =
  =20
                                                                       =
                                                                       =
  =20

Here are the big things I'd like to tackle next:

* Pull ant stuff out into a separate module. I would like to have the c=
ore
language not dependent on ant, there should be a generic way to import =
that
functionality
* Fix "new" syntax, it's kinda confusing since it's really a clone()
operation. Should be replaced with a new() or clone() method on object.=

* Need a way to create random java objects. It would be nice if this di=
dn't
complicate the whole cloning vs. instantiating thing
* "overridable" variables, so that if a variables like buildLabel can b=
e
defined outside the script (maybe have a "constant:" declaration, simil=
ar
to "var", except it can be multiply defined but only first one counts)
* Documentation
* Need to sort out scoping issues for code like this, to differentiate
between the "mkdir.dir" field and the "dir" variable argument passed in=
to
the method:

var dir =3D "."
mkdir:
=A0 =A0 =A0 =A0 dir =3D dir

Also, I've added some functionality to StringExpression to do file
separator conversions (ie '/' gets converted to File.separatorChar) and=

embedded variable references (ie "abc{foo}def" gets converted to
"abdXXXdef", assuming foo =3D XXX). Let me know what you think.

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
pynt-devel mailing list
pyn...@li...
https://lists.sourceforge.net/lists/listinfo/pynt-devel

=

Here are the big things I'd like to tackle next:

* Pull ant stuff out into a separate module. I would like to have the c=
ore
language not dependent on ant, there should be a generic way to import =
that
functionality
* Fix "new" syntax, it's kinda confusing since it's really a clone()
operation. Should be replaced with a new() or clone() method on object.=

* Need a way to create random java objects. It would be nice if this di=
dn't
complicate the whole cloning vs. instantiating thing
* "overridable" variables, so that if a variables like buildLabel can b=
e
defined outside the script (maybe have a "constant:" declaration, simil=
ar
to "var", except it can be multiply defined but only first one counts)
* Documentation
* Need to sort out scoping issues for code like this, to differentiate
between the "mkdir.dir" field and the "dir" variable argument passed in=
to
the method:

var dir =3D "."
mkdir:
=A0 =A0 =A0 =A0 dir =3D dir

Also, I've added some functionality to StringExpression to do file
separator conversions (ie '/' gets converted to File.separatorChar) and=

embedded variable references (ie "abc{foo}def" gets converted to
"abdXXXdef", assuming foo =3D XXX). Let me know what you think.
=

2003	Jan	Feb	Mar	Apr (7)	May	Jun	Jul (1)	Aug	Sep	Oct	Nov	Dec
2004	Jan	Feb	Mar	Apr	May (1)	Jun	Jul	Aug (1)	Sep (1)	Oct (2)	Nov (2)	Dec
2006	Jan	Feb	Mar (2)	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2007	Jan	Feb	Mar	Apr (2)	May	Jun	Jul (2)	Aug (2)	Sep (3)	Oct (2)	Nov (4)	Dec (5)
2008	Jan (2)	Feb (3)	Mar (35)	Apr (24)	May (16)	Jun (6)	Jul (14)	Aug (5)	Sep (12)	Oct (12)	Nov (39)	Dec (64)
2009	Jan (31)	Feb (15)	Mar (39)	Apr (46)	May (123)	Jun (94)	Jul (72)	Aug (23)	Sep (26)	Oct (33)	Nov (4)	Dec (11)
2010	Jan (6)	Feb (7)	Mar (35)	Apr (49)	May (70)	Jun (68)	Jul (42)	Aug (50)	Sep (27)	Oct (7)	Nov	Dec
2011	Jan (1)	Feb (3)	Mar	Apr	May	Jun (1)	Jul	Aug	Sep	Oct	Nov	Dec
2013	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct (1)	Nov	Dec

pynt-devel Mailing List for Pynt (Page 6)

pynt-devel — Developer List